From: Dave Hansen <haveblue@us.ibm.com>
To: Shesha Sreenivasamurthy <shesha@inostor.com>
Cc: "'redhat-ppp-list@redhat.com'" <redhat-ppp-list@redhat.com>,
"'kernelnewbies@nl.linux.org'" <kernelnewbies@nl.linux.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Highmemory problem
Date: Mon, 16 Feb 2004 15:21:33 -0800 [thread overview]
Message-ID: <1076973693.10966.39.camel@nighthawk> (raw)
In-Reply-To: <402FFA91.5020206@inostor.com>
On Sun, 2004-02-15 at 15:02, Shesha Sreenivasamurthy wrote:
> Hi All,
> I have a driver that currently does not support highmem. i.e., no "kmap"
> & "kunmap" is being implemented. Now we want to support more than 896MB
> RAM. What is the best approach to tackle the situation? Any ideas is
> highly valued.
Which driver are you referring to? Posting a copy of it would be a good
first step, so we can get an idea what we're dealing with.
--dave
prev parent reply other threads:[~2004-02-16 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 1:51 Help in writing a synchrnous ppp driver Vanitha Ramaswami
2004-01-30 3:43 ` Paul Fulghum
2004-02-15 23:02 ` Kernel Highmemory problem Shesha Sreenivasamurthy
2004-02-16 23:21 ` Dave Hansen [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=1076973693.10966.39.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=redhat-ppp-list@redhat.com \
--cc=shesha@inostor.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