From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tony Olech <tony.olech@elandigitalsystems.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Linux kernel development <linux-kernel@vger.kernel.org>,
PCMCIA Maintainence <linux-pcmcia@lists.infradead.org>,
David Hinds <dahinds@users.sourceforge.net>,
Jaroslav Kysela <perex@suse.cz>,
Bart Prescott <bart.prescott@elandigitalsystems.com>
Subject: Re: [PATCH] PCMCIA identification strings for cards manufactured by Elan
Date: Mon, 20 Nov 2006 15:29:27 +0000 [thread overview]
Message-ID: <20061120152927.GA26791@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1164032582.30853.36.camel@n04-143.elan.private>
On Mon, Nov 20, 2006 at 02:23:02PM +0000, Tony Olech wrote:
> Hi,
> The strings came from our company product database.
> I do not have the time to track down examples of each
> varient, but here are the two I have been testing with:
>
> Socket 0:
> product info: "Elan", "Serial+Parallel Port: SP230", "1.00",
> "KIT:K51477-006 "
> manfid: 0x015d, 0x4c45
> function: 2 (serial)
>
> Socket 1:
> product info: "Elan", "Serial Port: SL332", "1.01", "KIT:K51520-027
> "
> manfid: 0x015d, 0x4c45
> function: 2 (serial)
>
> AND NO, matching on function ID just randomly locked up the
> kernel, but now I think that was because of the "pdaudiocf"
> module and its MANF_ID/CARD_ID number matching.
The obvious question is - if you only remove the IDs from pdaudiocf, does
it then work?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-11-20 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 11:17 [PATCH] PCMCIA identification strings for cards manufactured by Elan Tony Olech
2006-11-20 12:51 ` Arjan van de Ven
2006-11-20 13:02 ` Russell King
2006-11-20 14:23 ` Tony Olech
2006-11-20 15:29 ` Russell King [this message]
2006-11-20 16:51 ` Tony Olech
2006-11-20 17:27 ` Russell King
2006-11-20 17:39 ` David Hinds
2006-11-20 17:45 ` Dominik Brodowski
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=20061120152927.GA26791@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bart.prescott@elandigitalsystems.com \
--cc=dahinds@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--cc=perex@suse.cz \
--cc=tony.olech@elandigitalsystems.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