All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: albertl@mail.com
Cc: matthieu castet <castet.matthieu@free.fr>,
	Jeff Garzik <jeff@garzik.org>,
	akpm@osdl.org,
	"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>,
	Unicorn Chang <uchang@tw.ibm.com>, Doug Maxey <dwm@maxeymade.com>
Subject: Re: + via-pata-controller-xfer-fixes.patch added to -mm tree
Date: Fri, 30 Jun 2006 11:03:23 +0100	[thread overview]
Message-ID: <1151661803.31392.1.camel@localhost.localdomain> (raw)
In-Reply-To: <44A4CE21.30009@tw.ibm.com>

Ar Gwe, 2006-06-30 am 15:09 +0800, ysgrifennodd Albert Lee:
> If it is the problem of the specific ATAPI device, all controllers
> should be affected, not only VIA. So, strange not seeing the problem on
> Promise.

That may be because of the way the chips handle buffering of interrupt
delivery and readahead/writebehind. I have two traces on the ALi
chipsets that look like the delayed response problem.



  parent reply	other threads:[~2006-06-30  9:48 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
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 [this message]
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=1151661803.31392.1.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=albertl@mail.com \
    --cc=castet.matthieu@free.fr \
    --cc=dwm@maxeymade.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uchang@tw.ibm.com \
    /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.