> So each hardware interface will then have to have a bus ioctl to
> tell you what bus it works on. Then you can go and use /dev/pcimmap
> or /dev/zorrommap etc. Yuck!!
>
> At the core, I would agree with you, it can become a mess.
>
> However, I suggested the interface this way for a reason. Each device
> type specifies a particular bus and device differently. PCI uses the
> bus/device/function triple, SBUS uses device path strings or firmware
> device tree nodes, and I'm sure zorro has it's own method of device
> specification too.
>
> We already have BUS drivers for each of these entities, so all the
> details and implementation of this /dev/${BUS}map thing can be
> contained in those drivers.
Okay. I can see it as a short term solution but we really need to work out
this mmap mess via the virtual memory system.
Q: Why did they deprecate a.out support in linux?
A: Because a nasty coff is bad for your elf.
James Simmons [jsimmons@linux-fbdev.org] ____/|
fbdev/console/gfx developer \ o.O|
http://www.linux-fbdev.org =(_)=
http://linuxgfx.sourceforge.net U
http://linuxconsole.sourceforge.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:25 EST