All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Samphan Raruenrom <samphan@nectec.or.th>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, Linux TLE Team <rdi1@opentle.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [Rdi1] Re: [PATCH] Add MOUNT_STATUS ioctl to cdrom device
Date: Tue, 26 Aug 2003 16:16:14 +0200	[thread overview]
Message-ID: <20030826141614.GE862@suse.de> (raw)
In-Reply-To: <3F4B561A.2000103@nectec.or.th>

On Tue, Aug 26 2003, Samphan Raruenrom wrote:
> Jens Axboe wrote:
> >On Tue, Aug 26 2003, Samphan Raruenrom wrote:
> >>>Exactly. You poll media events from the drive, and upon an eject request
> >>>you try and umount it. If it suceeds, you eject the tray. 
> >>No, it seems impossible to sense the eject request (right?). This
> >No it isn't, in fact there are several ways to do it. Just by searching
> >this list you should be able to find them.
> 
> YES!! 
> http://www.ussg.iu.edu/hypermail/linux/kernel/0202.0/att-0603/01-cd_poll.c
> get_media_event() = 1 -> eject
> Thanks :-)  I think you can't imagine how happy I am now. Thank you again.

I'm surprised you didn't find these things up front.

> >>is what I really did with the patched kernel and patched magicdev.
> >magicdev is a piece of crap.
> 
> Why? I read all its code. Because of 2 sec. polling?

Because it relies on unreliable mechanisms instead of using the proper
support. That makes it 100% crap in my eyes, unusable.

> >I think you need to spend a little more time thinking/researching this
> >problem. At least it really looks like you are going about it all wrong.
> 
> You've just put me on the right track. Thank you very much. I really
> appreciate your and every others insightful comments.

No problem.

-- 
Jens Axboe


  reply	other threads:[~2003-08-26 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 18:22 [PATCH] Add MOUNT_STATUS ioctl to cdrom device Samphan Raruenrom
2003-08-25 18:50 ` Christoph Hellwig
2003-08-26  6:50   ` Samphan Raruenrom
2003-08-26  7:32     ` Christoph Hellwig
2003-08-26  9:09       ` Samphan Raruenrom
2003-08-26  9:56         ` Christoph Hellwig
2003-08-26  9:58           ` Jens Axboe
2003-08-26 11:30             ` [Rdi1] " Samphan Raruenrom
2003-08-26 11:36               ` Jens Axboe
2003-08-26 12:44                 ` Samphan Raruenrom
2003-08-26 14:16                   ` Jens Axboe [this message]
2003-08-26 13:58               ` Christoph Hellwig
2003-08-26 15:32                 ` Samphan Raruenrom
2003-08-26 15:45                   ` Jens Axboe
2003-08-25 20:03 ` viro

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=20030826141614.GE862@suse.de \
    --to=axboe@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rdi1@opentle.org \
    --cc=samphan@nectec.or.th \
    /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.