All of lore.kernel.org
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: libata PATA patch update
Date: Wed, 10 May 2006 23:24:02 +0200	[thread overview]
Message-ID: <446259F2.4080308@free.fr> (raw)
In-Reply-To: <4460D7D7.3070807@free.fr>

Hi,
matthieu castet wrote:
> Hi,
> 
> Alan Cox wrote:
> 
>> On Llu, 2006-05-08 at 23:57 +0200, Matthieu CASTET wrote:
>>
> 
>>
>>> PS : any idea in order to allow to work my cdrw drive, that don't return
>>> interrupt when setting xfermode ?
>>
>>
>>
>> The real question is "why is it not returning an interrupt", as it is
>> required to do so unless nIEN masking is active. Handling that is a
>> matter for the libata core itself and depends on what Jeff has planned,
>> but I'm still a bit bothered that it may not be a drive problem but a
>> bug in the via pata driver.
> 
> You seem right : I tried the drive on the sil680 and it works [1].
> The same config (only one slave drive channel 1) fails [2].
> What is strange it that there is the same problem with the old via ide 
> driver and hdparm -X [3].
> Have you any hint what could I try ?
> 

It seems there is really a bug in the timing code.
I attach the lspci diff (from ide to pata) and the viaideinfo one


Matthieu

  00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00
  10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  20: 01 fc 00 00 00 00 00 00 00 00 00 00 06 11 71 05
  30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 01 00 00
  40: 0b f2 09 35 18 1c c0 00 20 20 20 20 ff 00 20 20
-50: e6 e6 e1 e1 0c 00 00 00 a8 a8 a8 a8 00 00 00 00
+50: 27 27 27 27 0c 00 00 00 a8 a8 a8 a8 00 00 00 00
  60: 00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00
  70: 02 01 00 00 00 00 00 00 02 01 00 00 00 00 00 00
-80: 00 40 ed 3f 00 00 00 00 00 00 00 00 00 00 00 00
+80: 00 f0 b9 01 00 00 00 00 00 50 a9 01 00 00 00 00
  90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


@@ -16,7 +16,7 @@
  Post Write Buffer:            yes                 yes
  Enabled:                      yes                 yes
  Simplex only:                  no                  no
-Cable Type:                   80w                 40w
+Cable Type:                   40w                 40w
  -------------------drive0----drive1----drive2----drive3-----
  Transfer Mode:       UDMA      UDMA      UDMA      UDMA
  Address Setup:      120ns     120ns     120ns     120ns
@@ -24,5 +24,5 @@
  Cmd Recovery:        30ns      30ns      30ns      30ns
  Data Active:         90ns      90ns      90ns      90ns
  Data Recovery:       30ns      30ns      30ns      30ns
-Cycle Time:          22ns      22ns      60ns      60ns
-Transfer Rate:   88.8MB/s  88.8MB/s  33.3MB/s  33.3MB/s
+Cycle Time:          67ns      67ns      67ns      67ns
+Transfer Rate:   29.6MB/s  29.6MB/s  29.6MB/s  29.6MB/s

  parent reply	other threads:[~2006-05-10 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:06 libata PATA patch update 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 [this message]
2006-05-08 23:48 ` Rene Herman
2006-05-09 12:30   ` Alan Cox
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=446259F2.4080308@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.