All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parav Pandit <paravpandit@yahoo.com>
To: "David H. Lynch Jr." <dhlii@dlasys.net>,
	Clint Thomas <cthomas@Soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Define Linux system memory
Date: Wed, 20 Dec 2006 23:05:28 -0800 (PST)	[thread overview]
Message-ID: <588266.74305.qm@web36606.mail.mud.yahoo.com> (raw)
In-Reply-To: <458A2289.4070401@dlasys.net>

[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]

Hi,
   
  This memory information is passed by the u-boot in bd_info structure (typedef to bd_t).
  Its defined in include/asm-ppc/ppcboot.h file.
  First two parameters specify the start address and length.
   
  Well, I'll at least try on my host x86 system. There is doesn't get from the grub.
  It should work and I should be able to see in cat /proc/meminfo.
  I'll try and let you know.
   
  Regards,
  Parav Pandit
  

"David H. Lynch Jr." <dhlii@dlasys.net> wrote:
  Clint Thomas wrote:       To anybody who has done this before or understands how to do this, I was wondering if you know how to "tell" the kernel how much memory there is in the system. An example would be if I have 512MB of RAM, but only want the system to know that there is about 500MB in RAM, so that 12MB does not exist to the OS/kernel. Would this require mucking about in U-boot? or can I just define this in the kernel source? Thanks
   
   Clinton Thomas

    Most bootloaders including u-boot pass a board information structure that includes a variety of information including the memory size.
    Also I think top of memory is also typically passed to the Linux Kernel as a register parameter  by the boot loader.



     


---------------------------------
  _______________________________________________  Linuxppc-embedded mailing list  Linuxppc-embedded@ozlabs.org  https://ozlabs.org/mailman/listinfo/linuxppc-embedded



--   Dave Lynch             DLA Systems  Software Development:               Embedded Linux  717.627.3770         dhlii@dlasys.net    http://www.dlasys.net  fax: 1.253.369.9244               Cell: 1.717.587.7774  Over 25 years' experience in platforms, languages, and technologies too numerous to list.    "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."  Albert Einstein  
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #2: Type: text/html, Size: 3556 bytes --]

      reply	other threads:[~2006-12-21  7:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 16:52 Define Linux system memory Clint Thomas
2006-12-20 16:57 ` Frank
2006-12-20 18:02   ` Clint Thomas
2006-12-21  5:58 ` David H. Lynch Jr.
2006-12-21  7:05   ` Parav Pandit [this message]

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=588266.74305.qm@web36606.mail.mud.yahoo.com \
    --to=paravpandit@yahoo.com \
    --cc=cthomas@Soneticom.com \
    --cc=dhlii@dlasys.net \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.