From: Jens Axboe <axboe@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6 ide-cd DMA ripping
Date: Wed, 3 Mar 2004 12:45:31 +0100 [thread overview]
Message-ID: <20040303114531.GR9196@suse.de> (raw)
In-Reply-To: <20040303113756.GQ9196@suse.de>
On Wed, Mar 03 2004, Jens Axboe wrote:
> +static int cdrom_read_cdda(struct cdrom_device_info *cdi, __u8 __user *ubuf,
> + int lba, int nframes)
> +{
> + int ret;
> +
> + if (cdi->cdda_method == CDDA_OLD)
> + return cdrom_read_cdda_old(cdi, ubuf, lba, nframes);
> +
> + do {
> + ret = cdrom_read_cdda_bpc(cdi, ubuf, lba, nframes);
> +
> + if (!ret)
> + break;
> +
> + /*
> + * I've seen drives get sense 4/8/3 udma crc errors, so
> + * drop to single frame dma if we need to
> + */
> + if (cdi->cdda_method == CDDA_BPC_FULL && nframes > 1) {
> + printk("cdrom: dropping to single frame dma\n");
> + cdi->cdda_method = CDDA_BPC_SINGLE;
> + continue;
> + }
> +
> + printk("cdrom: dropping to old style cdda\n");
> + cdi->cdda_method = CDDA_OLD;
> + ret = cdrom_read_cdda_old(cdi, ubuf, lba, nframes);
> + } while (0);
Irk, that should have been a while (1) of course, and a break after the
last cdrom_read_cdda_old();
--
Jens Axboe
next prev parent reply other threads:[~2004-03-03 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 11:37 [PATCH] 2.6 ide-cd DMA ripping Jens Axboe
2004-03-03 11:45 ` Jens Axboe [this message]
2004-03-03 12:26 ` Alistair John Strachan
2004-03-03 12:25 ` Jens Axboe
2004-03-06 14:04 ` Sean Neakums
2004-03-07 10:35 ` Jens Axboe
2004-03-07 12:04 ` Sean Neakums
2004-03-08 9:41 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 11:07 Vince
2004-03-04 15:28 ` [PATCH] " Jens Axboe
2004-03-05 12:08 ` Colin Leroy
2004-03-05 12:21 ` Jens Axboe
2004-03-05 13:15 ` Colin Leroy
2004-03-05 13:22 ` Jens Axboe
2004-03-05 18:58 Voluspa
2004-03-07 10:34 ` Jens Axboe
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=20040303114531.GR9196@suse.de \
--to=axboe@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox