From: bhslinker@gmail.com (Bharath H S)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Reserving physical memory in Linux
Date: Tue, 28 Dec 2010 09:19:46 +0530 [thread overview]
Message-ID: <AANLkTinQxua51aQ1cOMCgKJW3fgT5t0Gs-U+=Q2fYyDN@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikhq89O1eUrUj_K=T99qozMuquA2MSfkJrhrYki@mail.gmail.com>
Asha,
You let the kernel now that X amount is DMA space only. It depends on
architecture though. What is architecture being worked upon?
- Bharath H S
On Mon, Dec 27, 2010 at 2:36 PM, Asha R <rd.asha22@gmail.com> wrote:
> Thanks Adam Lee.
> Is this mem= or memmap=?
> Regards,
> Asha
> On Mon, Dec 27, 2010 at 1:01 PM, Adam Lee <adam8157@gmail.com> wrote:
>>
>> On Mon, Dec 27, 2010 at 2:59 PM, Asha R <rd.asha22@gmail.com> wrote:
>> > Hi,
>> > I want to reserve one range of physical memory say from 0x10000000
>> > of?256MB
>> > in Linux. This region is required for DMA functions alone.
>> > Please help me understand how we can reserve this in Linux. Can this be
>> > done?using?boot options or any other?
>> >
>> > Regards,
>> > Asha
>>
>> try adding "mem=256M$0x10000000" in arg.
>>
>> via http://lxr.linux.no/source/Documentation/kernel-parameters.txt
>>
>> --
>> Regards,
>> Adam Lee
>> --------------------------------------------------
>> E-mail: adam8157 at gmail.com
>> Website: http://www.adam8157.info
>> --------------------------------------------------
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
prev parent reply other threads:[~2010-12-28 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 6:59 Reserving physical memory in Linux Asha R
2010-12-27 7:27 ` Rajat Sharma
2010-12-27 7:31 ` Adam Lee
2010-12-27 9:06 ` Asha R
2010-12-27 9:09 ` Adam Lee
2010-12-28 3:49 ` Bharath H S [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='AANLkTinQxua51aQ1cOMCgKJW3fgT5t0Gs-U+=Q2fYyDN@mail.gmail.com' \
--to=bhslinker@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).