From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI domain stuff
Date: 30 Jun 2003 22:47:50 -0700 [thread overview]
Message-ID: <bdr7a6$4eu$1@cesium.transmeta.com> (raw)
In-Reply-To: 1057034041.31826.1.camel@rth.ninka.net
Followup to: <1057034041.31826.1.camel@rth.ninka.net>
By author: "David S. Miller" <davem@redhat.com>
In newsgroup: linux.dev.kernel
>
> On Mon, 2003-06-30 at 21:05, Matthew Wilcox wrote:
> > We need to support mmaping device resources. I think this actually
> > merits being a first class sysfs concept -- turn a struct resource into
> > an mmapable file. The current fugly ioctl really has to go.
>
> What's so wrong with the "fugly ioctl"?
>
> What can't you do with it?
>
> You can even mmap the complete I/O space of a PCI bus (in order to poke
> around in implicit I/O resources like the VGA registers that a PCI card
> might respond to).
>
Presumably only on architectures which use memory-mapped IO address
space.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-07-01 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1057010214.1277.11.camel@albertc>
[not found] ` <20030630220758.GA27368@kroah.com>
[not found] ` <1057014182.4048.3887.camel@cube>
[not found] ` <20030630231515.GA27813@kroah.com>
2003-07-01 4:05 ` PCI domain stuff Matthew Wilcox
2003-07-01 4:25 ` H. Peter Anvin
2003-07-01 4:34 ` David S. Miller
2003-07-01 5:47 ` H. Peter Anvin [this message]
2003-07-01 6:02 ` David S. Miller
2003-07-01 6:06 ` H. Peter Anvin
2003-07-01 6:03 ` David S. Miller
2003-07-01 6:13 ` H. Peter Anvin
2003-07-01 16:30 ` Andy Isaacson
2003-07-01 16:34 ` H. Peter Anvin
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='bdr7a6$4eu$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