From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need new modutils aliases for 2.4.0? (Was) Re: Cannothotplugcardbus
Date: Fri, 26 Jan 2001 06:44:01 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98049136431655@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98045890309512@msgid-missing>
> David Hinds wrote:
>
> On Thu, Jan 25, 2001 at 01:43:18PM -0800, Miles Lane wrote:
> > David Brownell wrote:
> > >
> > > My thoughts exactly. 2.4 should be hotplugging the 2.4 kernel's
> > > Cardbus drivers ... unbundled pcmcia_cs drivers shouldn't be used,
> > > as a rule, the kernel drivers get more attention (and the expectation
> > > is that'll continue).
>
> Actually I think all the evidence suggests that at this point the
> unbundled pcmcia drivers still get considerably more attention than
> the kernel drivers, at least at the end user level.
Well, during the 2.5 time-frame, the kernel developers will
probably put more effort into improving the kernel drivers,
while you continue (?) to work on improving the pcmcia-cs
drivers. I agree with you that the pcmcia-cs drivers are
getting *way* more use and testing. I feel frustrated about
this. We could be much further along if one or two kernel
developers devoted their focus to getting PCMCIA/Cardbus
development and testing into good shape. Currently, people
who are willing to test the kernel drivers don't have a
"champion" to turn to. You have done an admirable job of
gathering the community of users and serving them.
I'd be willing to do a lot of driver testing, but it requires
far more hardware than I have access to.
I do think that you, David, could help by evangelizing testing
of the kernel drivers. Most of what people use PCMCIA/Cardbus
devices for is adjunct to mission-critical work. That means
that if folks are willing to rebuild their kernel and do some
testing, they can boot back into their stable, comfy environments
pretty easily. It would be a tremendous help if testers would
step up and simply tell us what's broken!
> > I would like to explore the "mutual-noninterference pact"
> > between Cardmgr and /sbin/hotplug. It seems important to
> > get right. Obviously, David Hinds will play a big role
> > in this.
>
> I have added code to cardmgr to parse modules.pcimap to figure out
> which cards should be handled by the hotplug stuff. I still have a
> few things to clean up but I don't think it will be hard.
Wow! That's great news! Thanks for working on this.
Miles
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-26 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 21:43 Need new modutils aliases for 2.4.0? (Was) Re: Cannothotplugcardbus Miles Lane
2001-01-26 6:44 ` Miles Lane [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 19:22 Need new modutils aliases for 2.4.0? (Was)Re:Cannothotplugcardbus David Brownell
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=marc-linux-hotplug-98049136431655@msgid-missing \
--to=miles@megapathdsl.net \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).