public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: SysFS, module names and .name
Date: Sat, 03 Sep 2005 00:17:57 +0200	[thread overview]
Message-ID: <4318CF95.5040801@rulez.cz> (raw)
In-Reply-To: <20050902155338.GA13648@kroah.com>

Yes, I am rather interested -- could you please provide details about 
this method?

Thanks in advance.

  - iSteve

Greg KH wrote:
> On Thu, Sep 01, 2005 at 10:28:56PM +0200, iSteve wrote:
> 
>>Greetings,
>>in sysfs, /sys/bus/*/drivers lists the driver names, with their exported 
>>.name (eg. '.name = "EMU10K1_Audigy"' in the module code, from now on 
>>'driver name'). In /sys/modules, the kernel modules are listed with 
>>their module name, eg. snd_emu10k1. However, it seems to me that in 
>>sysfs, there is no way in particular to tell, which module has which 
>>.name. That is, that snd_emu10k1 is EMU10K1_Audigy and vice versa.
>>
>>I wonder whether it wouldn't be possible to add a symlink to the 
>>particular module from the driver, and/or from the module to the driver, 
>>so the list of devices handled by the module and the module name would 
>>be accessible. This way, I would know which driver name corresponds to 
>>which module name and vice versa.
> 
> 
> It's already automatically created for some bus drivers (like USB).  I
> had a simple patch to enable this for PCI, but haven't gotten around to
> changing every single pci driver to enable it.  If you want to do so,
> it isn't tough at all.
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2005-09-02 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 20:28 SysFS, module names and .name iSteve
2005-09-02 15:53 ` Greg KH
2005-09-02 22:17   ` iSteve [this message]
2005-09-03  5:31     ` Greg KH
2005-09-03 10:55       ` James Courtier-Dutton

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=4318CF95.5040801@rulez.cz \
    --to=isteve@rulez.cz \
    --cc=greg@kroah.com \
    --cc=linux-kernel@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