From: Kristian Hogsberg <hogsberg@users.sourceforge.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: /sbin/hotplug (from hotplug-core-2001_09_19-1 and hotplug-utils-2001_09_19-1) doesn't work for F
Date: Wed, 07 Nov 2001 11:38:39 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100513310318128@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100509894621625@msgid-missing>
Greg KH <greg@kroah.com> writes:
> On Tue, Nov 06, 2001 at 05:34:01PM -0800, Miles Lane wrote:
> > Nov 6 16:34:45 stomata /etc/hotplug/ieee1394.agent: ... no drivers for IEEE1394 product 0x00005e/0x00005e/0x000002
>
> And do you have those drivers listed in modules.ieee1394map?
This is an issuse with the 1394 drivers, or in fact two issues: first,
the config rom, which describes your linux box' capabilities as an
1394 node, says that your box supports ipv4 and ipv6 over 1394, which
it doesn't. We are trying to determine an interface for dynamically
changing the config rom, and I wanted to sort that out before changing
anything. Second, the node probing functionality, which eventually
calls the hotplug helper, scans the config rom for your linux box as
if it was a remote device and tries to load drivers for the ipv4 and
ipv6 functionality your box claims to have...
The upshot of all this: there's some bogus going on in the detection
code. This is easy to fix, and you can safely ignore those warnings.
Kristian
_______________________________________________
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
prev parent reply other threads:[~2001-11-07 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 2:09 /sbin/hotplug (from hotplug-core-2001_09_19-1 and hotplug-utils-2001_09_19-1) doesn't work for F Greg KH
2001-11-07 11:38 ` Kristian Hogsberg [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=marc-linux-hotplug-100513310318128@msgid-missing \
--to=hogsberg@users.sourceforge.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).