linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run?
Date: Wed, 28 Feb 2001 05:14:15 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98333719126662@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98309074821805@msgid-missing>

David Hinds wrote:

> On Mon, Feb 26, 2001 at 10:23:37PM -0800, Miles Lane wrote:
> 
>> This isn't true.  The 2.4.x kernel drivers should handle virtually
>> all Cardbus *and* PCMCIA devices.  At least, that's what David
>> Hinds told me.  So, if you compile a 2.4.x kernel with Cardbus
>> and i82365 and build the necessary drivers, you should be able 
>> to load the modules and use your PCMCIA devices.  You'd just
>> build pcmcia_cs support in order to get the cardmgr and cardctl
>> programs and the various config and opts files.  If you do this,
>> then pcmcia_cs shouldn't do any "beeping" during the boot process,
>> because all PC Cards will be configured by /sbin/hotplug.
>
> Err no.  2.4.x kernel drivers exist for most of the 16-bit PCMCIA
> cards supported by pcmcia-cs.  But they are not hotplug drivers; only
> the Cardbus drivers are hotplug aware.  No 16-bit PC Cards are
> configured by /sbin/hotplug.

Hmm, okay.  Sorry I overlooked the need to hotplug-enable the
PCMCIA drivers in the kernel tree.

>> David Hinds' recent cardmgr releases should already have the 
>> work-around built in to not attempt to configure any devices 
>> that 2.4.x kernel hotplugging will handle.  NOTE:  This is *not* 
>> just for Cardbus PC Cards. 
> 
> Yes it is just for CardBus cards.  And it will actually require a
> small one-line kernel patch which I haven't submitted yet.

When do you plan to submit your patch?

>> As a reminder, here is David Hinds list of work items related
>> to getting PCMCIA support into the kernel (the recent design
>> work done by Adam Richter, Oliver Neukum and others overhauls
>> portions of this list):
> 
> As far as I know none of the things I listed are done yet.  Is that
> not correct?

They aren't done.  In fact, the work on the list is still in the
design discussion phase.  The discussion got a bit myopically
focussed on the problem of getting hotplug event handling 
implemented in a really sensible and race-free way.  Adam Richter
and Oliver Neukum have reached an agreement between them about
a design solution.  A message was sent to the list containing
the design.  So far, noone has given them feedback.  Hopefully,
once the event handling design is agreed upon, the discussion
will get back to addressing your list of issues and we'll 
come up with a general design and development plan.  

If you are willing to give feedback on the event handling
design, please read Adam's message with the subject:

	Update on hot plugging serialization without
	kernel event queuing

The message was sent on 02/24/01 at 8:25pm.

Thanks,
	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

  parent reply	other threads:[~2001-02-28  5:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-25  8:47 OT(?) -- Should the net.agent script cause "ifup lo" to be run? Miles Lane
2001-02-25 10:03 ` Adam J. Richter
2001-02-25 21:37 ` Bill Nottingham
2001-02-25 23:45 ` David Brownell
2001-02-26  0:38 ` Bill Nottingham
2001-02-26  3:40 ` David Brownell
2001-02-26  4:12 ` Bill Nottingham
2001-02-26  4:14 ` Bill Nottingham
2001-02-26  6:59 ` Miles Lane
2001-02-26  7:17 ` Miles Lane
2001-02-26 16:50 ` David Brownell
2001-02-26 17:31 ` David Brownell
2001-02-26 19:52 ` Bill Nottingham
2001-02-26 22:08 ` David Brownell
2001-02-26 22:14 ` David Brownell
2001-02-26 22:17 ` David Brownell
2001-02-26 22:24 ` Bill Nottingham
2001-02-26 22:30 ` Bill Nottingham
2001-02-26 22:48 ` David Brownell
2001-02-27  6:23 ` Miles Lane
2001-02-27  6:46 ` Miles Lane
2001-02-27  7:17 ` Miles Lane
2001-02-27  7:23 ` Miles Lane
2001-02-27  7:54 ` David Hinds
2001-02-28  5:14 ` Miles Lane [this message]
2001-02-28 16:50 ` David Brownell
2001-02-28 17:24 ` David Hinds
2001-03-01  4:37 ` David Brownell
2001-03-01  5:27 ` Bill Nottingham
2001-03-01  5:34 ` Bill Nottingham
2001-03-01  5:45 ` David Hinds
2001-03-01 17:27 ` 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-98333719126662@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).