From: Grant Likely <grant.likely@secretlab.ca>
To: sebastien.chretien.enseirb@gmail.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ioremap and vmalloc
Date: Fri, 19 Sep 2008 10:43:42 -0600 [thread overview]
Message-ID: <20080919164342.GA8723@secretlab.ca> (raw)
In-Reply-To: <48D3D47E.5050200@gmail.com>
On Fri, Sep 19, 2008 at 06:34:06PM +0200, =?ISO-8859-1?Q?S=E9bastien_Chr=E9tien_ wrote:
> The first is ioremap(0x20000000,0x10000000);
> The second is ioremap(0x80000000,0x10000000);
> Is it too long
Well, you're trying to allocate two 256MB regions. That is very large.
What kind of device are you trying to map?
g.
prev parent reply other threads:[~2008-09-19 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 11:15 ioremap and vmalloc Sébastien Chrétien
2008-09-19 13:49 ` Grant Likely
2008-09-19 16:34 ` Sébastien Chrétien
2008-09-19 16:38 ` Josh Boyer
2008-09-19 16:45 ` Sébastien Chrétien
2008-09-19 16:58 ` Josh Boyer
2008-09-19 17:12 ` Grant Likely
2008-09-19 17:47 ` Sébastien Chrétien
2008-09-19 17:52 ` Sébastien Chrétien
2008-09-22 5:28 ` Benjamin Herrenschmidt
2008-09-19 16:43 ` Grant Likely [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=20080919164342.GA8723@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=sebastien.chretien.enseirb@gmail.com \
/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).