From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: pci.handmap equivalent for 2.6?
Date: Wed, 15 Sep 2004 22:27:23 +0000 [thread overview]
Message-ID: <200409151527.23940.david-b@pacbell.net> (raw)
In-Reply-To: <200409152139.i8FLdfu6025598@mailhost.alsc.com>
On Wednesday 15 September 2004 3:12 pm, Marco d'Itri wrote:
> On Sep 15, Alex Dininno <alex@alsc.com> wrote:
>
> >
> > system from handling my stand-alone driver module. I see that there is a
> > usb.handmap file in the latest hotplug tarball (hotplug-2004_04_01.tar)
> > - is
> > there some way to specify stand-alone pci devices in a way similar to the
> > usb.handmap file?
> You are lucky, a patch to do this has been submitted to debian a few
> hours ago: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug'1843 .
Most "usb.handmap" entries were needed because there was no
input hotplugging way back when 2.4.0 shipped.
Why would a PCI driver, properly installed with "depmod -a", need
any sort of "handmap" mechanism?
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
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
next prev parent reply other threads:[~2004-09-15 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 21:39 pci.handmap equivalent for 2.6? Alex Dininno
2004-09-15 22:12 ` Marco d'Itri
2004-09-15 22:27 ` David Brownell [this message]
2004-09-15 22:48 ` Marco d'Itri
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=200409151527.23940.david-b@pacbell.net \
--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 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).