public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@cern.ch>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	modica@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Proposal for a new PCI function call
Date: 19 Apr 2001 04:25:59 +0200	[thread overview]
Message-ID: <d366g1zkug.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <3AD601B4.7E0B14E4@sgi.com> <3AD604B0.2713F08B@mandrakesoft.com> <d3vgo9ej5r.fsf@lxplus015.cern.ch> <3AD7A6ED.7626BE05@mandrakesoft.com>
In-Reply-To: Jeff Garzik's message of "Fri, 13 Apr 2001 21:25:01 -0400"

>>>>> "Jeff" == Jeff Garzik <jgarzik@mandrakesoft.com> writes:

Jeff> Jes Sorensen wrote:
>> Hmmm, I was wondering if could come up with a pretty way to do this
>> on 32 bit boxes that wants to enable highmem DMA. Right now
>> pci_set_dma_mask() wants a dma_addr_t which means you have to do
>> #ifdef CONFIG_HIGHMEM <blah> #else <bleh> #endif.

Jeff> It seems to me that not doing #ifdef CONFIG_HIGHMEM right now is
Jeff> a bug...  I think it's the megaraid driver that wants to set
Jeff> dma_addr_t to a 64-bit mask.

There's a bunch of them doing it - it's butt-ugly though.

Jes

      parent reply	other threads:[~2001-04-19  2:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 19:27 Proposal for a new PCI function call Steve Modica
2001-04-12 19:40 ` Jeff Garzik
2001-04-13  0:29   ` Jes Sorensen
2001-04-13  0:40     ` Alan Cox
2001-04-19  2:27       ` Jes Sorensen
2001-04-14  1:25     ` Jeff Garzik
2001-04-16 14:24       ` Venkatesh Ramamurthy
2001-04-19  2:25       ` Jes Sorensen [this message]

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=d366g1zkug.fsf@lxplus015.cern.ch \
    --to=jes.sorensen@cern.ch \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=modica@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