From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-os@analogic.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Walking all the physical memory in an x86 system
Date: Tue, 30 Nov 2004 20:28:06 +0000 [thread overview]
Message-ID: <1101846485.25609.173.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.53.0411302141080.31175@yvahk01.tjqt.qr>
On Maw, 2004-11-30 at 20:46, Jan Engelhardt wrote:
> I want(ed) to find out which I/O port to use for inb() and stuff, and using the
> BIOS's provided data. If you are referring to "ports", I could not find a
> device node, but "port" maybe:
I didn't know that was in the BIOS page.
> Oh, look what /dev/mem found! (I retried haha)
> So, /dev/mem points to "physical" mem in a sense like DOS has. (Where, the
> BIOS, is blend into, as you can see)
The kernel also preserves the low 4K because some apps, APM and the like
turned out to need it.
next prev parent reply other threads:[~2004-11-30 21:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 16:09 Walking all the physical memory in an x86 system Hanson, Jonathan M
2004-11-30 16:10 ` Jan Engelhardt
2004-11-30 16:12 ` Jan Engelhardt
2004-11-30 17:17 ` Erik Mouw
[not found] ` <41ACADD3.2030206@draigBrady.com>
2004-11-30 17:34 ` Jan Engelhardt
2004-11-30 18:50 ` Alan Cox
2004-11-30 20:25 ` linux-os
2004-11-30 20:46 ` Jan Engelhardt
2004-11-30 20:28 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-30 23:24 Hanson, Jonathan M
2004-12-01 8:37 ` Jan Engelhardt
2004-11-30 21:36 Hanson, Jonathan M
2004-11-30 21:16 Hanson, Jonathan M
2004-11-30 21:26 ` linux-os
2004-11-30 21:28 ` Jan Engelhardt
2004-11-30 15:41 Hanson, Jonathan M
2004-11-30 15:55 ` Jan Engelhardt
2004-11-30 16:01 ` P
2004-11-30 16:10 ` linux-os
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=1101846485.25609.173.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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