All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com (David Howells),
	jes@sunsite.dk (Jes Sorensen),
	linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [RFC] I/O Access Abstractions
Date: Mon, 02 Jul 2001 17:41:36 +0100	[thread overview]
Message-ID: <19921.994092096@redhat.com> (raw)
In-Reply-To: <E15H6R1-00066U-00@the-village.bc.nu>
In-Reply-To: <E15H6R1-00066U-00@the-village.bc.nu>


alan@lxorguk.ukuu.org.uk said:
>  The question I think being ignored here is. Why not leave things as
> is.

Because if we just pass in this one extra piece of information which is
normally already available in the driver, we can avoid a whole lot of ugly
cruft in the out-of-line functions by plugging in the correct out-of-line 
function to match the resource. 

> The multiple bus stuff is a port specific detail hidden behind
> readb() and friends. 

The alternative view is that the _single_ bus stuff is a port-specific
detail which has permeated all the drivers and forced the non-i386
architectures' I/O functions to have to try to work out which bus they're
talking to when the driver could have just passed that information to them.

--
dwmw2



  reply	other threads:[~2001-07-02 16:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 13:13 [RFC] I/O Access Abstractions David Howells
2001-06-28 13:32 ` Alan Cox
2001-06-28 13:55   ` David Woodhouse
2001-06-28 16:02     ` Jes Sorensen
2001-06-29  8:31       ` David Howells
2001-06-29 21:02         ` Jes Sorensen
2001-07-02 14:22         ` David Woodhouse
2001-07-02 15:57           ` David Howells
2001-07-02 16:17             ` David Woodhouse
2001-07-02 16:20               ` Alan Cox
2001-07-02 16:41                 ` David Woodhouse [this message]
2001-07-02 16:56                   ` Alan Cox
2001-07-02 18:22                     ` Russell King
2001-07-02 18:26                       ` Jeff Garzik
2001-07-02 20:10                         ` Alan Cox
2001-07-02 22:08                           ` Benjamin Herrenschmidt
2001-07-02 22:15                             ` Alan Cox
2001-07-02 23:54                               ` Benjamin Herrenschmidt
2001-07-03 12:02                                 ` Alan Cox
2001-07-03 14:38                                   ` Benjamin Herrenschmidt
2001-07-03  2:06                           ` Jeff Garzik
2001-07-03  8:38                             ` David Howells
2001-07-07 11:27                               ` Geert Uytterhoeven
2001-07-03  8:15                         ` David Howells
2001-07-03  8:22                           ` Jeff Garzik
2001-07-03  8:31                             ` Jeff Garzik
2001-07-03  9:00                               ` David Howells
2001-07-03  9:29                                 ` Jeff Garzik
2001-07-02 22:10                       ` Benjamin Herrenschmidt
2001-07-03  8:04                     ` David Howells
2001-07-03  7:55                 ` David Howells
2001-07-03  8:00                   ` Jeff Garzik
2001-07-03  8:07                     ` David Howells
2001-07-03 11:53                   ` Alan Cox
2001-07-07 11:26                   ` Geert Uytterhoeven
     [not found] <20010702191129.A29246@flint.arm.linux.org.uk>
2001-07-03  8:12 ` David Howells

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=19921.994092096@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=jes@sunsite.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.