From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.17 /dev/port
Date: 22 May 2002 16:32:04 -0700 [thread overview]
Message-ID: <ach9pk$ced$1@cesium.transmeta.com> (raw)
In-Reply-To: <UTC200205222246.g4MMkNL26024.aeb@smtp.cwi.nl>
Followup to: <UTC200205222246.g4MMkNL26024.aeb@smtp.cwi.nl>
By author: Andries.Brouwer@cwi.nl
In newsgroup: linux.dev.kernel
>
> In my eyes /dev/port is a rather unimportant corner
> of the kernel. Removing it does not streamline anything,
> we hear that it saves 454 bytes. A worthy goal, but..
>
> Today a few things use /dev/port. Some low level mouse,
> keyboard and console utilities. kbdrate. hwclock.
>
> Is it needed? Hardly - most uses can be replaced by inb()
> and outb(). But I am not sure why that would be better.
> And I seem to recall that hwclock on some flavours of Alpha
> really needed the /dev/port way. But I may be mistaken.
>
On non-Intel platforms, with no dedicated IOIO opcodes, IOIO is
usually implemented as a specific memory range. In that case, the
only way to allow user-space access to it would be to mmap() that
range... which means iopl() inb() and outb() on those platforms might
be implemented either as open, readp and writep, respectively, or by
iopl() being open() followed by mmap().
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-05-22 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 22:46 [PATCH] 2.5.17 /dev/port Andries.Brouwer
2002-05-22 23:32 ` H. Peter Anvin [this message]
2002-05-23 1:59 ` Alan Cox
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='ach9pk$ced$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox