Francois Romieu wrote:
Tejun Heo [EMAIL PROTECTED] :
[...]
Apparently, I'm more confused than you are. My master was at 872aad45
but my index was at rc7. Can you please force checkout the head and
re-test? I've tested both native and legacy modes and it's fixed here.
I have done a
Jeff Garzik wrote:
Alan Cox wrote:
but IDE simply ignores the error and continues to operate in MWDMA
mode, so I guess we can remove the 'temporary fix' comment or add
another quirk type - ATA_HORKAGE_SETXFER_MAY_FAIL - and use it.
Should we warn in these cases ? Or issue a new identify and
Tejun Heo wrote:
I like the whole series. Just a few nits.
* 9 and 10 need to be oen patch. As it currently stands, compile will
fail after 9.
* Please don't include Patch n/10 in message body.
* Add freeze/thaw to all, merge, kill freeze/thaw from all sequence is a
bit odd. It
On 5 Jul 2007, at 23:27, Rod Whitby wrote:
Alan Cox wrote:
Chipsets
ARTOP
No reports, but nobody appears to be using one
The NSLU2-Linux project (http://www.nslu2-linux.org) relies on the
pata-artop driver for the arm/ixp4xx-based Iomega NAS100d and D-Link
DSM-G600 NAS
From: Dan Williams [EMAIL PROTECTED]
Separate sata_vsc interrupt handling into a normal (per-port) path and an
error path with the addition of vsc_port_intr and vsc_error_intr
respectively. The error path handles interrupt based
hotplug events which requires the definition of vsc_freeze and
I put in this patch and I get:
00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
[ 1416.680306] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x20 (host bus error)
[ 1416.723962] ATA: abnormal status 0xD0 on port 0xE100821C
[ 1416.746129] ATA: abnormal status 0xD0 on port 0xE100821C
[
Hello,
I found out that pata_ali is not working with a 64 bit kernel, while a
32 bit kernel on the same machine works fine. I'm running a very recent
kernel (872aad45, somewhere after 2.6.22-rc7).
The problem is that as soon as the module is loaded I get a screaming
interrupt:
(initramfs)
On 07/06/2007 03:09 PM, Jeff Garzik wrote:
{Maxtor 6B200M0, BANC1BM0, ATA_HORKAGE_NONCQ }
Or should *all* Maxtor 6B200M0 be blacklisted, since there's already
one of them in the list?
Wanna send that as a patch, with attribution and sign-offs? :)
For all revisions, or just
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 05, 2007 1:30 PM
To: Thorsten Leemhuis
Cc: Thorsten Leemhuis; Chuck Ebbert; Jeff Garzik; IDE/ATA
development list; Gaston, Jason D; Alan Cox;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re:
