From: Miles Lane <miles@megapathdsl.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alessandro Suardi <alessandro.suardi@oracle.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
tytso@mit.edu, guthrie@infonautics.com
Subject: Re: [PATCH] Re: PCMCIA serial CardBus support vanished in 2.4.3-pre3 and later
Date: 20 Mar 2001 10:20:02 -0800 [thread overview]
Message-ID: <auto-000017105057@megapathdsl.net> (raw)
In-Reply-To: <3AB77944.20018B9A@mandrakesoft.com>
In-Reply-To: <Pine.LNX.3.96.1010320080638.18764C-100000@mandrakesoft.mandrakesoft.com> <3AB77485.3BAB3AFE@oracle.com> <3AB77944.20018B9A@mandrakesoft.com>
On 20 Mar 2001 10:37:40 -0500, Jeff Garzik wrote:
> On closer inspection, that patch I linked to appears to be incomplete.
>
> Can you try the attached patch, to see if it fixes the
> absence-of-serial_cb problem?
>
> Thanks,
>
> Jeff
>
>
> P.S. I'm surprised serial_cb in 2.4 worked at all, for anybody. I guess
> they must be using pcmcia_cs's serial_cb, not the kernel's serial_cb...
Yes. Well, this just strengthens the case for getting PCMCIA support
migrated fully into the kernel tree so that we can pry people's finger
loose from pcmcia_cs. David Woodhouse is planning to take up this
project early in the 2.5 development cycle.
It's kind of a shame that more testing of the 2.4.x Cardbus/PCMCIA
drivers isn't happening, because a lot of the Cardbus/PCMCIA support
in the kernel tree is really just fine. We should all be using it and
testing it and reporting bugs.
One of the work items will be getting the in-kernel PCMCIA support
to work with the new hotplug stuff.
Miles
prev parent reply other threads:[~2001-03-20 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AB759F4.F9F5F35D@oracle.com>
2001-03-20 14:11 ` PCMCIA serial CardBus support vanished in 2.4.3-pre3 and later Jeff Garzik
2001-03-20 15:17 ` Alessandro Suardi
2001-03-20 15:37 ` [PATCH] " Jeff Garzik
2001-03-20 18:20 ` Miles Lane [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=auto-000017105057@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=alessandro.suardi@oracle.com \
--cc=guthrie@infonautics.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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