aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware/layerscape/ppfe-firmware
Commit message (Collapse)AuthorAgeFilesLines
* ppfe-firmware: Bump to lf-6.1.1-1.0.0 and switch to githubWojciech Dubowik2023-05-201-5/+5
| | | | | | | | | | | | | The default location of ppfe-firmware has been changed from codeuaurora to github. Also use the latest tag for Layerscape Linux Development POC from NXP. Tested on: * NXP FRWY-LS1012A Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@protonmail.ch> (reset PKG_RELEASE) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* treewide: replace AUTORELEASE with real PKG_RELEASETianling Shen2023-05-181-1/+1
| | | | | | | | | | | | | | | | | | Based on Paul Fertser <fercerpav@gmail.com>'s guidance: Change AUTORELEASE in rules.mk to: ``` AUTORELEASE = $(if $(DUMP),0,$(shell sed -i "s/\$$(AUTORELEASE)/$(call commitcount,1)/" $(CURDIR)/Makefile)) ``` then update all affected packages by: ``` for i in $(git grep -l PKG_RELEASE:=.*AUTORELEASE | sed 's^.*/\([^/]*\)/Makefile^\1^';); do make package/$i/clean done ``` Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* layerscape: update remaining PKG_HASH / PKG_MIRROR_HASHChristian Lamparter2022-07-221-1/+1
| | | | | | | | | The change of the PKG_VERSION caused the hash of the package to change. This is because the PKG_VERSION is present in the internal directory structure of the archive. Fixes: e879cccaa215 ("uboot-layerscape: update PKG_HASH") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* layerscape: use semantic versions for LSDKPaul Spooren2022-03-011-1/+1
| | | | | | PKG_VERSION should not contain the package name but the version only. Signed-off-by: Paul Spooren <mail@aparcar.org>
* ppfe-firmware: bump to LSDK-21.08Martin Schiller2021-12-131-4/+4
| | | | | | | | Update ppfe-firmware to latest LSDK-21.08. Switched to AUTORELEASE for simplicity. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* treewide: Mark packages nonshared if they depend on @TARGET_Hauke Mehrtens2021-05-241-0/+2
| | | | | | | | | | | | | | This marks all packages which depend on a target with @TARGET nonshared. If they are not marked nonshared they would be build by the SDK build and if this happens with a different SDK, then the SDK from the target the package depends on, the package would not be added to the index. This should fix the image builder for some of these packages. This should fix the image builder at least for bcm27xx/bcm2710 and bcm4908/generic. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* layerscape: update ppfe-firmware to LSDK-20.04Yangbo Lu2020-05-071-3/+3
| | | | | | Update ppfe-firmware to latest LSDK-20.04. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ppfe-firmware to LSDK 19.03Biwen Li2019-06-061-3/+3
| | | | | | | Update ppfe-firmware to LSDK 19.03. Signed-off-by: Biwen Li <biwen.li@nxp.com> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ppfe-firmware to LSDK-18.06Yangbo Lu2018-09-221-6/+4
| | | | | | This patch is to update ppfe-firmware to LSDK-18.06 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ppfe firmware to LSDK1712Yangbo Lu2018-02-131-5/+5
| | | | | | | | Updated ppfe firmware to NXP LSDK1712 release. Used ppfe firmware git tree on NXP github since it was migrated here from qoriq-open-source github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: fix package downloadHauke Mehrtens2017-12-211-2/+2
| | | | | | | | | | | | | | | | The git hash was changed for multiple layerscape packages without changing the version number. The LEDE build system will not download the packages again if the old version is already there and so some people and the build bots are using wrong version of some packages. Use PKG_SOURCE_DATE instead of PKG_VERSION to generate packages with the date and the first charterers of the git hash. This will change the file name and make the build system download them again, also if in future the git hash is changed the file name will change and trigger a new download. This should fix a problem spotted by build bot. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* layerscape: support LSDK ppfeYangbo Lu2017-11-101-61/+26
| | | | | | | | This patch is to use ppfe git tree on LSDK github instead of private git tree, and support the latest ppfe on ls1012ardb. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: move fman/rcw/ppfe packages to layerscape/Yangbo Lu2017-11-101-0/+87
This patch is to create a layerscape directory for all firmware packages of layerscape. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-27 03:29:38 +0000
IDEV_BACKEND tristate "PCI device backend driver" depends on PCI && XEN_BACKEND default XEN_PRIVILEGED_GUEST help The PCI device backend driver allows the kernel to export arbitrary PCI devices to other guests. If you select this to be a module, you will need to make sure no other driver has bound to the device(s) you want to make visible to other guests. choice prompt "PCI Backend Mode" depends on XEN_PCIDEV_BACKEND default XEN_PCIDEV_BACKEND_VPCI config XEN_PCIDEV_BACKEND_VPCI bool "Virtual PCI" ---help--- This PCI Backend hides the true PCI topology and makes the frontend think there is a single PCI bus with only the exported devices on it. For example, a device at 03:05.0 will be re-assigned to 00:00.0. A second device at 02:1a.0 will be re-assigned to 00:01.0. config XEN_PCIDEV_BACKEND_PASS bool "Passthrough" ---help--- This PCI Backend provides a real view of the PCI topology to the frontend (for example, a device at 06:01.b will still appear at 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed PCI devices to its driver domains. This may be required for drivers which depend on finding their hardward in certain bus/slot locations. endchoice config XEN_PCIDEV_BE_DEBUG bool "PCI Backend Debugging" depends on XEN_PCIDEV_BACKEND default n config XEN_BLKDEV_BACKEND tristate "Block-device backend driver" depends on XEN_BACKEND default y help The block-device backend driver allows the kernel to export its block devices to other guests via a high-performance shared-memory interface. config XEN_BLKDEV_TAP_BE tristate "Block Tap support for backend driver (DANGEROUS)" depends on XEN_BLKDEV_BACKEND default n help If you intend to use the block tap driver, the backend domain will not know the domain id of the real frontend, and so will not be able to map its data pages. This modifies the backend to attempt to map from both the tap domain and the real frontend. This presents a security risk, and so should ONLY be used for development with the blktap. This option will be removed as the block drivers are modified to use grant tables. config XEN_NETDEV_BACKEND tristate "Network-device backend driver" depends on XEN_BACKEND && NET default y help The network-device backend driver allows the kernel to export its network devices to other guests via a high-performance shared-memory interface. config XEN_NETDEV_PIPELINED_TRANSMITTER bool "Pipelined transmitter (DANGEROUS)" depends on XEN_NETDEV_BACKEND default n help If the net backend is a dumb domain, such as a transparent Ethernet bridge with no local IP interface, it is safe to say Y here to get slightly lower network overhead. If the backend has a local IP interface; or may be doing smart things like reassembling packets to perform firewall filtering; or if you are unsure; or if you experience network hangs when this option is enabled; then you must say N here. config XEN_NETDEV_LOOPBACK tristate "Network-device loopback driver" depends on XEN_NETDEV_BACKEND default y help A two-interface loopback device to emulate a local netfront-netback connection. config XEN_TPMDEV_BACKEND tristate "TPM-device backend driver" depends on XEN_BACKEND default n help The TPM-device backend driver config XEN_TPMDEV_CLOSE_IF_VTPM_FAILS bool "TPM backend closes upon vTPM failure" depends on XEN_TPMDEV_BACKEND default n help The TPM backend closes the channel if the vTPM in userspace indicates a failure. The corresponding domain's channel will be closed. Say Y if you want this feature. config XEN_BLKDEV_FRONTEND tristate "Block-device frontend driver" depends on XEN default y help The block-device frontend driver allows the kernel to access block devices mounted within another guest OS. Unless you are building a dedicated device-driver domain, or your master control domain (domain 0), then you almost certainly want to say Y here. config XEN_NETDEV_FRONTEND tristate "Network-device frontend driver" depends on XEN && NET default y help The network-device frontend driver allows the kernel to access network interfaces within another guest OS. Unless you are building a dedicated device-driver domain, or your master control domain (domain 0), then you almost certainly want to say Y here. config XEN_BLKDEV_TAP tristate "Block device tap driver" depends on XEN_BACKEND default n help This driver allows a VM to interact on block device channels to other VMs. Block messages may be passed through or redirected to a character device, allowing device prototyping in application space. Odds are that you want to say N here. config XEN_SCRUB_PAGES bool "Scrub memory before freeing it to Xen" default y help Erase memory contents before freeing it back to Xen's global pool. This ensures that any secrets contained within that memory (e.g., private keys) cannot be found by other guests that may be running on the machine. Most people will want to say Y here. If security is not a concern then you may increase performance by saying N. config XEN_DISABLE_SERIAL bool "Disable serial port drivers" default y help Disable serial port drivers, allowing the Xen console driver to provide a serial console at ttyS0. config XEN_SYSFS tristate "Export Xen attributes in sysfs" depends on SYSFS default y help Xen hypervisor attributes will show up under /sys/hypervisor/. choice prompt "Xen version compatibility" default XEN_COMPAT_030002_AND_LATER config XEN_COMPAT_030002_AND_LATER bool "3.0.2 and later" config XEN_COMPAT_LATEST_ONLY bool "no compatibility code" endchoice config XEN_COMPAT_030002 bool default XEN_COMPAT_030002_AND_LATER endmenu config HAVE_ARCH_ALLOC_SKB bool default y config HAVE_ARCH_DEV_ALLOC_SKB bool default y config NO_IDLE_HZ bool default y endif
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-27 03:29:37 +0000