linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "David C. Chiu" <dchiu@ariodata.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Memory Pre-allocation (mem=xxx)
Date: Sat, 23 Feb 2002 01:57:24 +0100	[thread overview]
Message-ID: <20020223005729.F26B1109E3@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 22 Feb 2002 16:42:46 PST." <8A098FDFC6EED94B872CA2033711F86F0ABD0C@orion.ariodata.com>


In message <8A098FDFC6EED94B872CA2033711F86F0ABD0C@orion.ariodata.com> you wrote:
>
> We're working on a project that requires a two megabytes block of
> contiguous memory in kernel space. Although it is well documented that
> memory can be reserved by using mem=xx arguments during boot time, it is
> unclear (to me) as to how a driver can automatically detect the size of
> the said reserved block.

Pass an extra boot argument?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Generally speaking, there are other ways to accomplish whatever it is
that you think you need ...                               - Doug Gwyn

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-23  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  0:42 Memory Pre-allocation (mem=xxx) David C. Chiu
2002-02-23  0:57 ` Wolfgang Denk [this message]
2002-02-23  1:54 ` Jim Lewis
  -- strict thread matches above, loose matches on Subject: below --
2002-02-23  1:21 David C. Chiu
2002-02-25 12:35 ` Kenneth Johansson
2002-02-23  3:11 David C. Chiu
2002-02-23 17:14 ` Tom Rini
2002-02-24  0:15   ` Tom Rini
2002-02-27 21:23 David C. Chiu

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=20020223005729.F26B1109E3@denx.denx.de \
    --to=wd@denx.de \
    --cc=dchiu@ariodata.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).