public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Alan Cox <alan@redhat.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Douglas Gilbert <dougg@torque.net>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: sg driver and Fedora Core 2
Date: Sat, 29 May 2004 18:45:12 +0100	[thread overview]
Message-ID: <20040529174512.GU5850@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040529164239.GA8855@devserv.devel.redhat.com>

On Sat, May 29, 2004 at 12:42:39PM -0400, Alan Cox wrote:
> (If you want to argue about 2.7.x then its somewhat different - if scsi
>  devices appear in sysfs and the sysfs nodes also support SG_IO then the
>  entire notion of /dev/sg could go away in 2.7)

That would involve supporting ioctls in sysfs, which is something that's
been opposed so far.  I do agree that you want to flash disc firmware
using a hierarchical path rather than a flat namespace that you have
to double-check to be sure you're not flashing your scanner with disc
firmware.

Possibly we could have /sys/bus/scsi/devices/1\:0\:1\:0/raw_io that
internally uses the SG_IO codepath.  We'd need to rewrite the raw file
interface to support the large IOs necessary, but that's certainly doable.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-05-29 17:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 14:05 sg driver and Fedora Core 2 Douglas Gilbert
2004-05-28 14:18 ` Jens Axboe
2004-05-28 14:28   ` Jens Axboe
2004-05-28 17:25 ` Alan Cox
2004-05-29 15:55   ` James Bottomley
2004-05-29 15:57     ` Alan Cox
2004-05-29 16:07       ` James Bottomley
2004-05-29 16:29         ` Alan Cox
2004-05-29 16:36           ` Arjan van de Ven
2004-05-29 16:42             ` Alan Cox
2004-05-29 17:45               ` Matthew Wilcox [this message]
2004-05-29 16:49           ` James Bottomley
2004-05-29 16:56             ` Alan Cox
2004-05-29 17:28               ` James Bottomley
2004-05-29 17:38                 ` Alan Cox
2004-05-29 17:27             ` Jeff Garzik
2004-05-29 17:29               ` Jens Axboe
2004-05-30 10:37                 ` Douglas Gilbert
2004-05-30 10:41                   ` Alan Cox
2004-06-07  8:56                     ` Douglas Gilbert
2004-05-29 17:35               ` Alan Cox
2004-05-29 17:42                 ` Jeff Garzik
2004-05-29 17:38               ` James Bottomley
2004-05-29 17:46                 ` Alan Cox
2004-05-29 17:58                 ` Jeff Garzik
2004-05-30 10:20                   ` Jens Axboe
2004-05-29 16:24       ` Arjan van de Ven
2004-05-28 17:39 ` Arjan van de Ven

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=20040529174512.GU5850@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alan@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=dougg@torque.net \
    --cc=linux-scsi@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