From: Stephen Hemminger <shemminger@vyatta.com>
To: Kurt Van Dijck <kurt.van.dijck@eia.be>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Wolfgang Grandegger <wg@grandegger.com>,
netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH v2] allow access to sysfs_groups member
Date: Mon, 16 Nov 2009 08:46:12 -0800 [thread overview]
Message-ID: <20091116084612.3654bdd1@nehalam> (raw)
In-Reply-To: <20091114165408.GA283@e-circ.dyndns.org>
On Sat, 14 Nov 2009 17:54:09 +0100
Kurt Van Dijck <kurt.van.dijck@eia.be> wrote:
> On Fri, Nov 13, 2009 at 02:27:38PM -0800, Stephen Hemminger wrote:
> > On Fri, 13 Nov 2009 11:51:57 +0100
> > Kurt Van Dijck <kurt.van.dijck@eia.be> wrote:
> [...]
> > EXPORT_SYMBOL_GPL() for all device/sysfs related stuff.
> Ok, no problem
> >
> > Also, need some way to BUG() if this is done after device has
> > been registered.
> Ok. I gave it a try. I _think_ I did it write, but a second look would
> not harm :-). I was not able to run a real test yet.
> >
> > Another way to add sub-directories which is what bridge, bonding,
> > and others do is to use another kobject. I think this is what you
> > want for the case of two CAN objects under one netdevice.
> In fact, I wanted to add this for cards that have multiple seperate CAN
> network device, combined on 1 PCI or PCMCIA device.
> In the 'add network' uevent, a udev rule could find properties of the
> card (device/ symlink). Right now, there is no way to tell if a network
> device is bus 1 or 2 on the card. in CAN, there's no such thing as a MAC
> address.
> I encountered this issue with a softing CAN card (not yet in mainline),
> and there are other drivers in the socketCAN queue that have the same
> problem.
>
> The ethernet cards with multiple busses (that I've seen yet :-) )
> combine multiple PCI devices on 1 card, and identification of the
> 'instance on the card' can happen with the sysfs properties delivered by
> the PCI bus.
> CAN devices with multiple busses typically are combined all together on
> 1 single device on the PCI or PCMCIA bus.
>
> So, I wanted to add a 'channel' property in /sys/class/net/canX, which
> could indicate the instance on the device. Such property must be
> installed by the driver, not the bus the device is on.
> This patch allows me to have this channel property present at the moment
> of the uevent.
>
> I can imagine other subsystems may benefit from this too.
Okay by me.
Acked-by: Stephen Hemminger <shemminger@vyatta.com>
--
next prev parent reply other threads:[~2009-11-16 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 10:51 [net-next-2.6 PATCH] allow access to sysfs_groups member Kurt Van Dijck
2009-11-13 22:27 ` Stephen Hemminger
2009-11-14 16:54 ` [net-next-2.6 PATCH v2] " Kurt Van Dijck
2009-11-16 16:46 ` Stephen Hemminger [this message]
2009-11-17 16:21 ` Kurt Van Dijck
2009-11-18 15:43 ` Kurt Van Dijck
2009-11-18 16:08 ` David Miller
2009-11-18 16:41 ` Kurt Van Dijck
2009-11-18 17:57 ` David Miller
2009-11-18 20:57 ` Kurt Van Dijck
2009-11-18 20:59 ` Kurt Van Dijck
2009-11-18 21:08 ` David Miller
2009-11-18 21:42 ` Kurt Van Dijck
2009-11-20 1:11 ` Eric W. Biederman
2009-11-20 10:21 ` Kurt Van Dijck
2009-11-20 16:32 ` Eric W. Biederman
2009-11-21 11:47 ` Kurt Van Dijck
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=20091116084612.3654bdd1@nehalam \
--to=shemminger@vyatta.com \
--cc=kurt.van.dijck@eia.be \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/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).