From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Report about error: unknown bus]
Date: Wed, 20 Oct 2004 17:44:58 +0000 [thread overview]
Message-ID: <1098294298.4902.4.camel@blaze.homeip.net> (raw)
In-Reply-To: <1098244606.7230.7.camel@blaze.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Wed, 2004-10-20 at 15:17 +0200, Kay Sievers wrote:
Kay,
>
> Fine, I will go fix that tonight.
>
> > '/devices/pci0000:00/0000:00:0d.0/fw-host0' properly (unknown bus)
>
> Greg, any idea how to handle that properly? Should we exclude
> "fw-host*"? Or is it expected to have a "bus" and the firewire driver
> should be fixed instead?
>
> > '/class/net/eth1' properly (no device symlink)
>
> What driver creates the eth1 device? It needs to crete the "device" symlink
> and the maintainer should know.
eth1 Link encap:UNSPEC HWaddr
8A-1C-C7-FF-FF-00-20-ED-00-00-00-00-00-00-00-00
is created by the eth1394 driver.
>
> Thanks,
> Kay
>
Thanks,
Paul
--
FreeBSD -- The Power to Serve!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-20 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 3:56 [Report about error: unknown bus] Paul Blazejowski
2004-10-20 4:27 ` Kay Sievers
2004-10-20 5:33 ` Paul Blazejowski
2004-10-20 13:17 ` Kay Sievers
2004-10-20 17:05 ` Kay Sievers
2004-10-20 17:44 ` Paul Blazejowski [this message]
2004-10-20 17:48 ` Paul Blazejowski
2004-10-20 18:03 ` Kay Sievers
2004-10-20 20:44 ` Kay Sievers
2004-10-21 4:15 ` Paul Blazejowski
2004-10-21 8:11 ` Kay Sievers
2004-10-21 18:40 ` Paul Blazejowski
2004-10-21 19:58 ` Kay Sievers
2004-10-21 20:28 ` Paul Blazejowski
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=1098294298.4902.4.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.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).