From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miles Lane Date: Wed, 28 Feb 2001 05:14:15 +0000 Subject: Re: OT(?) -- Should the net.agent script cause "ifup lo" to be run? Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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