linux/meta-xilinx.git/recipes-bsp/device-tree, branch pyro

zybo-linux-bd-zynq7: Change gem0 phy to match kernel definition

2017-06-08T13:03:05+00:00

Change the device tree for the gem0 phy to match that of the kernel device tree for ZYBO. This removes the compatible string and uses the phy address of 0 (broadcast). This lets the kernel auto detect the phy since there are no other devices on the MDIO bus for gem0. Signed-off-by: Nathan Rossi

device-tree: Improve, clean up and remove MACHINE_DEVICETREE

2017-04-26T05:33:30+00:00

This change improves and does a number of clean up to the device-tree recipe. This includes adding support for building overlays, default inclusion of kernel device tree sources, updated license value and general clean ups to the logic. This change also removes the support for MACHINE_DEVICETREE, and additionally the now unused xilinx-utils.bbclass. Note: In order to support overlays dtc version 1.4.3 or newer is needed, currently in oe-core only 1.4.2 is available. Signed-off-by: Nathan Rossi

device-tree.bbappend: Move use of MACHINE_DEVICETREE to SRC_URI

2017-04-26T05:33:30+00:00

Remove the use of MACHINE_DEVICETREE for providing sources to device-tree, instead provide the device tree sources as SRC_URI entires. Whilst this was already being done automatically by the MACHINE_DEVICETREE logic it also created a non-standard way of providing the device tree sources to the recipe. The setup of SRC_URI is done via the use of a device-tree.bbappend instead of directly in the device-tree.bb recipe itself. This is for two reason, separation of the source from the build logic as well as to provide an example for how a user can extend the device-tree recipe to provide custom device tree sources in their layer. This change also moves the paths to the sources around, this is to align the names of the directories to match the OVERRIDES so that when expanding the file paths it will search the subdirs based on the OVERRIDES or machine names. Signed-off-by: Nathan Rossi

device-tree/microzed-zynq7.dts: Replace with kernel source version

2017-03-24T10:50:49+00:00

Replace the existing device tree content with the content of the zynq-microzed.dts from the kernel source. Specifically based on commit df2f3c48b9cd51e2612a1598342769d09d849f39. This resolves the issues with the ethernet phy as well as adding pinctrl for USB. Signed-off-by: Nathan Rossi

device-tree: Remove zynq7-base.dtsi

2017-02-01T12:40:20+00:00

This include has been deprecated for two releases. It is now completely obsolete and being removed. Remove the deprecation warning message as well. Signed-off-by: Nathan Rossi

kc705-microblazeel: Update to 2016.3 Xilinx design

2016-12-04T10:50:39+00:00

Change kc705-microblazeel to reflect v2016.3 Xilinx tools. Signed-off-by: Manjukumar Matha Signed-off-by: Nathan Rossi

zybo-linux-bd-zynq7: Update the device-tree for linux-xlnx v4.6

2016-11-19T11:36:36+00:00

Update the bindings where required for the v4.6 linux-xlnx kernel. These changes are incompatible with older linux-xlnx kernels due to changes in the Xilinx DRM bindings. Signed-off-by: Nathan Rossi

qemu* -> qemu-: Rename QEMU machines

2016-10-26T16:15:28+00:00

Rename the QEMU machines to match the -- convention. QEMU only machines no longer need to be named qemu*. Note for qemuzynq it is special in that it does not model a board, as such it has no board in the name being just 'qemu-zynq7'. This updates the README.md to match the new machine names. Additional update all occurrences of the qemu* machines Signed-off-by: Nathan Rossi Reviewed-by: Alistair Francis

device-tree: Remove old runqemu compatibility outputs

2016-10-11T11:10:52+00:00

Remove the symlinking of ${KERNEL_IMAGETYPE}-${DTS}.dtb for compatibility with runqemu. This is now handled with the machines QB_DTB variable. Signed-off-by: Nathan Rossi Reviewed-by: Alistair Francis

device-tree: Use deploy class to handle shared state

2016-09-28T13:16:11+00:00

Use the deploy class and DEPLOYDIR to ensure that deploy objects are populated into the shared state cache. This ensures that the objects are also correctly populated into the output deploy directory regardless of whether the do_deploy task is executed. Signed-off-by: Nathan Rossi