RE: Follow up on 4 Gig of DDR on MPC8548E

quoted

apparently after more investigations - it looks like there is =

something in the ext2 driver code

quoted

that is mal-adjusted....I haven't talked to the guy today who was =

looking at that - but the ext2

quoted

driver code that was openning a 'virtual file' / console - had some =

problems mapping that

quoted

space - again, my gut is telling me more stronger there is a problem =

with signed/unsigned...

quoted

now deeper in the ext2 code...

I very much doubt there is a signed/unsigned issue in ext2 or =

elsewhere...

You have CONFIG_HIGHMEM ? What are your setting for KERNELBASE and =

PAGE_OFFSET ?

Ben,
=20
I am sorry it I alluded to ext2 code itself having a signed/unsigned =
problem -=20
just that the problem was manifesting itself inside the ext2 code in a =
very=20
strange way ...with something that I guessed below it that was violating =

a signed/unsigned API....
=20
and I was wrong with this hunch (gotta check my hunch meter)...
It was a nuance in the configuration of inbound windows for PCI/PEX=20
that was dribbling onto the memory that was consistently being i/o =
mapped
to the ext2 driver - which then got confused and bailed completely.
=20
We now have it working as we want it to with all 4 GIG of=20
DDR working as we want it.
=20
Thank you for pushing us to push through the hunch and get to the=20
root cause. It was a tough one to find.
=20
Tom
=20