All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] FB cleanups
Date: Wed, 11 Apr 2001 23:51:04 +0100	[thread overview]
Message-ID: <20010411235104.A19570@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <d31yqzrwtz.fsf@lxplus015.cern.ch>; from jes@linuxcare.com on Wed, Apr 11, 2001 at 10:43:52PM +0200

On Wed, Apr 11, 2001 at 10:43:52PM +0200, Jes Sorensen wrote:
> Point is that readb/writeb are *only* defined for PCI and PCI
> look-alike devices, even for ISA you're supposed to use
> isa_readb/isa_writeb

No, you're wrong.  isa_* are due to go away in 2.5.  After you've
called ioremap(), you can call readb/writeb on the returned address.
You might want to refer to Documentation/IO-mapping.txt and/or
Documentation/DocBook/deviceiobook.* (only in Alan's tree right now).

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-04-11 22:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 20:13 [parisc-linux] FB cleanups Matthew Wilcox
2001-04-11 20:30 ` Jes Sorensen
2001-04-11 20:34   ` Matthew Wilcox
2001-04-11 20:43     ` Jes Sorensen
2001-04-11 22:51       ` Matthew Wilcox [this message]
2001-04-11 22:56         ` Jes Sorensen
2001-04-11 23:00           ` Alan Cox
2001-04-12 18:48             ` Jes Sorensen
2001-04-13  7:04             ` Grant Grundler
2001-04-13 12:52               ` Alan Cox
2001-04-13 17:52                 ` Grant Grundler
2001-04-13 18:13                   ` Alan Cox
2001-04-11 23:36           ` Matthew Wilcox
2001-04-13 16:48             ` Jes Sorensen
2001-04-13 18:11               ` Alan Cox
2001-04-17 18:04                 ` Jes Sorensen
2001-04-17 18:22                   ` Matthew Wilcox
2001-04-17 19:57                     ` Alan Cox
2001-04-13  7:02           ` Grant Grundler
2001-04-13 16:49             ` Jes Sorensen

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=20010411235104.A19570@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=jes@linuxcare.com \
    --cc=parisc-linux@parisc-linux.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.