From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What is the truth about Linux 2.4's RAM limitations?
Date: Tue, 10 Jul 2001 13:01:53 -0500 [thread overview]
Message-ID: <3B4B4311.90206@interactivesi.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010710131403.18337A-100000@chaos.analogic.com>
Richard B. Johnson wrote:
>The kernel has the capability (by design) of addressing anything it
>wants. So, if this is what you mean by "shared", I guess you imply
>that Windows can't address anything it wants? Of course it can.
>
Well, I may have oversimplified it a bit. My point was that a given
Windows driver can't just take a 32-bit pointer and pass it to another
driver and have it just work like that.
--
Timur Tabi
Interactive Silicon
next prev parent reply other threads:[~2001-07-10 18:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 20:01 What is the truth about Linux 2.4's RAM limitations? Adam Shand
2001-07-09 21:15 ` Brian Gerst
2001-07-09 21:18 ` Rik van Riel
2001-07-09 22:17 ` Matti Aarnio
2001-07-10 13:49 ` Chris Wedgwood
2001-07-10 17:03 ` Timur Tabi
2001-07-10 17:35 ` Richard B. Johnson
2001-07-10 18:01 ` Timur Tabi [this message]
2001-07-10 18:08 ` Jonathan Lundell
2001-07-10 18:45 ` Richard B. Johnson
2001-07-10 19:26 ` Jonathan Lundell
2001-07-10 23:56 ` Jesse Pollard
2001-07-10 20:19 ` Malcolm Beattie
2001-07-10 3:01 ` jlnance
2001-07-10 3:29 ` Michael Bacarella
2001-07-16 8:37 ` Ingo Oeser
[not found] <Pine.LNX.4.32.0107091250170.25061-100000@maus.spack.org.suse.lists.linux.kernel>
2001-07-09 21:03 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-07-09 21:29 Jesse Pollard
2001-07-10 17:01 ` Timur Tabi
2001-07-10 18:12 Jesse Pollard
2001-07-10 18:22 ` Jonathan Lundell
2001-07-10 18:28 ` Brian Gerst
2001-07-10 18:43 ` Chris Wedgwood
2001-07-10 19:35 ` Brian Gerst
2001-07-10 18:38 Jesse Pollard
2001-07-10 19:14 ` Mark H. Wood
2001-07-10 21:49 Jesse Pollard
2001-07-10 22:07 ` Jonathan Lundell
2001-07-11 4:31 alad
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=3B4B4311.90206@interactivesi.com \
--to=ttabi@interactivesi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.