From: Pete Zaitcev <zaitcev@redhat.com>
To: John Weber <weber@nyc.rr.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.4 Sound Driver Problem
Date: Mon, 11 Feb 2002 13:27:25 -0500 [thread overview]
Message-ID: <20020211132725.A18726@devserv.devel.redhat.com> (raw)
In-Reply-To: <E16aKwN-0007Ro-00@the-village.bc.nu> <3C6809C2.1030808@nyc.rr.com>
In-Reply-To: <3C6809C2.1030808@nyc.rr.com>; from weber@nyc.rr.com on Mon, Feb 11, 2002 at 01:13:22PM -0500
> Date: Mon, 11 Feb 2002 13:13:22 -0500
> From: John Weber <weber@nyc.rr.com>
> I am looking at both 2.5.4 and 2.4.18-pre9.
OK. Marcelo is not removing virt_to_bus any time soon, so ymfpci
in 2.4.18 is not going to have it removed. There were some other
interesting fixes, so I want 2.4.18 to be testing those. Sure,
for 2.4.19 I can add pci_alloc_XXX. The patch to do it is in my
tree and I am using it on my laptop. It is not a priority though.
Linus tree is different. I feel pretty safe dumping all fixes
that I receive into it as soon as they get tested on my laptop.
If his sound stops working, he'll let me know pretty quick.
Thus, the ymfpci in 2.5.4 uses pci_alloc_consistent.
> In my copy of sound_alloc_dmap(), I see a direct call to
> __get_free_pages to allocate the buffer and a call to virt_to_bus.
This is wonderful, but how is this related to ymfpci?
Config.in makes you to build sound.o if you select
CONFIG_SOUND_YMFPCI, but that's pretty irrelevant.
The ymfpci should load fine without sound.o, it only needs
soundcore.o.
OTOH, if you just want to fix dmabuf.c, by all means be my guest.
-- Pete
P.S. I changed i810_audio to use pci_alloc_consistent too, it is
somewhere in dledford's queue.
next prev parent reply other threads:[~2002-02-11 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1013448601.14957.linux-kernel2news@redhat.com>
2002-02-11 17:46 ` Linux 2.5.4 Sound Driver Problem Pete Zaitcev
2002-02-11 18:12 ` Alan Cox
2002-02-11 18:13 ` John Weber
2002-02-11 18:27 ` Pete Zaitcev [this message]
2002-02-11 18:48 ` John Weber
[not found] ` <3C6816EC.2040406@nyc.rr.com>
2002-02-11 19:21 ` Pete Zaitcev
[not found] <fa.c0t1afv.1f02hrj@ifi.uio.no>
[not found] ` <fa.jvah72v.1h34cqd@ifi.uio.no>
2002-02-11 19:58 ` John Weber
2002-02-11 20:42 ` John Weber
2002-02-11 17:27 John Weber
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=20020211132725.A18726@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=weber@nyc.rr.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