All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.4.0 Patch for 3c575
Date: Thu, 11 Jan 2001 18:15:29 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97923891732229@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97923399516514@msgid-missing>

> I was thinking of just having a new keyword in /etc/pcmcia/config to
> say that certain drivers are "hotplug", which would mean to ignore
> those config entries under a 2.4 kernel with hotplug support.

That's probably a workable solution.  Though I suspect the pcmcia_cs
package will want a way to detect that hotplug PCI is running, so it
will do the right thing with such cardbus drivers in atypical setups.

Have you looked at the (PCI-less) /etc/hotplug stuff I sent around?
We could arrange that the next iteration of that use some sort of
config file in /etc/hotplug to expose such information; I can toss
in the PCI/Cardbus support, but it'll be short of testing.  The same
stuff could let the /sbin/hotplug command itself show status info.

> -- Dave



_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-01-11 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 17:25 2.4.0 Patch for 3c575 Miles Lane
2001-01-11 17:29 ` David Hinds
2001-01-11 18:15 ` David Brownell [this message]
2001-01-11 19:43 ` Miles Lane
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11  1:44 Aaron Eppert
2001-01-11  2:56 ` Miles Lane
2001-01-11  4:15   ` David Hinds
2001-01-11  7:21     ` Miles Lane
2001-01-11  7:56       ` David Hinds
2001-01-11 11:55     ` Andrew Morton
2001-01-11 17:26       ` David Hinds
2001-01-11  7:32   ` Miles Lane

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-97923891732229@msgid-missing \
    --to=david-b@pacbell.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.