From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] eth1394: dev file [Report about error: unknown bus]
Date: Wed, 20 Oct 2004 23:26:57 +0000 [thread overview]
Message-ID: <4176F441.9040806@osdl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Kay Sievers wrote:
> On Wed, Oct 20, 2004 at 01:44:58PM -0400, Paul Blazejowski wrote:
>
>>On Wed, 2004-10-20 at 15:17 +0200, Kay Sievers wrote:
>>
>>
>>>>'/class/net/eth1' properly (no device symlink) or the sysfs-support of
>>>>your device's driver needs to be fixed
>>>
>>>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.
>
>
> [CC: to the 1394 devel-list]
>
> The eth1394.c driver needs to create the symlinks in its sysfs
> representation to get support for modern userspace integration.
> Most networkd drivers use:
>
> SET_NETDEV_DEV(dev, &pdev->dev);
>
> to do that.
Paul,
Can you test this patch, please?
Thanks,
--
~Randy
[-- Attachment #2: eth1394_sysfs.patch --]
[-- Type: text/x-patch, Size: 443 bytes --]
linux-269-bk4
description
diffstat:=
diff -Naurp ./drivers/ieee1394/eth1394.c~eth1394_sysfs ./drivers/ieee1394/eth1394.c
--- ./drivers/ieee1394/eth1394.c~eth1394_sysfs 2004-10-20 16:01:51.765776760 -0700
+++ ./drivers/ieee1394/eth1394.c 2004-10-20 16:27:33.126454320 -0700
@@ -600,6 +600,7 @@ static void ether1394_add_host (struct h
}
SET_MODULE_OWNER(dev);
+ SET_NETDEV_DEV(dev, &host->device);
priv = netdev_priv(dev);
next reply other threads:[~2004-10-20 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 23:26 Randy.Dunlap [this message]
2004-10-21 4:09 ` [PATCH] eth1394: dev file [Report about error: unknown bus] Paul Blazejowski
2004-10-21 4:10 ` Randy.Dunlap
2004-10-21 7:57 ` Kay Sievers
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=4176F441.9040806@osdl.org \
--to=rddunlap@osdl.org \
--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).