From: Pete Zaitcev <zaitcev@redhat.com>
To: bha@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: ioremap returns NULL
Date: Fri, 29 Nov 2002 18:28:49 -0500 [thread overview]
Message-ID: <200211292328.gATNSnL27325@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1038579362.3203.linux-kernel2news@redhat.com>
>[...]
> For each card I ioremap() 2 * 16 MB of PCI memory space.
> It succeeds for the 1st card but for the 2nd card I get NULL
> as result. This means I cannot use the 2nd card...
I think you are screwed. The ioremap grabs from vmalloc area,
which is something like 64MB on i386. The best option is
to rewrite the driver to allocate less, and perhaps use
fewer modules.
Running a 2G/2G split might help, I'm not sure. But that
route has userland implications anyway, so don't.
-- Pete
next parent reply other threads:[~2002-11-29 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1038579362.3203.linux-kernel2news@redhat.com>
2002-11-29 23:28 ` Pete Zaitcev [this message]
2002-11-30 10:15 ioremap returns NULL Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 14:07 Bernd Harries
[not found] ` <200211291514.50171.gabrielli@roma2.infn.it>
2002-11-29 14:24 ` Bernd Harries
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=200211292328.gATNSnL27325@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=bha@gmx.de \
--cc=linux-kernel@vger.kernel.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