All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 25 Jan 2001 21:43:18 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98045890309512@msgid-missing> (raw)

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).
> 
> I think Miles still needs to get that "pci.agent" patch, which
> should help it read those variables correctly.  After we see more
> reports of that behaving, we can start to test "pcimodules".
> 
> (No, "/sbin/hotplug" has nothing to do with "cardmgr", they still
> need some sort of mutual-noninterference pact ...)

Cool.  PCI hotplugging is working for my Cardbus cards now.

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.

	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

             reply	other threads:[~2001-01-25 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 21:43 Miles Lane [this message]
2001-01-26  6:44 ` Need new modutils aliases for 2.4.0? (Was) Re: Cannothotplugcardbus Miles Lane
  -- 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-98045890309512@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 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.