From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rui Sousa <rui.p.m.sousa@clix.pt>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"German Gomez Garcia" <german@piraos.com>,
"José Carlos Monteiro" <jcm@netcabo.pt>,
linux-kernel@vger.kernel.org,
emu10k1-devel <emu10k1-devel@lists.sourceforge.net>,
"Steve Stavropoulos" <steve@math.upatras.gr>,
"Daniel Bertrand" <d.bertrand@ieee.org>,
dledford@redhat.com
Subject: Re: [Emu10k1-devel] Re: Emu10k1 SPDIF passthru doesn't work if
Date: Thu, 28 Feb 2002 17:33:10 -0500 [thread overview]
Message-ID: <3C7EB026.52ED48B3@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202282042150.1215-100000@sophia-sousar2.nice.mindspeed.com>
Rui Sousa wrote:
>
> On Wed, 27 Feb 2002, Alan Cox wrote:
>
> It's true dma_addr_t does change from u32 to u64 and we do thinks like:
>
> (32 bit pci register) = cpu_to_le32(dma_handle)
>
> What is the correct way of doing this?
>
> (32 bit pci register) = cpu_to_le32((u32)dma_handle)
If you only have 32 bits, then I presume 64-bit DMA isn't supported.
So, (1) never pass more than 0xffffffff to pci_set_dma_mask, and (2)
just truncate dma_addr_t (addr & 0xffffffff) so that you only read the
low 32-bits, always.
Jeff
--
Jeff Garzik | "UNIX enhancements aren't."
Building 1024 | -- says /usr/games/fortune
MandrakeSoft |
next prev parent reply other threads:[~2002-02-28 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1014586494.1518.23.camel@skyblade>
2002-02-26 15:32 ` Emu10k1 SPDIF passthru doesn't work if CONFIG_NOHIGHMEM is not enabled German Gomez Garcia
2002-02-27 14:58 ` [Emu10k1-devel] " Rui Sousa
2002-02-27 16:02 ` [Emu10k1-devel] Re: Emu10k1 SPDIF passthru doesn't work if Alan Cox
2002-02-28 19:50 ` Rui Sousa
2002-02-28 22:33 ` Jeff Garzik [this message]
2002-03-01 1:07 ` Alan Cox
2002-03-01 1:03 ` David S. Miller
2002-03-01 1:20 ` Daniel Bertrand
2002-03-02 6:38 ` 64bit dma_addr_t (was: Emu10k1 SPDIF ...) Daniel Bertrand
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=3C7EB026.52ED48B3@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=d.bertrand@ieee.org \
--cc=dledford@redhat.com \
--cc=emu10k1-devel@lists.sourceforge.net \
--cc=german@piraos.com \
--cc=jcm@netcabo.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.p.m.sousa@clix.pt \
--cc=steve@math.upatras.gr \
/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.