Followup to: <email@example.com>
By author: "David S. Miller" <firstname.lastname@example.org>
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
-- <email@example.com> at work, <firstname.lastname@example.org> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 07 2003 - 22:00:12 EST