Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>,
	alsa-user@lists.sourceforge.net,
	alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] fm801 driver status?
Date: Fri, 13 Dec 2002 18:02:08 +0100	[thread overview]
Message-ID: <s5hel8lua27.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DFA1166.2020409@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

At Fri, 13 Dec 2002 17:57:10 +0100,
Friedrich Ewaldt wrote:
> 
> Takashi Iwai schrieb:
> [...]
>  >>00:0b.0 Multimedia audio controller: Fortemedia, Inc Xwave QS3000A
>  >>[FM801] (rev a0)
>  >>        Subsystem: Fortemedia, Inc: Unknown device 1319
>  >>        Flags: bus master, medium devsel, latency 40, IRQ 10
>  >>        I/O ports at ec00 [size=128]
>  >>        Capabilities: [dc] Power Management version 1
>  >>
>  >>00:0b.1 Input device controller: Fortemedia, Inc Xwave QS3000A [FM801]
>  >>(rev a0)
>  >>        Subsystem: Fortemedia, Inc: Unknown device 1319
>  >>        Flags: bus master, medium devsel, latency 40, IRQ 11
>  >>        Capabilities: [dc] Power Management version 1
>  >
>  >
>  > i need the pci vendor/device id for them.
>  > could you give me the output of "lspci -n" for two devices above?
>  > the audio chip should be 0x1319:0x0801.
>  >
> 
> lspci -n output:
> 
> 00:0b.0 Class 0401: 1319:0801 (rev a0)
> 00:0b.1 Class 0980: 1319:0801 (rev a0)

thanks, could you try the attached patch?
at least, the weird messages for allocation of invalid i/o ports
should disappear.  not sure whether this cures the lock-up problem,
though.


Takashi

[-- Attachment #2: fm801-fix.dif --]
[-- Type: application/octet-stream, Size: 599 bytes --]

Index: alsa-kernel/pci/fm801.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/fm801.c,v
retrieving revision 1.20
diff -u -r1.20 fm801.c
--- alsa-kernel/pci/fm801.c	9 Dec 2002 10:54:45 -0000	1.20
+++ alsa-kernel/pci/fm801.c	13 Dec 2002 16:59:43 -0000
@@ -164,7 +164,7 @@
 };
 
 static struct pci_device_id snd_fm801_ids[] __devinitdata = {
-	{ 0x1319, 0x0801, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /* FM801 */
+	{ 0x1319, 0x0801, PCI_ANY_ID, PCI_ANY_ID, PCI_CLASS_MULTIMEDIA_AUDIO << 8, 0xffff00, 0, },   /* FM801 */
 	{ 0, }
 };
 

  reply	other threads:[~2002-12-13 17:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 14:45 fm801 driver status? Friedrich Ewaldt
2002-12-12 15:08 ` [Alsa-user] " Takashi Iwai
2002-12-12 16:27   ` Friedrich Ewaldt
2002-12-12 17:32     ` Takashi Iwai
2002-12-13  9:53       ` Thierry Vignaud
2002-12-13 11:17         ` Friedrich Ewaldt
2002-12-13 16:29           ` Takashi Iwai
2002-12-13 16:33             ` Thierry Vignaud
2002-12-13 16:57             ` Friedrich Ewaldt
2002-12-13 17:02               ` Takashi Iwai [this message]
2002-12-13 18:24                 ` Friedrich Ewaldt
2002-12-16 15:12                   ` Takashi Iwai
2002-12-16 20:55                     ` Friedrich Ewaldt
2002-12-17 18:11                       ` Takashi Iwai
2002-12-18 13:28                         ` Friedrich Ewaldt
2002-12-19 11:31                           ` Takashi Iwai
2002-12-19 20:21                             ` Friedrich Ewaldt
2002-12-13 11:15       ` Friedrich Ewaldt

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=s5hel8lua27.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=friedrich.ewaldt@gmx.de \
    --cc=tvignaud@mandrakesoft.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