> -----Original Message-----
> From: Jonathan Day [mailto:firstname.lastname@example.org]
> Sent: Tuesday, September 19, 2006 11:07 AM
> To: Mark E Mason; email@example.com
> Subject: RE: Kernel debugging contd.
> I would guess I can fix the problem by simply
> cutting-and-pasting the SB1 codes back in and then
> changing the calls. (If there's a patch for this out
> there, that would be even easier...! :)
> Out of curiosity, any idea why the code was switched
> to a generic implementation?
Ralf will have to answer that one, but I believe it was caught up in a
general housecleaning of the MMU/cache code.
> --- Mark E Mason <firstname.lastname@example.org> wrote:
> > Hello,
> > FWIW - this is the same place my boards are hanging
> > (right after freeing
> > kernel memory). I'd tracked it down to the commit
> > that changed the
> > cache/page handling for the sibyte parts from the
> > sb1 specific to the
> > generic codes -- but haven't found time to look into
> > it further as yet.
> > /Mark
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around