public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Chris Wedgwood <cw@f00f.org>, LKML <linux-kernel@vger.kernel.org>,
	Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: MMC ioctl or sysfs interface?
Date: Sun, 12 Jun 2005 19:25:22 +0100	[thread overview]
Message-ID: <1118600720.9949.99.camel@localhost.localdomain> (raw)
In-Reply-To: <42AC7BD4.9040906@drzeus.cx>

On Sul, 2005-06-12 at 19:15, Pierre Ossman wrote:
> Alan Cox wrote:
> I wasn't aware that you could do ioctl on sysfs nodes. I guess I'll have
> to dig a bit deeper in the documentation/code.

You can add support, but you'll need a device node one day anyway so you
might as well give up on the sysfs only game - it doesn't IMHO work.

> As for keeping the same ioctl. If the current ioctls are similar enough
> then I don't see why not. The userspace tools might need changing though
> since all ATA ioctls won't be available. What tool is used for locking
> an ATA drive? And is there some documentation detailing the lock
> commands and related ioctls so I can compare with what I'm trying to do?

Right now for ATA you issue a taskfile ioctl, for SCSI you use SG_IO and
applications are not presented with any uniformity.


  reply	other threads:[~2005-06-12 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 13:08 MMC ioctl or sysfs interface? Pierre Ossman
2005-06-10  0:58 ` Chris Wedgwood
2005-06-10 21:00   ` Pierre Ossman
2005-06-10 23:00     ` Alan Cox
2005-06-12 18:15       ` Pierre Ossman
2005-06-12 18:25         ` Alan Cox [this message]
2005-06-12 20:30           ` Jon Smirl

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=1118600720.9949.99.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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