From: Kevin Hilman <kevin@hilman.org>
To: linux-kernel@vger.kernel.org
Subject: ioremap() >= 128Mb (was: Memory problem with bttv driver)
Date: Wed, 10 Apr 2002 15:39:05 -0700 [thread overview]
Message-ID: <87sn63tbzq.fsf@bugs.hilman.org> (raw)
I followed the 'Memory problem with bttv driver' thread from the
archives and was curious if there was any resolution.
The basic problem is that I have a machine with 1G physical memory and
a device with an 128Mb of on-board memory that I would like to
ioremap(). Of course, since VMALLOC_RESERVE is 128Mb this will always
fail if there have been any previous calls to vmalloc() or ioremap()
(which is aways true when the driver loads as a module.)
So far I have a few workarounds, but no good long term solution.
- boot the kernel with less than 1G on cmdline: mem=768M
- hack VMALLOC_RESERVE
Is it reasonable to make VMALLOC_RESERVE be configurable at boot-time
instead of compile time?
Or, is there a better way to get memory-mapped access to all of the
devices on-board memory?
Thanks.
--
Kevin Hilman <kevin@hilman.org>
next reply other threads:[~2002-04-10 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 22:39 Kevin Hilman [this message]
2002-04-11 5:38 ` ioremap() >= 128Mb (was: Memory problem with bttv driver) Martin J. Bligh
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=87sn63tbzq.fsf@bugs.hilman.org \
--to=kevin@hilman.org \
--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