[PATCH] powerpc: consolidate mpc83xx platform files

[Geoff Thorpe]

Kumar Gala wrote:

>It adds code to all those people that don't need it just so we don't  
>duplicate a few lines of source code.
>  
>

Sounds like you're describing the raison d'être for device-trees though? 
After all, if you want to build a kernel that supports these minor h/w 
variations depending on the device-tree it's booted with, then the "few 
lines of duplicated source code" you're talking about would also "add 
code to all those people that don't need it".

Kumar Gala also wrote:

>On Dec 12, 2006, at 4:41 PM, Scott Wood wrote:
>  
>
>>And an 83xx-generic machine description does not stop them from  
>>doing so.  "Generic" does not mean "universal".  It means "there's  
>>nothing special about this board".  If you need board-specific code  
>>in the kernel, then don't label it generic.
>>    
>>
>
>But what value does this have?  83xx, and the majority of freescale's  
>devices are not put into something as standard as a desktop computer.
>  
>

Then what value do device-trees have at all? Why require new code for 
new h/w if it's technically unnecessary? If I've understood correctly (I 
confess to not having followed all of the discussion nor the finer 
technical points), this would require new code to find its way 
"upstream" (to whoever/wherever/whatever that means) from freescale and 
then downstream to it's user before the h/w is supported, when this 
situation is precisely what device-trees apparently ought to resolve.

Maybe I'm missing something (quite possible). Ben's objection seemed to 
be one of naming, but yours seems to be that new h/w should require new 
code because it's not wintel fodder for desktop grannies? So why bother 
separating h/w description from the compiled kernel in the first place?

Cheers,
Geoff