linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dougg@torque.net
To: Greg KH <greg@kroah.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>, 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: Wed, 14 Jan 2004 01:12:56 +0000	[thread overview]
Message-ID: <1074042776.4004979822819@wwws.torque.net> (raw)
In-Reply-To: <20040113231813.GA7409@kroah.com>

Quoting Greg KH <greg@kroah.com>:

> On Tue, Jan 13, 2004 at 03:01:47PM -0800, Patrick Mansfield wrote:
> > Don't forget to let the scsi people know ;-) cc-ing linux-scsi
> 
> Ok, here goes:
> 
> linux-scsi, DO NOT USE THE cdev sysfs directory.  It will be going away
> as soon as I get around to writing the patch for it.  Putting the sg
> symlink in there is not the proper place.

Greg,
Is the register_chrdev_region() call which according to
J. Corbet's documentation allows support for more than 256 
devices, going away? Or is it simply going to lose its
sysfs visibility (in the /sys/cdev/major directory)?
 
> For scsi generic you should create a scsi generic class (scsi_generic?)
> and create the individual sg devices in that directory (feel free to use
> the simple_class.c code that is currently in the -mm tree if you want,
> it makes it much simpler)

Does any device use the simple_class.c code yet?
 
> > st also needs changes.

and osst.

Kai changed the st naming scheme in /sys/cdev/major/st*
in a way that seems to allow for more than 8 variants
of each device.
 
> I agree.
> 
> > 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.
> 
> Create multiple class_device items for every tape device and have the
> device symlink point to the same scsi device.  The simple_class code
> should make life a lot easier for you.
> 
> > 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.
> 
> That's a scsi core issue, not a udev issue :)

Well, before cdev gets ripped out, following two symlinks
(i.e. tape -> device -> generic) solves the long standing
ULD to sg (and vice versa) mapping problem.

It shouldn't be too hard putting (another) implementation
of the SG_IO in scsi/scsi_ioctl.c next to the
implementation of the SCSI_IOCTL_SEND_COMMAND ioctl.

Doug Gilbert






-------------------------------------------------------
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-14  1:12 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
2004-01-13 23:18     ` Greg KH
2004-01-14  1:12       ` dougg [this message]
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=1074042776.4004979822819@wwws.torque.net \
    --to=dougg@torque.net \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=patmans@us.ibm.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).