linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simone Gotti <simone.gotti@email.it>
To: linux-hotplug@vger.kernel.org
Subject: Re: Little script for ISAPNP hotplug
Date: Sat, 24 Apr 2004 09:15:45 +0000	[thread overview]
Message-ID: <200404241115.45094.simone.gotti@email.it> (raw)
In-Reply-To: <200404092044.54429.simone.gotti@email.it>

On Friday 23 April 2004 18:19, Bill Nottingham wrote:
> Marco d'Itri (md@Linux.IT) said:
> > On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:
> > > I've did this agent (that is attached) and now I can manage the
> > > coldplugging of modules like 8250_pnp, parport_pc, ns558 etc...
> >
> > Your work is very interesting, it could help automatically loading some
> > of the drivers which currently cannot be autodetected and annoy udev
> > users (e.g. 8250, rtc, parport and floppy).
>
> Well, it can certainly detect the floppy *controller*. The drive
> is still stuck as 'whatever the BIOS configured', yes?
>
> Bill

The floppy module doesn't export any isapnp ids, so by now it can't be 
autoloaded. 
My script (like all hotplug scripts) find that there's a floppy controller 
reading from /sys/bus/pnp/devices, but then in modules.isapnpmap there's 
nothing that tell what module is related to that IDs.

I don't know how the floppy module works, I don't know if these module is 
related only to isapnp floopy controller or it manage other kinds.

If it's only related to isapnp floppy controllers then it can easily patched 
like I've did with rtc, pcspkr and psmouse. 
If you are sure that this is the right way to do the things I'll do a patch 
for it too.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-04-24  9:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09 18:44 Little script for ISAPNP hotplug Simone Gotti
2004-04-10 17:16 ` Simone Gotti
2004-04-11 17:09 ` Simone Gotti
2004-04-12  2:25 ` Alexander E. Patrakov
2004-04-12  9:57 ` Simone Gotti
2004-04-13 15:47 ` Alexander E. Patrakov
2004-04-13 17:06 ` Simone Gotti
2004-04-18 19:10 ` Simone Gotti
2004-04-22 18:14 ` Simone Gotti
2004-04-22 19:28 ` Marco d'Itri
2004-04-23  9:42 ` Simone Gotti
2004-04-23 16:19 ` Bill Nottingham
2004-04-23 16:23 ` Marco d'Itri
2004-04-23 16:30 ` Bill Nottingham
2004-04-24  9:15 ` Simone Gotti
2004-04-24  9:15 ` Simone Gotti [this message]

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=200404241115.45094.simone.gotti@email.it \
    --to=simone.gotti@email.it \
    --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).