From: Tony Vroon <tony@vroon.org>
To: "Vedran Miletić" <rivanvx@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: emu10k1: fix device names for Live!/Audigy1/2/4/E-mu and coding style
Date: Wed, 22 Oct 2008 11:27:19 +0100 [thread overview]
Message-ID: <1224671239.4001.19.camel@localhost> (raw)
In-Reply-To: <s5hprltj71z.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]
Vedran,
With regard to the SB0228 comment, just make sure you're reading the
product ID from the correct location. The silk-screened number on the
PCB will always end in 0, but if you read the serial number label on the
back of the card, you'll find the real product ID.
Generally something along the lines of M1SB0228xxxxxxxxx
Skip the first two characters, read the next 6. This works on Creative
soundcards that are Live! or newer, before then their serial numbers
looked different.
This may help you find more specific product IDs for other OEM Live! &
Audigy boards.
Regards,
Tony V.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-10-22 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 12:33 [PATCH] ALSA: emu10k1: fix device names for Live!/Audigy1/2/4/E-mu and coding style Vedran Miletić
2008-10-20 6:15 ` Takashi Iwai
2008-10-21 9:00 ` Vedran Miletić
2008-10-21 15:45 ` Takashi Iwai
2008-10-21 17:18 ` Vedran Miletić
2008-10-22 9:46 ` Takashi Iwai
2008-10-22 10:27 ` Tony Vroon [this message]
2008-10-22 11:07 ` Vedran Miletić
-- strict thread matches above, loose matches on Subject: below --
2008-10-22 12:31 Tony Vroon
2008-10-22 15:22 ` Vedran Miletić
[not found] ` <48FF96AE.6030407@gmail.com>
2008-10-23 10:14 ` Vedran Miletić
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=1224671239.4001.19.camel@localhost \
--to=tony@vroon.org \
--cc=alsa-devel@alsa-project.org \
--cc=rivanvx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.