linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Marinceu <elixxir@ucc.asn.au>
To: linux-kernel@vger.kernel.org
Subject: Re: cdrecord hangs my computer
Date: Mon, 15 Dec 2003 21:29:27 +0800	[thread overview]
Message-ID: <1071494967.2503.82.camel@localhost> (raw)

Just thought I'd add some positive feedback to this thread, if a bit
late (and not really related to cdrecord).

I updated my laptop to -test11 a couple of hours ago and burnt my first
cd using ide-cd. Not having made (nor planning to make) any benchmarks,
the following is to be taken with a grain of salt:

I used a recent xcdroast with a Matshita (Panasonic) ATAPI CD-RW/DVD-ROM
combo drive (model UJDA740) and was impressed. It Just Worked (TM) and
performance was excellent (at 16x), barely using any cpu at all.

Although ide-scsi has been faithful to me, I'm glad that the legacy
emulated scsi code has finally been replaced in favour of native
ide/atapi. I don't really care whether it's dev=0,0,0 or dev=/dev/cdrom,
though from a HCI point of view, the latter is better, but I definitely
want to thank those responsible. I'm sure that a lot of effort has gone
into making this possible.

My laptop _doesn't have_ any scsi hardware, so why should I then have to
select the scsi tree in my kernel config?? Happily, no more.


-- 
 Paul Marinceu
 http://elixxir.ucc.asn.au



             reply	other threads:[~2003-12-15 13:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 13:29 Paul Marinceu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08  9:31 cdrecord hangs my computer Douglas Gilbert
2003-12-11 12:56 ` Jens Axboe
2003-12-11 16:15   ` Linus Torvalds
2003-12-06 19:08 Tero Knuutila
2003-12-06 18:27 Tero Knuutila
2003-12-06 12:39 Tero Knuutila
2003-12-06  8:01 Tero Knuutila
2003-12-06  8:12 ` Linus Torvalds
2003-12-06  8:54   ` Ethan Weinstein
2003-12-06 11:59     ` Måns Rullgård
2003-12-06 13:40     ` Wakko Warner
2003-12-06 14:37       ` John Bradford
2003-12-06 21:57       ` Linus Torvalds
2003-12-06 22:02         ` Larry McVoy
2003-12-06 22:32           ` Linus Torvalds
2003-12-07 11:01             ` Eduard Bloch
2003-12-07 16:18               ` Linus Torvalds
2003-12-08 16:21                 ` bill davidsen
2003-12-08 17:46                   ` Linus Torvalds
2003-12-09 12:38                     ` Bill Davidsen
2003-12-08 17:53                   ` Valdis.Kletnieks
2003-12-08 18:53                     ` Linus Torvalds
2003-12-08 19:40                       ` Valdis.Kletnieks
2003-12-09 14:50                         ` Ian Soboroff
2003-12-09 20:42                           ` Mikael Pettersson
2003-12-08 16:24                 ` Martin J. Bligh
2003-12-08  4:36           ` Bob
2003-12-08  4:51             ` Larry McVoy
2003-12-07  0:16         ` Wakko Warner
2003-12-07  3:31           ` William Lee Irwin III
2003-12-07  4:49           ` Linus Torvalds
2003-12-08 16:13         ` bill davidsen
2003-12-08 17:38           ` Linus Torvalds
2003-12-06 16:42     ` Linus Torvalds

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=1071494967.2503.82.camel@localhost \
    --to=elixxir@ucc.asn.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).