linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@osdl.org, alan@lxorguk.ukuu.org.uk,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	B.Zolnierkiewicz@elka.pw.edu.pl, htejun@gmail.com,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: + via-pata-controller-xfer-fixes.patch added to -mm tree
Date: Sun, 25 Jun 2006 11:15:49 +0200	[thread overview]
Message-ID: <449E5445.60008@free.fr> (raw)
In-Reply-To: <449DBFFD.2010700@garzik.org>

Jeff Garzik wrote:
> Data point #3 (or #0...):
> 
> This appears to be a _device_ that sends its interrupt early.
> 
> If that is the case, the device may appear on any controller, not just 
> VIA, and we would have to handle it globally via a device special-case 
> in libata-core.
> 

For the record, the cdrom writer that need this quirk on pata via, works 
on pata sil680.
But 3 microsecond is very short, and the problem could be hidden by the 
controller, or other stuffs.



  reply	other threads:[~2006-06-25  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200606242214.k5OMEHCU005963@shell0.pdx.osdl.net>
2006-06-24 22:36 ` + via-pata-controller-xfer-fixes.patch added to -mm tree Jeff Garzik
2006-06-24 22:43   ` Jeff Garzik
2006-06-25  9:15     ` matthieu castet [this message]
2006-06-30  7:09       ` Albert Lee
2006-06-30  7:55         ` castet.matthieu
2006-06-30  8:26           ` Albert Lee
2006-07-02  8:36             ` matthieu castet
2006-07-02 10:32               ` matthieu castet
2006-07-02 12:46                 ` Albert Lee
2006-07-02 13:06                   ` matthieu castet
2006-07-02 14:17                     ` Albert Lee
2006-06-30 10:03         ` Alan Cox
2006-07-02 13:59           ` Albert Lee
2006-06-24 23:17   ` Alan Cox

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=449E5445.60008@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --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).