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

[microblaze-uclinux] mem kernel command

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: [microblaze-uclinux] mem kernel command
From: Frank Lombardo <flombardo@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2008 20:06:11 -0700 (PDT)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ameritech.net; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=oHdSgINGN9rQ5cVsODBdJDo6a8zaPEcFSHwV/RD0sRZtFwPihDyTzklyV4CCvbDJJEHFHtKCl2+YDdo2IPiErWi03mcSYGwzaSr46Lqxq4H7hC23V+dexZZSp7At4fO22oG7ZfIB/t2df1PA5VwZgKvf2cE2t/j9bRcrgx9Y2AE=;
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx

I am trying to limit the kernel to use only the bottom 60M of memory in a system with 64M.  The top 4M will be used by our custom logic.  I am attempting to do this use the mem=60M kernel parameter, but the 4M region gets corrupted during the kernel boot.  Should this work?  Is there a better way to go about this?

Thanks,
Frank


___________________________
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/

Follow-Ups:
- Re: [microblaze-uclinux] mem kernel command
  - From: John Williams

Prev by Date: Re: [microblaze-uclinux] MicroBlaze MMU support test release now available
Next by Date: Re: [microblaze-uclinux] Microblaze GDB problems
Previous by thread: [microblaze-uclinux] Jpeg viewer
Next by thread: Re: [microblaze-uclinux] mem kernel command
Index(es):
- Date
- Thread