On Mon, May 12, 2008 at 1:10 PM, Stephen Neuendorffer <[EMAIL PROTECTED]> wrote: > > The best possibility that I see is glopping the compatibility > information about what cores are compatible with which drivers and > generating something. This is moderately better than blindly treating > all cores with the same major version as interface compatible, but still > has the potential to blindly declare that core versions are compatible > when they are not really compatible.
That's okay, the device tree conventions provide for that uncertainty. If compatible includes both the *exact* version and the oldest known *compatible* version (the one the drivers know about) then we're in the situation where 99% of the time it just works. For the 1% of the time when mistakes are made we still have the necessary information to write exceptions in the code to work around bad data. This means code only needs to changes when mistakes are discovered, not for every IP core uprev. > I *really* don't want to put this into the device tree generator on a > case-by-case basis, so unless there is something that can be generated > from whatever meta-information EDK has, I think we're going to have to > just have the explicit versions in the drivers for the time being. Can we post process the generated device tree with a table of known compatibility strings (or regexps) for adding the older compatible values? I don't expect the list will be particularly long or hard to maintain and the code to do so should be trivial. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
