From: John Weber <john.weber@linuxhq.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.4 sound module problem
Date: Wed, 13 Feb 2002 00:03:01 -0500 [thread overview]
Message-ID: <3C69F385.5050207@linuxhq.com> (raw)
In-Reply-To: <fa.f4gi5iv.1ikenrc@ifi.uio.no> <fa.fo94urv.167g1q5@ifi.uio.no>
Alan wrote:
> On Tuesday 12 February 2002 19:51, Albert Cranford wrote:
>
>>Not sure if this was the same message I received. but here
>>is the patch I used to get around my sound problem in
>>2.5.4.
>>
>
> Are you sure this is correct? include/asm/io.h seems to indicate that i/o
> addresses for PCI may not map correctly. The sound card I am using is PCI,
> not ISA.
You should not use isa_virt_to_bus. IIRC someone on this list worried
about this exact thing happening.
> Documentation/DMA-mapping.txt says that virt_to_bus is completly depreciated
> and nothing should be using it. Well, grepping the kernel source shows that
> quite a bit still uses it.
This is on the kernel janitor TODO, and we (janitors) will be tackling
this shortly. But your instinct is right, virt_to_bus shouldn't be
everywhere.
> What it looks like, on first glance, is that virt_to_bus was changed for pci
> devices to give this error message. (Since that symbol goes nowhere.) That
> effects a number of things, not just sound. (A whole bunch of cardbus drivers
> I would guess...)
This is correct. It has been a policy to use pci_alloc_consistent
instead of kmalloc/getfreepages and virt_to_bus, 2.5 is enforcing it now.
It is boring work to change this in many drivers, but I don't know any
better so I think it quite fun to go in and help :). I'll start sending
patches to the relevant maintainers shortly.
By the way, anyone know who the maintainer is for the persistent DMA
buffer code?
--
(o- j o h n e w e b e r
//\ http://www.linuxhq.com/people/weber/
v_/_ john.weber@linuxhq.com
next parent reply other threads:[~2002-02-13 5:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.f4gi5iv.1ikenrc@ifi.uio.no>
[not found] ` <fa.fo94urv.167g1q5@ifi.uio.no>
2002-02-13 5:03 ` John Weber [this message]
2002-02-13 5:18 ` Alan
2002-02-13 9:21 ` Alan Cox
2002-02-13 7:46 ` Miles Lane
[not found] <mailman.1013591941.29105.linux-kernel2news@redhat.com>
2002-02-13 17:21 ` Pete Zaitcev
2002-02-13 3:51 Albert Cranford
2002-02-13 3:10 ` Alan
2002-02-13 4:22 ` David S. Miller
2002-02-13 9:26 ` Alan Cox
2002-02-13 9:36 ` David S. Miller
2002-02-12 18:52 ` Gérard Roudier
2002-02-13 10:24 ` Alan Cox
2002-02-13 18:59 ` Alan
2002-02-13 20:26 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 2:22 Alan
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=3C69F385.5050207@linuxhq.com \
--to=john.weber@linuxhq.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
all inboxes | Powered by JetHome®