thoughts and questions on 8xx patches

Robert P. J. Day rpjday at
Tue Sep 21 22:56:58 EST 2004

On Tue, 21 Sep 2004, Wolfgang Denk wrote:

> In message <Pine.LNX.4.60.0409210808250.9449 at> you wrote:
>> from list discussions some time back, i already gave up on the idea of
>> the configuration being able to detect the exact processor and taking
>> that into account.  we've already established that, and i'm happy with
>> that.
> OK.
>> all i'm suggesting now is a drop down choice menu of known patches
>> relevant to that architecture, that's all.  in some cases, there would
>> be two choices, as in:
>>  	[ ] I2C/SPI for 850
>>   	[ ] I2C/SPI for 8xx (non-850)
> Plus there is also the case of "need to relocate parameter RAM  on  a
> MPC852/859/866/...  processor".  In  this  case  no microcode patch i
> sneeded, and the current code will crash the system.
> More cases may be necessary.
>> and, unless i'm reading this badly, that's the entire list.  all of
> No, it's  not.  It  will  not  work  on  most  of  the  newer  MPC8xx
> processors.
>> so ... why is this such an objectionable thing?
> Because it is (1) incomplete and (2) broken.

ok, so i'll back off and ask one more question.  even without a 
*current* list of microcode patches, is there any value to even 
building in the infrastructure for such a thing in the config menu, so 
that patches can be added quickly and (relatively) painlessly as they 
come up?  and old ones tossed out as they become obsolete?  if there's 
no value to this at all, i'll just let it drop and move on.


More information about the Linuxppc-dev mailing list