Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com, jgarzik@mandrakesoft.com,
	davem@redhat.com
Subject: Re: [parisc-linux] tulip DMA mapping
Date: Fri, 10 Nov 2000 10:18:08 +0000	[thread overview]
Message-ID: <20001110101808.B11268@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200011092012.MAA06943@milano.cup.hp.com>; from grundler@cup.hp.com on Thu, Nov 09, 2000 at 12:12:25PM -0800

On Thu, Nov 09, 2000 at 12:12:25PM -0800, Grant Grundler wrote:
> 0 is a valid pci_map_single() return value when the system has an IO MMU.

Oh dear.  You can bet tulip won't be the only driver which assumes it
isn't a valid return value.  Can't our IOMMU code be limited in such a
way that 0 is not a valid return value?  Say, constrain all allocated
addresses to the top half of the device bus?

(um, just check me on this, map_single returns a device bus address,
not a processor bus address, right?)

> The system will panic before pci_map_single() will fail.
> The driver needs to remember some other way if a buffer was mapped or not.
> Or the Documentation/DMA-mapping.txt should be changed - ie add this
> to the interface definition and I can reserve the 1st mapping
> entry so no-one uses it.

we should probably have a BAD_DMA_ADDR define which that array should be
initialised to.  it's a little late in 2.4 to go through and audit all
the drivers again.

> Should I be mailing Jeff Garzik <jgarzik@mandrakesoft.com> directly?
> Or can someone who knows Jeff point this out to him?

i've cc'd jeff & dave miller on this.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2000-11-10 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 20:12 [parisc-linux] tulip DMA mapping Grant Grundler
2000-11-10 10:18 ` Matthew Wilcox [this message]
2000-11-10 10:16   ` David S. Miller
2000-11-10 11:12     ` Richard Hirst
2000-11-10 11:26       ` David S. Miller
2000-11-10 14:30         ` Jeff Garzik
2001-03-04 17:22         ` Jeff Garzik
2000-11-10 16:29   ` Grant Grundler

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=20001110101808.B11268@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=davem@redhat.com \
    --cc=grundler@cup.hp.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox