[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] mem kernel command

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] mem kernel command
From: John Williams <jwilliams@xxxxxxxxxxxxxx>
Date: Fri, 28 Mar 2008 09:44:40 +1000
In-reply-to: <285649.78944.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <285649.78944.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060418 Red Hat/1.7.13-1.1.3.1.centos3

Hi Frank,

Frank Lombardo wrote:

Thanks for pointing that out John, I missed that discussion.  What about u-boot?  CONFIG_PRAM doesn't seem to protect the 4M region either.  Is there a way to protect this RAM through a reset?


u-boot will respect the same memory boundaries as the kernel.

So, if you use MAIN_MEMORY_SIZE and _OFFSET params in MSS file to carveout a region, anything outside that should be ignored (and untouched) byboth kernel and u-boot.


Please let me know if you find this not to be the case!

Cheers,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

References:
- Re: [microblaze-uclinux] mem kernel command
  - From: Frank Lombardo

Prev by Date: Re: [microblaze-uclinux] mem kernel command
Next by Date: Re: [microblaze-uclinux] Adding new driver to kernel 2.6
Previous by thread: Re: [microblaze-uclinux] mem kernel command
Next by thread: [microblaze-uclinux] RTSP client
Index(es):
- Date
- Thread