Xilinx Home
Embedded Linux
Register  ·  Sign In  ·  Help
Jump to Page:   1
  Reply   Reply  

Using Xilinx Open Source Linux with EDK 11.1, device trees
Options    Options  
linnj
Expert Contributor
Posts: 354
Registered: 09-10-2008


linnj

Message 1 of 1

Viewed 1,258 times


There are new core versions in EDK 11.1 and a new device tree generator is needed to deal with them.

 

The drivers in the kernel have versions in them to say what h/w they are compatible with.  We changed the device tree generator so that it would deal with some backward compatibility so we don't have to change the drivers every time there's new h/w.  Since some drivers are in the mainline kernel changing them often is not a quick and painless task.

 

Thanks,

John

 

git.xilinx.com Git - device-tree.git/commit

author John Bonesio <john.bonesio@xilinx.com>
  Wed, 25 Feb 2009 02:43:03 +0000 (18:43 -0800)
committer John Bonesio <john.bonesio@xilinx.com>
  Wed, 25 Feb 2009 02:43:03 +0000 (18:43 -0800)
commit a3ba6a7ceb9bc2654847f27ddb4710b494400083
tree e99a2aad179b6a356a82f59a5ce71ac611a5381d
parent 5893e28974b3b692c7e1ebb7b888c072a5abf891
device-tree: Enhancement: "compatible = " is now a list

To avoid having to update the linux kernel every time a Xilinx core changes
it's version string, with this change, the generator now generates
"compatible=" lines with:
        1) the core's actual version
        2) the oldest core version that is software compatible with the core's
           actual version.
Example:
        compatible = "xlnx,xps-intc-2.00.a", "xlnx,xps-intc-1.00.a";

There are a few rules that go with this:
1) The oldest core version listed must be a version that is already supported
   by the linux kernel, or this change doesn't help.
2) The versions are considered compatible if the driver/kernel code made for
   the older version will work with the core's actual version. What this means
   is that the newer core might have additional features, but the core must
   be operable by the driver/kernel using only the older feature set.

This feature is implemented by using a static table in the tcl script. At this
time there does not seem to be a good  method for determining this using
automation.

Signed-off-by: John Bonesio <john.bonesio@xilinx.com>
bsp/device-tree/data/device-tree_v2_1_0.tcl  
 

 

 

 


 

John Linn

Kudos!
04-10-2009 03:13 PM
Jump to Page:   1