From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Tony Olech <tony.olech@elandigitalsystems.com>
Cc: 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 Elan -- second attempt
Date: Mon, 27 Nov 2006 21:05:41 -0500 [thread overview]
Message-ID: <20061128020541.GD21472@isilmar.linta.de> (raw)
In-Reply-To: <200611201306.kAKD6gRt008347@imap.elan.private>
On Mon, Nov 20, 2006 at 01:04:39PM +0000, Tony Olech wrote:
> patch against linux kernel 2.6.18 to add PCMCIA identification strings
> From: Tony Olech <tony.olech@elandigitalsystems.com>
>
> In older versions of the linux kernel it was sufficient for the
> 16-bit PCMCIA card manufacturer to distribute or make available
> a text configuration file along with the physical cards. Such a
> file with an extension of ".conf" and placed in the /etc/pcmcia
> very easily enabled new hardware without rebuilding the kernel,
> however with the new scheme of things, having found no userland
> solution to the problem of new 16bit pcmcia card identification
> this patch enumerates Elan Digital Systems strings.
>
> In addition, for the ID strings to result in the correct module
> being loaded, the too wide matching criterion of the PDaudioCF
> card needs to have the MANF_ID/CARD_ID numbers replaced by the
> more specific PROD_ID1 and PROD_ID2 strings. It is unfortunate
> that otherwise the pdaudiocf module is loaded whenever an ELAN
> pcmcia card is inserted, resulting in various random lockups
Applied to pcmcia-2.6, thanks.
Dominik
prev parent reply other threads:[~2006-11-28 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 13:04 [PATCH] PCMCIA identification strings for Elan -- second attempt Tony Olech
2006-11-20 17:49 ` Dominik Brodowski
2006-11-21 8:53 ` Tony Olech
2006-11-21 13:28 ` Dominik Brodowski
2006-11-21 13:58 ` Tony Olech
2006-11-28 2:04 ` Dominik Brodowski
2006-11-28 2:05 ` Dominik Brodowski [this message]
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=20061128020541.GD21472@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=bart.prescott@elandigitalsystems.com \
--cc=dahinds@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--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