unable to boot Linux smoothly while there is physical address 0xc0000000.

[Rob Landley]

On Tuesday 07 March 2006 2:18 am, stanliao at globalunichip.com wrote:
> Hi All,
>
> Our system has physical address from 0x3c000000 ~ 0x3effffff and from
> 0xc0000000~0xc0100000.

From that sentence alone, there is no _possible_ way the rest of this message 
could be a BusyBox issue.

> We put linux kernel on 0x3c008000

Those are the people to talk to.

> and the compressed ramdisk at 0x3c800000, 
> the system
> runs without problems. While the 0xc0000000~0xc0100000 is enabled, problem
> raised.

You're writing your own bootloader?

> By my 
> understanding, the virtual address of our linux kernel occupy 0xc0000000
> ~0xffffffff (from the System.map
> and the vector table address).

Only the kernel should ever know the difference between virtual and physical 
addresses.

> Excuse me, would the physical address 0xc0000000~0xc0100000 impact the
> linux kernel (suppose that
> the system has no error in hardware design)?

Why don't you ask the linux-kernel guys?

> Best Regards,
> Stan Liao

Rob
-- 
Never bet against the cheap plastic solution.