From: Xianghua Xiao <x.xiao@freescale•com>
To: Scott Coulter <scott.coulter@cyclone•com>, linuxppc-embedded@ozlabs•org
Subject: Re: booting Linux 2.6.15 using a ramdisk and greater than 512MB of DRAM
Date: Fri, 09 Jun 2006 14:46:19 -0500 [thread overview]
Message-ID: <4489D00B.7070800@freescale.com> (raw)
In-Reply-To: <43EB80E07C42E1408726E4905FB96B0466C6C1@CYBORG3.cyclone.com>
I think it's a u-boot 'feature' and has nothing to do with the kernel.
xianghua
Scott Coulter wrote:
>Xianghua,
>
>That seems to have worked.
>
>Do you think that this is worth investigating?
>
>Thanks,
>
>
>Scott
>
>
>
>
>
>
>___________________________________________________________________
>
> Scott N. Coulter
> Senior Software Engineer
>
> Cyclone Microsystems
> 370 James Street Phone: 203.786.5536 ext. 118
> New Haven, CT 06513-3051 Email: scott.coulter@cyclone•com
> U.S.A. Web: http://www.cyclone.com
>___________________________________________________________________
>
>-----Original Message-----
>From: Xianghua Xiao [mailto:x.xiao@freescale•com]
>Sent: Friday, June 09, 2006 3:37 PM
>To: Scott Coulter
>Subject: Re: booting Linux 2.6.15 using a ramdisk and greater than 512MB
>of DRAM
>
>try set initrd_high=0xffffffff under u-boot, see if it helps
>
>Scott Coulter wrote:
>
>
>
>>Hi everyone,
>>
>>I am not sure if this is a linux question or a u-boot question. I have
>>a custom MPC8540 board running U-boot 1.1.4. With a NFS root
>>configuration, I have booted and run 2.6.15 with memory from 256MB to
>>2GB. If I build a ramdisk image (or even if I use the ramdisk image
>>with the 85xx version of ELDK 4.0) and then combine it with the kernel
>>image (vmlinux.gz) using "mkimage", the linux boot blows out with an
>>oops if I boot the board with more that 512MB of DRAM. From the U-boot
>>output, it looks like the ramdisk image is getting copied to the upper
>>portion of DRAM. Is it possible that the kernel doesn't map enough
>>
>>
>DRAM
>
>
>>to allow the image to be read?
>>
>>I haven't spent a lot of time debugging this once I saw that the 512MB
>>configuration worked OK. Has anyone run into this?
>>
>>Thanks,
>>
>>Scott
>>
>>
>>
>>___________________________________________________________________
>>
>> Scott N. Coulter
>> Senior Software Engineer
>>
>> Cyclone Microsystems
>> 370 James Street Phone: 203.786.5536 ext. 118
>> New Haven, CT 06513-3051 Email: scott.coulter@cyclone•com
>> U.S.A. Web: http://www.cyclone.com
>>___________________________________________________________________
>>
>>_______________________________________________
>>Linuxppc-embedded mailing list
>>Linuxppc-embedded@ozlabs•org
>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>>
>>
next parent reply other threads:[~2006-06-09 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43EB80E07C42E1408726E4905FB96B0466C6C1@CYBORG3.cyclone.com>
2006-06-09 19:46 ` Xianghua Xiao [this message]
2006-06-09 19:28 booting Linux 2.6.15 using a ramdisk and greater than 512MB of DRAM Scott Coulter
2006-06-09 22:41 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4489D00B.7070800@freescale.com \
--to=x.xiao@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=scott.coulter@cyclone$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox