All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Gregor Jasny <gjasny@wh8.tu-dresden.de>
Cc: Erik Andersen <andersen@codepoet.org>,
	"Calin A. Culianu" <calin@ajvar.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Asynchronous CDROM Events in Userland
Date: Mon, 4 Feb 2002 10:39:56 +0100	[thread overview]
Message-ID: <20020204103956.T29553@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0202032333200.1158-100000@rtlab.med.cornell.edu> <20020204070414.GA19268@codepoet.org> <20020204085712.O29553@suse.de> <200202040933.g149Xidx006940@backfire.WH8.TU-Dresden.De>
In-Reply-To: <200202040933.g149Xidx006940@backfire.WH8.TU-Dresden.De>

On Mon, Feb 04 2002, Gregor Jasny wrote:
> Am Montag, 4. Februar 2002 08:57 schrieb Jens Axboe:
> > Yep, _no_ drives to date support queued event notification. However, a
> > polled approach is really not too bad -- it simply means that we'll push
> > it to user space instead. I've written a small utility for reference.
> 
> You're wrong.

Not likely

> PLEXTOR CD-R PX-W2410A
> media removal
> eject request
> media removal
> media removal
> 
> HITACHI DVD-ROM GD-2500
> no media change
> new media
> media removal

I'm wrong about what? If you mean that my test app works, then yes of
course it works. It's a synchronous command poll for media status. I
said that _queued event notification_ isn't implemented in any drives.

Did you read the code?

-- 
Jens Axboe


  reply	other threads:[~2002-02-04  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04  4:41 Asynchronous CDROM Events in Userland Calin A. Culianu
2002-02-04  5:07 ` H. Peter Anvin
2002-02-04  5:19   ` Calin A. Culianu
2002-02-04 12:43   ` john slee
2002-02-04 15:23     ` Calin A. Culianu
2002-02-04 16:20     ` H. Peter Anvin
2002-02-04  7:04 ` Erik Andersen
2002-02-04  7:57   ` Jens Axboe
2002-02-04  9:33     ` Gregor Jasny
2002-02-04  9:39       ` Jens Axboe [this message]
2002-02-04 14:05     ` hugang
2002-02-05  7:43       ` Jens Axboe
2002-02-04 12:16   ` Alan Cox
2002-02-04 20:51     ` oops booting 2.4.18-pre7-ac3 Todd M. Roy
2002-02-05  4:04 ` Asynchronous CDROM Events in Userland Stevie O
2002-02-05  4:28   ` H. Peter Anvin
2002-02-05  4:44     ` Calin A. Culianu
2002-02-05  4:47       ` H. Peter Anvin
     [not found] ` <a3l4uc@cesium.transmeta.com>
2002-02-06 14:22   ` Pavel Machek
2002-02-06 22:48     ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2002-02-05 13:17 David Balazic

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=20020204103956.T29553@suse.de \
    --to=axboe@suse.de \
    --cc=andersen@codepoet.org \
    --cc=calin@ajvar.org \
    --cc=gjasny@wh8.tu-dresden.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.