From: Tom Gall <tom_gall@vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.4, cs46xx snd, and virt_to_bus
Date: Mon, 11 Feb 2002 12:09:43 -0600 [thread overview]
Message-ID: <3C6808E7.7F8BC131@vnet.ibm.com> (raw)
Hi All,
Well forgive me for not being up on the lastest news but from building
2.5.4 kernel for my box, which uses the cs46xx.c sound driver, it would
appear that virt_to_bus and bus_to_virt has gone the way of the do-do.
What's the correct method now?
Be nice to get this cleaned up....
Regards,
Tom
--
Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey
Peace, Love & "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
http://www.ibm.com/linux/ltc/ shattering ka-boom!"
(w) tom_gall@vnet.ibm.com -- Marvin Martian
(w) 507-253-4558
(h) tgall@rochcivictheatre.org
next reply other threads:[~2002-02-11 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 18:09 Tom Gall [this message]
2002-02-11 17:53 ` 2.5.4, cs46xx snd, and virt_to_bus Alan Cox
[not found] <fa.fefkfjv.rmid9f@ifi.uio.no>
2002-02-11 17:38 ` John Weber
2002-02-11 18:10 ` Alan Cox
2002-02-12 2:43 ` David S. Miller
2002-02-12 14:51 ` Alan Cox
2002-02-12 14:49 ` benh
2002-02-12 14:50 ` benh
2002-02-14 6:36 ` Paul Gortmaker
2002-02-14 13:26 ` Alan Cox
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=3C6808E7.7F8BC131@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox