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 17:27:31 +0000 [thread overview]
Message-ID: <20061120172731.GC26791@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1164041509.30853.48.camel@n04-143.elan.private>
On Mon, Nov 20, 2006 at 04:51:48PM +0000, Tony Olech wrote:
> Hi Russell,
> if I take out the patches to parport_cs and serial_cs,
> leaving in only the patch to "pdaudiocf" our SP230 card
> no longer works - it does not lock up the kernel, admittedly,
> and the serial only card does works, but we would like
> all are cards to just work.
Sounds like function ID matching is broken. Dominik?
> ALSO, I have found no way to force a particular 16-bit
> pcmcia card to be handled by a particular module in a
> similar way to the USB generic serial driver module
> parameter. Have I misssed the obvious? Or is that a
> desirable feature that have been taken out of the David
> Hinds original implementation?
Again, Dominik's area of expertise.
--
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 17:27 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
2006-11-20 16:51 ` Tony Olech
2006-11-20 17:27 ` Russell King [this message]
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=20061120172731.GC26791@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 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.