On Apr 22, 2009, at 1:16 PM, Scott Wood wrote:
Kumar Gala wrote:
What "we care about" at this point is irrelevant, given the PITA
it would be to change the device trees (or u-boot) that are
already in use once we do begin to care.
Which is exactly why I didn't put it in the .dts right now.
???
Today we know NO code exists that cares about "fsl,elbc-1.2". Once
someone adds such code they can also update the .dts to match it.
DTS files and firmware are *MUCH* harder to update once they're out
there than the kernel. Why such opposition to using an appropriate
compatible?
Because I want to avoid make the decision right now. We are on rev1.x
silicon and I want to avoid greatly having to spawn a new .dts just
for "fsl,elbc-1.2.1" that has some errata fix in it. If dtc was
smarter and I had less duplication between the 40-50 .dts we have for
our various parts I wouldn't care that match.
Is there anything in the p2020ds u-boot patches to set the elbc
version, or was that just a brush-off?
I was hoping that Poonam would look at doing that, but there isn't
anything right now.
I can put out some code for u-boot to address the specific elbc issue
if that will resolve this.
- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
