Re: [RFC] I/O Access Abstractions

From: Geert Uytterhoeven (geert@linux-m68k.org)
Date: Sat Jul 07 2001 - 06:27:46 EST

Next message: Alexander Viro: "Re: [Acpi] Re: ACPI fundamental locking problems"
Previous message: Geert Uytterhoeven: "Re: [RFC] I/O Access Abstractions"
In reply to: David Howells: "Re: [RFC] I/O Access Abstractions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 3 Jul 2001, David Howells wrote:
> * It should make drivers easier to write: they don't have to worry about
> whether a resource refers to memory or to I/O or to something more exotic.
>
> * It makes some drivers more flexible. For example, the ne2k-pci driver has
> to be set at _compile_ time to use _either_ I/O ports _or_ memory. It'd
> make Linux installation more better if _both_ were supported.
>
> * It'd allow some drivers to be massively cleaned up (serial.c).

And the IDE driver.

Gr{oetje,eeting}s,

Geert

-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Alexander Viro: "Re: [Acpi] Re: ACPI fundamental locking problems"
Previous message: Geert Uytterhoeven: "Re: [RFC] I/O Access Abstractions"
In reply to: David Howells: "Re: [RFC] I/O Access Abstractions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jul 07 2001 - 21:00:20 EST