All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ZONE_DMA
Date: Mon, 1 Jan 2001 18:24:35 +0000	[thread overview]
Message-ID: <20010101182435.C21918@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <E14D9PA-00017j-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Jan 01, 2001 at 06:09:53PM +0000

On Mon, Jan 01, 2001 at 06:09:53PM +0000, Alan Cox wrote:
> > I'm not familiar with the hardware problem here.  Must EISA cards be
> > restricted to a certain part of the address space?  I can glean from
> 
> EISA on PC can hit the full 32bits. DMA is meant to indicate the 16Mb lowest
> memory segment that ISA can hit (which may not be at 0 depending on the box)

OK, so people who write EISA drivers are not going to specify GFP_DMA.
Or shouldn't.

> > the source that ISA cards are restricted to a 16MB address space --
> > are we going to support ISA cards?
> 
> Some PCI cards have the same limit 8)

But that's handled through the PCI DMA mapping interface these days.

So how should we be populating our zones?  Put all of our memory in
ZONE_DMA, like ppc, since the only people who'll be specifying GFP_DMA
will have done so incorrectly?  Put the first 16MB of it in there,
since we might support ISA some day?  Put none of it in there on the
grounds we don't support ISA at all?

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-01-01 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-01 17:43 [parisc-linux] ZONE_DMA Matthew Wilcox
2001-01-01 18:09 ` Alan Cox
2001-01-01 18:24   ` Matthew Wilcox [this message]
2001-01-01 18:32     ` Alan Cox
2001-01-01 18:55       ` Matthew Wilcox
2001-01-01 19:01         ` Alan Cox
2001-01-01 19:18           ` Matthew Wilcox
2001-01-02  0:59   ` Grant Grundler
2001-01-02  1:21     ` Matthew Wilcox
2001-01-02  6:46       ` 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=20010101182435.C21918@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.