linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] eth1394: dev file [Report about error: unknown bus]
Date: Thu, 21 Oct 2004 04:10:29 +0000	[thread overview]
Message-ID: <417736B5.7070009@osdl.org> (raw)
In-Reply-To: <4176F441.9040806@osdl.org>

Paul Blazejowski wrote:
> On Wed, 2004-10-20 at 16:26 -0700, Randy.Dunlap wrote:
> 
>>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 applied the patch to kernel 2.6.9 and now eth1394 creates symlink
> under /sys/class/net/eth2
> 
> lrwxrwxrwx  1 root root    0 2004-10-20 23:58 device
> -> ../../../devices/pci0000:00/0000:00:0d.0/fw-host0/
> 
> Thank you,
> 
> Paul

So is this correct?  Does it do the right thing?

-- 
~Randy


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-10-21  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 23:26 [PATCH] eth1394: dev file [Report about error: unknown bus] Randy.Dunlap
2004-10-21  4:09 ` Paul Blazejowski
2004-10-21  4:10 ` Randy.Dunlap [this message]
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=417736B5.7070009@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).