linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Olaf Hering <olh@suse.de>,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: devices with more than one node
Date: Tue, 13 Jan 2004 23:01:47 +0000	[thread overview]
Message-ID: <20040113150147.A9902@beaverton.ibm.com> (raw)
In-Reply-To: <20040113212058.GA2595@kroah.com>; from greg@kroah.com on Tue, Jan 13, 2004 at 01:20:58PM -0800

On Tue, Jan 13, 2004 at 01:20:58PM -0800, Greg KH wrote:
> On Tue, Jan 13, 2004 at 10:11:22PM +0100, Olaf Hering wrote:
> >  On Tue, Jan 13, Greg KH wrote:
> > > On Tue, Jan 13, 2004 at 08:38:42PM +0100, Olaf Hering wrote:
> > > > inputdevices have also an event node attached.
> > > 
> > > Yes, and you get two different hotplug events, and udev just works,
> > > right?  (this is with the kernel patches I sent out last week...)
> > 
> > I tried the -mm tree, and /proc/bus/input/devices differs indeed. Havent
> > tried to feed udev with the data.
> 
> Look at /sys/class/input in the -mm kernel.  I didn't do anything with
> the /proc/bus/input stuff.
> 
> > > > Maybe I miss the obvious, but how do I match scsi as example? Not that
> > > > sg provides a sg 'dev' entry today, but an external PROGRAM could not
> > > > provide an relative symlink to sgN.
> > > 
> > > scsi needs to create a scsi_generic class (or some such name) and have
> > > it contain the sg information.  It should not be in the cdev directory
> > > like it currently is (that's badly broken and should have never made it
> > > in...)  That sg class can contain the symlink back to the device that it
> > > is associated with.
> > > 
> > > Does this help?
> > 
> > Yes. Do you have a patch for that? Or should the scsi people do it?
> 
> The scsi people should do it :)
> 
> But if pushed hard enough, I guess I could do it...
> I do need to make cdev disappear from the sysfs tree entirely anyway...
> 
> If only I had more time.  Anyone else want to do this?
> 
> thanks,
> 
> greg k-h

Don't forget to let the scsi people know ;-) cc-ing linux-scsi

st also needs changes.

Did anyone figure out how udev should handle the one tape device requiring
multiple minors (for open/close with/without rewind)? It really is a
single device requiring multiple dev entries.

For scsi_id support with udev, st needs to support SG_IO, AFAIUI it can
use similiar code as found in sd.c and sr.c.

-- Patrick Mansfield


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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

  reply	other threads:[~2004-01-13 23:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 19:38 devices with more than one node Olaf Hering
2004-01-13 19:46 ` Greg KH
2004-01-13 21:11 ` Olaf Hering
2004-01-13 21:20 ` Greg KH
2004-01-13 23:01   ` Patrick Mansfield [this message]
2004-01-13 23:18     ` Greg KH
2004-01-14  1:12       ` dougg
2004-01-14  1:26         ` Greg KH
2004-01-14 17:29 ` Olaf Hering
2004-01-14 17:39 ` Greg KH
2004-01-14 17:44 ` Greg KH
2004-01-14 19:15 ` Olaf Hering
2004-01-14 21:32 ` Greg KH
2004-01-14 21:35 ` Greg KH
2004-01-15  8:01 ` Vojtech Pavlik
2004-01-15  9:04 ` Olaf Hering
2004-01-15  9:19 ` Vojtech Pavlik
2004-01-15 21:18 ` Greg KH

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=20040113150147.A9902@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    /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).