public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: vojtech@suse.cz, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS2 mouse going nuts during cdparanoia session.
Date: Wed, 16 Jul 2003 18:20:20 +0100	[thread overview]
Message-ID: <20030716172020.GC21896@suse.de> (raw)
In-Reply-To: <20030716171323.GL833@suse.de>

On Wed, Jul 16, 2003 at 07:13:23PM +0200, Jens Axboe wrote:

 > > Ah right, I thought cdparanoia was still ripper de jour..
 > > What's recommended these days?
 > 
 > It is, unfortunately it uses read/write on /dev/sg* directly so cannot
 > be used with "new path" that is so much faster. It's been a while since
 > I looked, I can check for a good cdda ripper that uses SG_IO tomorrow if
 > you don't find one first.

Ok. I'll add a note about this to post-halloween-2.5 sometime too
when www.codemonkey.org.uk reappears again.
[sidenote: please folks, no more mails telling me about this site going away,
 it'll be back real soon, it just had to be 'upgraded' to a raq2, which didn't
 go quite as smoothly as planned.].

 > I'm about to cave in and add block emulation of that part, too. It's a
 > bit more code, though.

If it'll make apps like cdparanoia take the fast path without needing
rewriting, then that sounds like a good idea, if only to stop the
'dancing mouse' problem, though this does seem to be running away
from a bug rather than fixing it. The real question is why are the
two interacting with each other like this..

		Dave


  reply	other threads:[~2003-07-16 17:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 16:57 PS2 mouse going nuts during cdparanoia session Dave Jones
2003-07-16 17:03 ` Jens Axboe
2003-07-16 17:09   ` Dave Jones
2003-07-16 17:13     ` Jens Axboe
2003-07-16 17:20       ` Dave Jones [this message]
2003-07-16 17:24         ` Jens Axboe
2003-07-16 17:21     ` Markus Plail
2003-07-16 17:10   ` Alan Cox
2003-07-16 17:16     ` Jens Axboe
2003-07-16 17:23       ` Dave Jones
2003-07-16 17:25         ` Jens Axboe
2003-07-16 17:28           ` Dave Jones
2003-07-16 17:31             ` Jens Axboe
2003-07-16 18:22               ` Alan Cox
2003-07-16 19:03               ` Kristofer T. Karas
2003-07-16 19:13                 ` Valdis.Kletnieks
2003-07-16 19:00         ` Vojtech Pavlik
2003-07-16 19:30           ` Dave Jones
2003-07-16 20:53             ` Vojtech Pavlik
2003-07-16 23:31               ` Dave Jones
2003-07-16 23:47                 ` Vojtech Pavlik
2003-07-17 11:15                   ` Alan Cox
2003-07-17 17:08                     ` Dave Jones
2003-07-16 18:00     ` Andrew Morton
2003-07-16 18:56     ` Vojtech Pavlik
2003-07-16 21:05     ` Andries Brouwer
2003-07-16 17:10   ` Valdis.Kletnieks
2003-07-16 17:17     ` Jens Axboe
2003-07-16 17:55       ` Dave Jones
2003-07-16 17:57         ` Jens Axboe
     [not found]         ` <1058422511.1164.1440.camel@workshop.saharacpt.lan>
2003-07-17 12:39           ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2003-07-16 23:43 Mikael Pettersson
2003-07-17  2:03 ` Jacek Kawa
2003-07-17 21:44   ` Jacek Kawa

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=20030716172020.GC21896@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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