From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jes Sorensen <jes@linuxcare.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: modica@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Proposal for a new PCI function call
Date: Fri, 13 Apr 2001 21:25:01 -0400 [thread overview]
Message-ID: <3AD7A6ED.7626BE05@mandrakesoft.com> (raw)
In-Reply-To: <3AD601B4.7E0B14E4@sgi.com> <3AD604B0.2713F08B@mandrakesoft.com> <d3vgo9ej5r.fsf@lxplus015.cern.ch>
Jes Sorensen wrote:
> >>>>> "Jeff" == Jeff Garzik <jgarzik@mandrakesoft.com> writes:
> >> I think the function idea would let us do some sanity checking to
> >> make sure drivers weren't setting this to 64bit on non-64 bit
> >> busses and stuff.
> Jeff> pci_set_dma_mask. Modify that to do the additional checks you
> Jeff> need.
> Jeff> Nobody should be setting dma_mask directly anymore, it should be
> Jeff> done through this function.
> 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.
It seems to me that not doing #ifdef CONFIG_HIGHMEM right now is a
bug... I think it's the megaraid driver that wants to set dma_addr_t to
a 64-bit mask.
Alan Cox wrote:
> pci_set_dma_mask_bits() ? So you could do
>
> pci_set_dma_mask_bits(pdev, 64);
As they say, "six of one, 'half-dozen of the other." I don't have a
preference...
Jeff
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
next prev parent reply other threads:[~2001-04-14 1:50 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 [this message]
2001-04-16 14:24 ` Venkatesh Ramamurthy
2001-04-19 2:25 ` 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=3AD7A6ED.7626BE05@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jes@linuxcare.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