From: Grant Grundler <grundler@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PCI DAC routines for SN
Date: Tue, 23 Apr 2002 21:11:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905512@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905493@msgid-missing>
Jesse Barnes wrote:
> He was the one that implemented it I thought. His assertion was that
> since most chipsets don't handle 64 bit coherent allocations well, the
> consistent interface should be forced to return a 32 bit address (is
> that right Dave?).
Right - HP recently changed ZX1 support based on the same assertion.
And for the drivers I'm aware of (eg tg3, sym53c8xx), Dave is right.
...
> otherwise I'd like to leave it up to the platform
> (i.e. ia64/sn could return a 64 bit address and sparc64 could do 32).
This is not feasible. The driver/device will use/support the same number
of address bits regardless of architecture. If the architecture provides
fewer bits than the driver/device supports, no problem obviously.
I'm curious to see what happens with the pci_dac_alloc_consistent() idea.
grant
next prev parent reply other threads:[~2002-04-23 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:34 [Linux-ia64] Re: PCI DAC routines for SN David Mosberger
2002-04-22 22:39 ` Jesse Barnes
2002-04-22 23:07 ` David Mosberger
2002-04-22 23:40 ` Jesse Barnes
2002-04-23 1:34 ` Grant Grundler
2002-04-23 21:11 ` Grant Grundler [this message]
2002-04-24 4:04 ` David S. Miller
2002-04-24 5:49 ` Jesse Barnes
2002-04-24 5:50 ` David S. Miller
2002-04-24 16:13 ` Grant Grundler
2002-04-24 17:39 ` David S. Miller
2002-04-24 17:40 ` David S. Miller
2002-04-24 19:45 ` Jesse Barnes
2002-04-24 23:13 ` Jesse Barnes
2002-04-24 23:53 ` David S. Miller
2002-04-25 0:08 ` David S. Miller
2002-04-25 0:11 ` Jesse Barnes
2002-04-25 0:17 ` David S. Miller
2002-04-25 0:21 ` Jesse Barnes
2002-04-25 0:36 ` Jesse Barnes
2002-04-25 0:43 ` David S. Miller
2002-04-25 1:00 ` David S. Miller
2002-04-25 1:01 ` Jesse Barnes
2002-04-25 1:22 ` Jesse Barnes
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=marc-linux-ia64-105590701905512@msgid-missing \
--to=grundler@cup.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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.