From: Adrian Bunk <bunk@stusta.de>
To: Jon Mason <jdmason@us.ibm.com>
Cc: Muli Ben-Yehuda <mulix@mulix.org>,
Jiri Slaby <slaby@liberouter.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware
Date: Thu, 12 Jan 2006 23:00:39 +0100 [thread overview]
Message-ID: <20060112220039.GX29663@stusta.de> (raw)
In-Reply-To: <20060112214719.GE17539@us.ibm.com>
On Thu, Jan 12, 2006 at 03:47:19PM -0600, Jon Mason wrote:
> On Thu, Jan 12, 2006 at 10:07:35PM +0200, Muli Ben-Yehuda wrote:
> > On Thu, Jan 12, 2006 at 08:28:30PM +0100, Jiri Slaby wrote:
> >
> > > You should change alsa driver (sound/pci/trident/trident.c), rather than this,
> > > which will be removed soon, I guess. And, additionally, could you change that
> > > lines to use PCI_DEVICE macro?
> >
> > This driver is not up for removal soon, as it supports a device that
> > the alsa driver apparently doesn't (the INTERG_5050). As for
> > PCI_DEVICE, agreed. Jon, feel like patching it up?
>
> Patches to follow.
>
> After looking at the ALSA driver, it doesn't support PCI IDs for
> ALI_5451 or CYBER5050. Someone should look into porting any necessary
> code from sound/oss/trident.c to sound/pci/trident/trident.c
CYBER5050 is discussed in ALSA bug #1293 (tester wanted).
ALI_5451 is supported by the snd-ali5451 driver.
> Thanks,
> Jon
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-12 22:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 17:50 [PATCH] Prevent trident driver from grabbing pcnet32 hardware Jon Mason
2006-01-12 19:28 ` Jiri Slaby
2006-01-12 19:34 ` Jiri Slaby
2006-01-12 20:07 ` Muli Ben-Yehuda
2006-01-12 21:15 ` Lee Revell
2006-01-12 21:58 ` Adrian Bunk
2006-01-12 22:06 ` Lee Revell
2006-01-12 22:11 ` Jon Mason
2006-01-12 22:46 ` Adrian Bunk
2006-01-12 21:47 ` Jon Mason
2006-01-12 22:00 ` Adrian Bunk [this message]
2006-01-12 22:09 ` Jan Engelhardt
2006-01-12 22:20 ` Jon Mason
2006-01-12 22:42 ` Lee Revell
2006-01-12 22:52 ` Adrian Bunk
2006-01-12 22:55 ` Lee Revell
2006-01-13 10:16 ` Alan Cox
2006-01-12 23:32 ` Old hardware (was Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware) Lee Revell
2006-01-12 23:52 ` Bob Copeland
2006-01-13 10:28 ` [PATCH] Prevent trident driver from grabbing pcnet32 hardware Alan Cox
2006-01-13 17:55 ` Lee Revell
2006-01-13 11:37 ` Muli Ben-Yehuda
2006-01-13 12:23 ` Adrian Bunk
2006-01-13 12:32 ` Muli Ben-Yehuda
2006-01-13 15:24 ` Adrian Bunk
2006-01-13 15:36 ` Muli Ben-Yehuda
2006-01-12 22:08 ` Jon Mason
2006-01-12 20:49 ` pcnet32 devices with incorrect trident vendor ID Daniel Drake
2006-01-12 20:57 ` Matthew Wilcox
2006-01-12 21:03 ` Daniel Drake
2006-01-12 21:05 ` Matthew Wilcox
2006-01-12 21:22 ` Bill Nottingham
2006-01-12 21:24 ` Bill Nottingham
2006-01-12 22:23 ` Don Fry
2006-01-12 22:33 ` Jon Mason
2006-01-12 21:05 ` Lennart Sorensen
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=20060112220039.GX29663@stusta.de \
--to=bunk@stusta.de \
--cc=jdmason@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=slaby@liberouter.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;
as well as URLs for NNTP newsgroup(s).