public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <iod00d@hp.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	"David S. Miller" <davem@redhat.com>,
	Jes Sorensen <jes@wildopensource.com>,
	torvalds@transmeta.com, grundler@dsl2.external.hp.com,
	cngam@sgi.com, jeremy@sgi.com,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ia64@linuxia64.org, wildos@sgi.com
Subject: Re: [Linux-ia64] Re: [patch] support 64 bit pci_alloc_consistent
Date: 18 May 2003 12:49:49 -0500	[thread overview]
Message-ID: <1053280195.10810.61.camel@mulgrave> (raw)
In-Reply-To: <20030518172203.GA13855@cup.hp.com>

On Sun, 2003-05-18 at 12:22, Grant Grundler wrote:
> On Sun, May 18, 2003 at 09:43:41AM +0000, Arjan van de Ven wrote:
> > Most drivers will just say "look I
> > can do THIS much. I don't give a flying fish about how much of
> > that you actually use". At least in the probing code. 
> 
> The platform code needs a way to indicate the given mask will not work.
> Rejecting proposals by the driver seems reasonable if the driver
> only supports two different masks anyway (eg 64 and 32-bit).
> 
> In the case of a platform requiring 64-bit masks for consistent mappings,
> the platform DMA code must reject proposals for non-64-bit DMA masks.
> (eg PCI-X device implementing less than 64-bits)
> 
> In both cases the driver will care because it will crash the box otherwise.

In that case, the platform returns zero to "this much" being less than
the full 64 bits implying there's no mask the platform and driver can
agree on.

James



  reply	other threads:[~2003-05-18 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  4:09 [patch] support 64 bit pci_alloc_consistent Jes Sorensen
2003-05-18  5:46 ` David S. Miller
2003-05-18  6:00 ` Andre Hedrick
2003-05-18  9:29 ` Arjan van de Ven
2003-05-18  9:35   ` David S. Miller
2003-05-18  9:43     ` Arjan van de Ven
2003-05-18 17:22       ` [Linux-ia64] " Grant Grundler
2003-05-18 17:49         ` James Bottomley [this message]
2003-05-18 20:17           ` Grant Grundler
2003-05-18 21:26             ` James Bottomley
2003-05-19 16:26               ` Grant Grundler
2003-05-18 14:17   ` James Bottomley
2003-05-18 14:21     ` Arjan van de Ven
2003-05-18 14:28       ` James Bottomley

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=1053280195.10810.61.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=arjanv@redhat.com \
    --cc=cngam@sgi.com \
    --cc=davem@redhat.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=iod00d@hp.com \
    --cc=jeremy@sgi.com \
    --cc=jes@wildopensource.com \
    --cc=linux-ia64@linuxia64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=wildos@sgi.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