[linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp
Zumeng Chen
zchen at windriver.com
Thu Jun 13 17:05:14 PDT 2019
Ha, yes, thanks Bruce, it's just right time. Have a good trip ~
And I did a quick check, it's OK as well :)
zchen at pek-lpggp4:$ bitbake linux-yocto-dev
WARNING: You have included the meta-openstack layer, but 'openstack' has
not been enabled in your DISTRO_FEATURES. Some bbappend files and
preferred version setting may not take effect. See the meta-openstack
README for details on enabling openstack support.
Parsing recipes: 100%
|#############################################################################################################################################################################|
Time: 0:00:38
Parsing of 3648 .bb files complete (0 cached, 3648 parsed). 8552
targets, 5849 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
/buildarea1/zchen/build-19/wr19-06-14-arm64/layers/meta-cloud-services/meta-openstack/recipes-connectivity/openssh/openssh_7.%.bbappend
/buildarea1/zchen/build-19/wr19-06-14-arm64/layers/meta-cgl/meta-cgl-common/recipes-extended/umip/umip_%.bbappend
WARNING: No bb files matched BBFILE_PATTERN_overc ''
WARNING: No bb files matched BBFILE_PATTERN_cube ''
WARNING: No bb files matched BBFILE_PATTERN_wrlinux-overc ''
NOTE: Resolving any missing task queue dependencies
Build Configuration:
WRLINUX_VERSION = "10.19.24.0"
WRLINUX_BRANCH = "development"
BB_VERSION = "1.43.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
DISTRO = "wrlinux-std-sato"
DISTRO_VERSION = "10.19.24.0"
MACHINE = "xilinx-zynqmp"
DEFAULTTUNE = "cortexa53"
TARGET_SYS = "aarch64-wrs-linux"
TUNE_FEATURES = "aarch64 cortexa53 crc"
TARGET_FPU = ""
lib32: DEFAULTTUNE = "armv7athf-neon"
lib32: TARGET_SYS = "arm-wrsmllib32-linux-gnueabi"
lib32: TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
lib32: TARGET_FPU = "hard"
wrlinux
wrlinux-distro = "master-wr:7fe21fafdfffcfb483bc5a4152fdfeb445b61e80"
meta =
"wr-10.19-20190610:50529a3a7b1d6867d9e4ec9d47b21f56578444b4"
meta-initramfs
meta-xfce
meta-oe
meta-filesystems
meta-webserver
meta-networking
meta-python
meta-perl
meta-gnome
meta-multimedia =
"wr-10.19-20190528:9facfad2b487cdc1b335b1073b9182040de9676e"
meta-security =
"wr-10.19-20190529:b73416279b6b7f1735146911bb953e9bb13eb08f"
meta-selinux =
"wr-10.19-20190424:a8ed51181e5444c82f9702b6b5d12ca575472a58"
intel-x86 = "master-wr:ad411c10245aeb78e8509e9e7b9e888e2fc8eb6c"
xilinx-zynqmp = "master:fbb6d4f0affbaae78dbdf8cbdf43d1655b227843"
meta-virtualization =
"wr-10.19-20190603:e5d65550a5d532501ff245e7cd2a76cc415bf1bc"
meta-realtime =
"wr-10.19-20190408:9074810c117fdde9cec4058ac9c17c84f0f50420"
meta-mingw =
"wr-10.19-20190508:714437ac9ba52a4e022b3b199819dbb609d9952e"
wr-template = "master-wr:4f4e06413262e09e9eadbad427860218485bb3c3"
meta-yocto-bsp
meta-poky =
"wr-10.19-20190610:2826a58f6a0c103a3938ea5c797ea17923e10902"
meta-gplv2 =
"wr-10.19-20190610:168a5070bdf3bc45edb5bf2a1add9b7c081f5b64"
meta-efi-secure-boot
meta-encrypted-storage
meta-integrity
meta-signing-key =
"wr-10.19-20190610:e3ee3d8c9bd7033ccde8d5ce1e23893f3b215ea0"
meta-cloud-services =
"wr-10.19-20190610:31dfe4207c05faead77514e36cd8af8dabd334e6"
meta
meta-ids
meta-tpm
meta-tpm2 =
"wr-10.19-20190610:e3ee3d8c9bd7033ccde8d5ce1e23893f3b215ea0"
meta-openstack
meta-openstack-aio-deploy
meta-openstack-compute-deploy
meta-openstack-compute-test-config
meta-openstack-controller-deploy
meta-openstack-controller-test-config
meta-openstack-qemu
meta-openstack-swift-deploy =
"wr-10.19-20190610:31dfe4207c05faead77514e36cd8af8dabd334e6"
meta-intel =
"wr-10.19-20190610:e51ad5e08182f164077ca6a56a9220857043ad8e"
wrlinux-ovp = "master-wr:7fe21fafdfffcfb483bc5a4152fdfeb445b61e80"
meta-cgl-common =
"wr-10.19-20190508:bfd0554ad9734a210b636f9f5bdc307df19b1e79"
wrlinux-cgl = "master-wr:7fe21fafdfffcfb483bc5a4152fdfeb445b61e80"
meta-dpdk =
"wr-10.19-20190528:95dea5817da2b59a8ce4fa20be4bdcaef03e4e8c"
meta-intel-qat =
"wr-10.19-20190408:7a49ca357fc1a130d5de2d6862168901f7229b14"
meta-anaconda =
"wr-10.19-20190610:f0b82870061f17176c5873515749251a2e4bd7b4"
meta-overc
meta-cube =
"wr-10.19-20190520:4f7c0427acdf9ccab4e734840f1149840311a813"
meta-iot-cloud =
"wr-10.19-20190415:6e522eb46e35173eee5f9dd920bd32638aa00a11"
wrlinux-overc = "master-wr:7fe21fafdfffcfb483bc5a4152fdfeb445b61e80"
wrlinux-overc-cfg = "master-wr:639a999f5b83640b075c0306ea53b3da8913522d"
meta-selinux-dl = "master-wr:0e044fd49b16872966bf1d3c8e99d12df4bc6831"
meta-mingw-dl = "master-wr:8fc9becbb6f0d96b86b55969238e69fb9d8d3bb5"
meta-security-dl = "master-wr:d43ef6844eee8734f943f23e3e1a983b3094ca9e"
meta-efi-secure-boot-dl =
"master-wr:b79180d67c83c0fdf317c0583fa9a8e5fdb21b86"
meta-encrypted-storage-dl =
"master-wr:66323e9c6e55ecd52585172aab978d484c38038c"
meta-integrity-dl = "master-wr:c1f5e6d034937f78b4082c3109942d2544e902b7"
meta-ids-dl = "master-wr:3949731e192a988e10ca04845e205ea8582926af"
meta-tpm2-dl = "master-wr:1fb0ab512da1e4cd28fddd87ab9aa71b5ad18911"
wrlinux-dl = "master-wr:9a8ee391bed178c6edc275801806f3bab4e943c2"
meta-tpm-dl = "master-wr:a714909ea084fdb903c952f9d12036b720c57d30"
wrlinux-ovp-dl = "master-wr:b977985e906d8eebad4d84ac0d58e0f025f7cd48"
meta-cgl-common-dl = "master-wr:0e28920fa54ef3669ef254598376b8be17a8fc5c"
wrlinux-cgl-dl = "master-wr:347aa204485d9f7f5aeb839c79ba0bb864f34898"
meta-intel-dl = "master-wr:cf052f5407a4797b157a5fa05964c9190538749f"
meta-dpdk-dl = "master-wr:41b69bd8b5299303d4b58847d1c3761f68c27b38"
meta-intel-qat-dl = "master-wr:6076ccac2211ad64a4640fd1665c61ed577932a2"
meta-anaconda-dl = "master-wr:fe6dff64ca70491e762fa53ffea8099a70258b9a"
intel-socfpga-dl = "master-wr:1f850e1ad9c9d607a5e07703f730baa3a8f01c23"
meta-signing-key-dl = "master-wr:e4af4df72d5f6b0a9f561bc631bb8dde30f5715c"
meta-overc-dl = "master-wr:57300911316b043bbd665f129213cb61a862dffe"
meta-cloud-services-dl-2.7 =
"master-wr:fa850191b711968d778e0eabd990d415eaa7b5e3"
meta-filesystems-dl-2.7 =
"master-wr:9142e7c86447011f116261d7339c7991ae886e21"
meta-gnome-dl-2.7 = "master-wr:62544355e093b12dff8d23c491459db2295cb048"
meta-gplv2-dl-2.7 = "master-wr:659295af85544c098037894c68f41cf2d5e5f66c"
meta-initramfs-dl-2.7 = "master-wr:a478b17a139846430ee6ab5df979a18bcd78a7f7"
meta-multimedia-dl-2.7 =
"master-wr:627de73ccf29212ad522852450f843f968be706b"
meta-networking-dl-2.7 =
"master-wr:ff103503a439ebca142b6d0df1e9480431bcca89"
meta-oe-dl-2.7 = "master-wr:f94b042d5fbed4b90756c1bf6e9b4e38aa5d5302"
meta-openstack-dl-2.7 = "master-wr:932feacb8c20a263da8ab3a5629da7a0fa0d0f2f"
meta-perl-dl-2.7 = "master-wr:0ed5512cb5483208ea64200dbb767ef276b17e50"
meta-python-dl-2.7 = "master-wr:c797ddb11da1c1f56735ac915b8156a9ccfced30"
meta-realtime-dl-2.7 = "master-wr:9507da614b0e2899a7a6845642cff40a6590d524"
meta-virtualization-dl-2.7 =
"master-wr:05fae9d3dad2fefcc54d059c14a06ce0295140fa"
meta-webserver-dl-2.7 = "master-wr:4d1835fde6680cfdb8ba25572c175d386f59d3cb"
meta-xfce-dl-2.7 = "master-wr:5683cae374e8049f665de52b854a5ddab8193e24"
oe-core-dl-2.7 = "master-wr:8917419533b43b10a9938e2368084649f55ddd9c"
local = "master:fbb6d4f0affbaae78dbdf8cbdf43d1655b227843"
NOTE: Fetching uninative binary shim from
file:///buildarea1/zchen/build-19/wr19-06-14-arm64/layers/wrlinux/files/uninative-tarballs/ed0ac07c710b711925cb976685dd855fb1d442dd840d00194751c18bf480c4ed/x86_64-nativesdk-libc.tar.xz;sha256sum=ed0ac07c710b711925cb976685dd855fb1d442dd840d00194751c18bf480c4ed
----------------------------------------------------------------------
DISTRO wrlinux-std-sato is deprecated, use wrlinux-graphics instead.
----------------------------------------------------------------------
Initialising tasks: 100%
|##########################################################################################################################################################################|
Time: 0:00:00
Sstate summary: Wanted 79 Found 0 Missed 79 Current 0 (0% match, 0%
complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 522 tasks of which 0 didn't need to be
rerun and all succeeded.
Summary: There were 5 WARNING messages shown.
zchen at pek-lpggp4:$ ls
bitbake-cookerdaemon.log cache conf downloads README_templates
sstate-cache tmp-glibc
zchen at pek-lpggp4:$ cd tmp-glibc/work-shared/
gcc-9.1.0-r0/ xilinx-zynqmp/
zchen at pek-lpggp4:$ cd tmp-glibc/work-shared/xilinx-zynqmp/kernel-source/
zchen at pek-lpggp4:$ ls
arch certs CREDITS Documentation fs init Kbuild kernel
LICENSES Makefile net samples security tools virt
block COPYING crypto drivers include ipc Kconfig lib
MAINTAINERS mm README scripts sound usr
zchen at pek-lpggp4:$ git branch
master
standard/arm-versatile-926ejs
standard/base
standard/beagleboard
standard/beaglebone
standard/edgerouter
standard/fsl-mpc8315e-rdb
standard/intel
standard/intel-x86
standard/mti-malta32
standard/mti-malta64
standard/preempt-rt/base
standard/preempt-rt/intel
standard/preempt-rt/intel-x86
standard/preempt-rt/rebase
standard/qemuarm64
standard/qemuarma15
standard/qemuppc
standard/tiny/base
standard/tiny/common-pc
* standard/xilinx-zynqmp
Cheers,
Zumeng
On 6/13/19 10:20 PM, Bruce Ashfield wrote:
> Sorry about that. I was traveling this week, and kept forgetting to
> create the branch.
>
> It should be in place now.
>
> Bruce
>
> On Thu, Jun 13, 2019 at 3:48 AM Zumeng Chen <zchen at windriver.com> wrote:
>> Ping ....
>>
>> On 6/11/19 9:40 AM, Zumeng Chen wrote:
>>
>> Hi Bruce,
>>
>> I just finished insane check to build xilinx-zynqmp machine with core-image-sato, all passed with boot process.
>>
>> Could you please help me to create a branch like that standard/xilinx-zynqmp in the following git repo. in convenient your time, just directly branch out from origin/standard/base, thanks~
>>
>> git://git.yoctoproject.org/linux-yocto-dev
>>
>>
>> Cheers,
>>
>> Zumeng
>>
>> On 6/11/19 7:37 AM, Zumeng Chen wrote:
>>
>>
>> On 6/10/19 9:37 PM, Bruce Ashfield wrote:
>>
>> On Sun, Jun 9, 2019 at 8:00 PM Zumeng Chen <zchen at windriver.com> wrote:
>>
>> Sounds I like mean, no, I just talk the reality, Xilinx did like the
>> following:
>>
>> https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-bsp/recipes-kernel/linux/xilinx-kmeta/bsp
>>
>> I think they have a reason to share zynq-7000 series hardware, which
>> gears to the related hardware
>>
>> features, and the way to create dts(a relative complicated process)
>> corresponding to the hdl related
>>
>> features partly as well. And they just want to put zynqmp(arm64) into
>> recipes-kernel/linux/xilinx-kmeta/bsp/xilinx,
>>
>> As you can see, they have almost little in common in hardware features.
>>
>>
>> The reality here I said is about yocto project has not these related
>> ecosystem to create these whole thing for
>>
>> xilinx series(including zynq7000 32bit and zynqmp 64bit), like dts, hdl,
>> BOOT.BIN etc. there really are a bunch
>>
>> of Xilinx things.
>>
>>
>> So do we still want to following their SDK? If yes, fine, just help me
>> to merge zynqmp part from meta-xilinx, I'll take care the rest.
>>
>> I'm actually fine with an approach like we are taking here. Come up
>> with something that works purely with linux-yocto, and then we can
>> start factoring and grouping the fragments with the help of people
>> closer to the h/w.
>>
>> In particular as more Xilinx proprietary parts are open sourced, we'll
>> have the opportunity to tweak the configuration fragments to support
>> them properly/fully.
>>
>> We do want the fragments in the centralized kernel-cache, just as long
>> as they are appropriated factored/grouped under a xilinx/ subdir where
>> it makes sense, and have more generic feature groupings available to
>> be shared in the more common directories.
>>
>> What we have is a good start to that goal, so I'll get it merged and
>> we can start iterating on it in tree.
>>
>>
>>
>> Thanks Bruce, highly appreciated :)
>>
>>
>> Cheers,
>>
>> Zumeng
>>
>>
>> Bruce
>>
>>
>> Cheers,
>>
>> Zumeng
>>
>>
>> On 6/6/19 2:55 PM, Zumeng Chen wrote:
>>
>> Yes, I checked it, it seems only for zynq 7000 and its special
>> interfaces. I bet
>>
>> the original author didn't mean to share something for both arm64
>> and 32 :)
>>
>> When I created the structure I had intended for it to include the
>> zynqmp related configs. I even had some yocto-kernel-cache patches for
>> it at the time, but zynqmp has changed quite a bit since those initial
>> patches. Most of those configs still live in meta-xilinx though (some
>> are specific to the linux-xlnx kernel).
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/tree/meta-xilinx-bsp/recipes-kernel/linux/xilinx-kmeta
>>
>>
>> I would highly recommend keeping the xilinx bsp configs together under
>> the bsp/xilinx/ directory. And try to reuse the existing configs where
>> possible or splitting some parts of them out to make common configs
>> since zynq and zynqmp share a number of common drivers.
>>
>>
>> Negative, try to see what had done in the past, a very little can
>> re-used. And I suspect
>>
>> did you even how many features they are sharing.
>>
>> I don't think it's worth. To be honestly, they have totally the
>> different app scenario.
>>
>> Cheers,
>>
>> Zumeng
>>
>> Regards,
>> Nathan
>>
>> And for those common things, I guess some of them might be included
>> by our
>>
>> rootfs build system.
>>
>>
>> sense to locate these fragments there, and to factor out some common
>> configs. I see some of the issues I'm pointing out here are in the
>> existing fragments as well, so there's an opportunity for some low
>> effort fixups.
>>
>> +
>> +CONFIG_PCI=y
>> +CONFIG_PCI_MSI=y
>> +CONFIG_PCI_MSI_IRQ_DOMAIN=y
>> +CONFIG_PCIE_XILINX_NWL=y
>> +CONFIG_PCIEPORTBUS=y
>> +CONFIG_PCIE_XDMA_PL=y
>> +
>> +#CPU ilde and freq
>> +CONFIG_CPU_IDLE=y
>> +CONFIG_ARM_CPUIDLE=y
>> +CONFIG_CPU_FREQ=y
>> +CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
>> +CONFIG_CPU_FREQ_GOV_USERSPACE=y
>> +CONFIG_CPUFREQ_DT=y
>> +CONFIG_CPUFREQ_DT_PLATDEV=y
>>
>> These are also not tied to h/w. We already have a
>> features/power/intel.cfg fragment. Can you relocate these to a zynqmp
>> or xilinx fragment and put it along side of the existing ones ?
>>
>> I'll try it with a nice way.
>>
>> +
>> +# CAN Device Drivers
>> +#
>> +CONFIG_CAN=y
>> +CONFIG_CAN_DEV=y
>> +CONFIG_CAN_XILINXCAN=y
>> +
>> +CONFIG_MTD=y
>> +CONFIG_MTD_OF_PARTS=y
>> +CONFIG_MTD_BLKDEVS=y
>> +CONFIG_MTD_BLOCK=y
>> +CONFIG_MTD_M25P80=y
>> +CONFIG_MTD_SPI_NOR=y
>> +# CONFIG_JFFS2_FS_WRITEBUFFER is not set
>> +# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set
>> +
>> +CONFIG_BLK_DEV_SD=y
>> +CONFIG_ATA=y
>> +CONFIG_SATA_AHCI=y
>> +CONFIG_AHCI_CEVA=y
>> +CONFIG_NETDEVICES=y
>> +
>> +CONFIG_OF=y
>> +CONFIG_OF_MDIO=y
>> +CONFIG_ETHERNET=y
>> +CONFIG_NET_CADENCE=y
>> +CONFIG_MACB=y
>> +CONFIG_MACB_EXT_BD=y
>> +
>> +CONFIG_PHYLIB=y
>> +CONFIG_XILINX_PHY=y
>> +
>> +CONFIG_PHY_XILINX_ZYNQMP=y
>> +CONFIG_FIXED_PHY=y
>> +CONFIG_DEVMEM=y
>> +
>> +CONFIG_SERIAL_EARLYCON=y
>> +CONFIG_SERIAL_CORE=y
>> +CONFIG_SERIAL_CORE_CONSOLE=y
>> +CONFIG_SERIAL_XILINX_PS_UART=y
>> +CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
>> +#
>> +CONFIG_I2C=y
>> +CONFIG_I2C_MUX=y
>> +CONFIG_I2C_MUX_PCA954x=y
>> +CONFIG_I2C_MUX_REG
>> +CONFIG_I2C_CADENCE=y
>> +CONFIG_I2C_XILINX=y
>> +CONFIG_EEPROM_AT24=y
>> +
>> +
>> +CONFIG_SPI=y
>> +CONFIG_SPI_MASTER=y
>> +CONFIG_SPI_CADENCE=y
>> +CONFIG_SPI_XILINX=y
>> +CONFIG_SPI_ZYNQMP_GQSPI=y
>> +
>> +CONFIG_GPIOLIB=y
>> +CONFIG_GPIO_DEVRES=y
>> +CONFIG_OF_GPIO=y
>> +CONFIG_GPIO_SYSFS=y
>> +CONFIG_GPIO_XILINX=y
>> +CONFIG_GPIO_PCA953X=y
>> +CONFIG_GPIO_PCA953X_IRQ=y
>> +CONFIG_GPIO_ZYNQ=y
>> +
>> +CONFIG_POWER_RESET=y
>> +CONFIG_SENSORS_INA2XX=y
>> +CONFIG_WATCHDOG=y
>> +CONFIG_CADENCE_WATCHDOG=y
>> +CONFIG_XILINX_WATCHDOG=y
>> +
>> +CONFIG_USB=y
>> +CONFIG_USB_XHCI_HCD=y
>> +CONFIG_USB_DWC3=y
>> +CONFIG_USB_DWC3_OF_SIMPLE=y
>> +CONFIG_USB_OTG=y
>> +CONFIG_USB_OTG_FSM=m
>> +CONFIG_USB_GADGET=y
>> +CONFIG_USB_GADGET_XILINX=y
>> +CONFIG_USB_ETH=m
>> +CONFIG_USB_MASS_STORAGE=m
>>
>> bsp/xilinx/soc/drivers-zynq.cfg has some of these already. Can we
>> update and then include that fragment ?
>>
>> This is a nasty cfg. I think you don't want to use it. But we can
>> remove them since we have already include usb-mass-storage.scc
>>
>> +
>> +CONFIG_MMC=y
>> +CONFIG_MMC_BLOCK=y
>> +CONFIG_MMC_SDHCI=y
>> +CONFIG_MMC_SDHCI_PLTFM=y
>> +CONFIG_MMC_SDHCI_OF_ARASAN=y
>> +
>> +CONFIG_EDAC=y
>> +CONFIG_EDAC_MM_EDAC=y
>> +CONFIG_EDAC_SYNOPSYS=y
>> +CONFIG_EDAC_ZYNQMP_OCM=y
>> +
>> +CONFIG_RTC_CLASS=y
>> +CONFIG_RTC_HCTOSYS=y
>> +CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
>> +CONFIG_RTC_INTF_SYSFS=y
>> +CONFIG_RTC_DRV_ZYNQMP=y
>> +
>> +CONFIG_DMADEVICES=y
>> +CONFIG_DMA_ENGINE=y
>> +CONFIG_DMA_OF=y
>> +CONFIG_CMA=y
>> +CONFIG_DMA_CMA=y
>> +CONFIG_CMA_SIZE_MBYTES=256
>>
>> Similar to my USB comment, I'm seeing some of this in existing
>> fragments, can we update those fragments and then just include them ?
>>
>> En, I'll clean of them, some of them are redundant. But I'll keep
>> CONFIG_DMA_CMA=y since:
>>
>> grep -rni 'CONFIG_DMA_CMA=y' ./
>> ./bsp/beaglebone/beaglebone.cfg:47:CONFIG_DMA_CMA=y
>> ./bsp/xilinx-zynqmp/xilinx-zynqmp.cfg:140:CONFIG_DMA_CMA=y
>> ./bsp/intel-x86/intel-x86.cfg:319:CONFIG_DMA_CMA=y
>>
>>
>> +
>> +CONFIG_XILINX_AXIDMA=y
>> +CONFIG_XILINX_AXICDMA=y
>> +CONFIG_XILINX_ZYNQMP_DMA=y
>> +CONFIG_XILINX_DMA=y
>> +
>> +CONFIG_UIO=y
>> +CONFIG_UIO_XILINX_APM=y
>> +CONFIG_VIRTIO=y
>> +CONFIG_COMMON_CLK=y
>> +CONFIG_COMMON_CLK_SI570=y
>> +CONFIG_COMMON_CLK_ZYNQMP=y
>> +CONFIG_CLKSRC_OF=y
>> +CONFIG_IOMMU_API=y
>> +CONFIG_IOMMU_SUPPORT=y
>> +CONFIG_OF_IOMMU=y
>> +CONFIG_ARM_SMMU=y
>> +CONFIG_ARM_SMMU_V3=y
>> +#
>> +CONFIG_REMOTEPROC=m
>>
>> remotproc doesn't belong in a BSP fragment.
>>
>> remove it.
>>
>>
>> +CONFIG_ZYNQMP_R5_REMOTEPROC=m
>> +
>> +CONFIG_STAGING=y
>> +CONFIG_SOC_XILINX_ZYNQMP=y
>> +CONFIG_ZYNQMP_PM_DOMAINS=y
>> +CONFIG_PM_GENERIC_DOMAINS=y
>> +CONFIG_ZYNQMP_PM_API=y
>> +CONFIG_IRQCHIP=y
>> +CONFIG_ARM_GIC=y
>> +CONFIG_ARM_GIC_V3=y
>> +CONFIG_ARM_GIC_V3_ITS=y
>> +
>> +CONFIG_IIO=y
>> +CONFIG_XILINX_AMS=y
>> +CONFIG_XILINX_FCLK=y
>> +
>> +CONFIG_FPGA=y
>> +CONFIG_FPGA_MGR_ZYNQMP_FPGA=y
>> +CONFIG_NVMEM_ZYNQMP=y
>> +CONFIG_FPGA_REGION=y
>> +CONFIG_FPGA_BRIDGE=y
>> +
>> +CONFIG_RESET_CONTROLLER=y
>> +CONFIG_ZYNQMP_RESET_CONTROLLER=y
>> +
>> +CONFIG_REGULATOR=y
>> +CONFIG_REGULATOR_FIXED_VOLTAGE=y
>> +CONFIG_REGULATOR_GPIO=y
>> +
>> +
>> +CONFIG_FB=y
>> +CONFIG_FB_XILINX=y
>> +CONFIG_MEDIA_SUPPORT=y
>> +CONFIG_MEDIA_CONTROLLER=y
>> +CONFIG_MEDIA_CAMERA_SUPPORT=y
>> +CONFIG_VIDEO_DEV=y
>> +CONFIG_VIDEO_V4L2_SUBDEV_API=y
>> +CONFIG_VIDEO_V4L2=y
>> +CONFIG_V4L_PLATFORM_DRIVERS=y
>> +CONFIG_VIDEO_XILINX=y
>> +CONFIG_VIDEO_XILINX_CFA=y
>> +CONFIG_VIDEO_XILINX_CRESAMPLE=y
>> +CONFIG_VIDEO_XILINX_HLS=y
>> +CONFIG_VIDEO_XILINX_REMAPPER=y
>> +CONFIG_VIDEO_XILINX_RGB2YUV=y
>> +CONFIG_VIDEO_XILINX_SCALER=y
>> +CONFIG_VIDEO_XILINX_SWITCH=y
>> +CONFIG_VIDEO_XILINX_TPG=y
>> +CONFIG_VIDEO_XILINX_VTC=y
>>
>> The CONFIG_FB and related fragments can be separated out into a
>> feature fragment and then included. That's what we've done with other
>> FB features.
>>
>> En, yeah, these parts are BSP related other than this just one
>> CONFIG_FB, can we live with these as other BSPs did?
>>
>>
>> +
>> +CONFIG_DRM=y
>> +CONFIG_DRM_KMS_HELPER=y
>> +CONFIG_DRM_KMS_FB_HELPER=y
>> +CONFIG_DRM_FBDEV_EMULATION=y
>> +CONFIG_DRM_BRIDGE=y
>> +CONFIG_DRM_XILINX=y
>> +CONFIG_HDMI=y
>> +CONFIG_XILINX_FRMBUF=y
>> +CONFIG_XILINX_DPDMA=y
>> +CONFIG_XILINX_DMA_ENGINES=y
>> +
>> +CONFIG_FW_LOADER=y
>> +
>> +CONFIG_TIGON3=m
>> +CONFIG_E1000E=m
>>
>> Overall, this looks good to me. It just needs a bit of tweaking for
>> reuse.
>>
>> OK, I'll send v2 with sanity test, thanks Bruce.
>>
>>
>> Cheers,
>>
>> Zumeng
>>
>> Bruce
>>
>> diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp.scc
>> b/bsp/xilinx-zynqmp/xilinx-zynqmp.scc
>> new file mode 100644
>> index 0000000..81696c2
>> --- /dev/null
>> +++ b/bsp/xilinx-zynqmp/xilinx-zynqmp.scc
>> @@ -0,0 +1,7 @@
>> +include cfg/usb-mass-storage.scc
>> +include cfg/fs/flash_fs.cfg
>> +include features/hugetlb/hugetlb.scc
>> +# enable the ability to run 32 bit apps
>> +include arch/arm/32bit-compat.scc
>> +
>> +kconf hardware xilinx-zynqmp.cfg
>> --
>> 2.7.4
>>
>> --
>> - Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end
>> - "Use the force Harry" - Gandalf, Star Trek II
>>
>> --
>> _______________________________________________
>> linux-yocto mailing list
>> linux-yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/linux-yocto
>>
>>
>>
>
More information about the linux-yocto
mailing list