mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata PATA patch update
Date: Tue, 09 May 2006 13:30:57 +0100	[thread overview]
Message-ID: <1147177857.3172.70.camel@localhost.localdomain> (raw)
In-Reply-To: <445FD8D4.9030106@keyaccess.nl>

On Maw, 2006-05-09 at 01:48 +0200, Rene Herman wrote:
> The "couldn't disable kernel command translation layer" bit is probably
> expected?

I think so yes.

> In any case, it seems that this driver is also not using DMA for CDDA? I 

It should use whatever the sr.c SCSI CD driver code uses when doing
CDDA, and it isn't directly a part of the driver (although there are
hooks so drivers can filter/control what ATAPI can be done with DMA).

> am using slackware 10.2 (vanilla) "cdparanoia III release 9.8 (March 23, 
> 2001)". A while ago someone on this list pointed to some patches for 
> SG_IO use with cdparanoia but this made my machine highly unstable. 
> Would you like me to retest with this new driver? If so, any specific 
> version of cdparanoia?

I would be interested to know what happens if you try this, version
doesn't matter.

> DVD is fine. UDMA33 though, although the drive is capable of UDMA66:

The core code sets both drives to the same speed on the cable. The old
-ac code fixed this but I've not pushed that change over (in part
because it will naturally happen now as other changes go in).

Thus dev1 is pulling dev0 down to UDMA33 for now.

> The old IDE driver does set it to UDMA66 after an ide1=ata66, and after
> the recently merged patch to amd74xx to "only do disk side cable
> detection". I assumed it was that same problem, but I see that

That change is in the libata driver as well so should not be a problem.

> Hope this was a useful report...

Much appreciated,

Alan


  reply	other threads:[~2006-05-09 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:06 Alan Cox
2006-05-08 16:54 ` Meelis Roos
2006-05-08 17:29 ` Kevin Radloff
2006-05-09 12:24   ` Alan Cox
2006-05-09 16:52     ` Kevin Radloff
2006-05-08 21:57 ` Matthieu CASTET
     [not found]   ` <1147178241.3172.74.camel@localhost.localdomain>
     [not found]     ` <4460D7D7.3070807@free.fr>
2006-05-10 21:24       ` matthieu castet
2006-05-08 23:48 ` Rene Herman
2006-05-09 12:30   ` Alan Cox [this message]
2006-05-09 20:05     ` Rene Herman
2006-05-23 23:26   ` Rene Herman
2006-05-24  0:11     ` Rene Herman

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=1147177857.3172.70.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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

Powered by JetHome