On Tue, May 3, 2016 at 3:38 AM, Manjukumar Harthikote Matha <[email protected]> wrote: > Hi Nathan, > > On 05/02/2016 08:12 AM, Nathan Rossi wrote: >> >> On Tue, Apr 26, 2016 at 11:40 AM, Manjukumar Matha >> <[email protected]> wrote: >>> >>> Use Xilinx kernel by default for zynqmp. >> >> >> Hi Manju, >> >> Could you elaborate more on why this change is required? >> >> I would really like to keep the default as linux-yocto, but specific >> machines can select linux-xlnx when they need drivers/device-trees >> that are not yet in linux-yocto/mainline. >> > The only motivation is that Xilinx boards have better support in Xilinx > Linux tree or Xilinx u-boot. Also, the include file is to setup default > configurations for Xilinx board(s).
The Xilinx vendor tree is great for driver support specific to Xilinx. But it can be problematic for long term projects (for a variety of reasons), and as such it makes a more sense for users to actively pick it for specific reasons rather than to default to it without specifically needing the support it provides. It was also my understanding that the position Xilinx has for these vendor trees is such that the Xilinx vendor kernel/u-boot moves at a pace which allows for adding early support for Xilinx drivers/etc. which may not yet be suited for mainline submission or long term product designs. Also don't confuse the "machine-xilinx-*.inc" to be referring to Xilinx boards specifically, this refers to machines/boards in the meta-xilinx layer and potentially outside of the layer too. If you need linux-xlnx and or u-boot-xlnx specifically for the ZCU102 the best way to set this up is to set the preferred provider in the machines .conf. Regards, Nathan -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
