From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Jon Kåre Hellan" <hellan@acm.org>,
linux-ide@vger.kernel.org,
"Carlos Pardo" <Carlos.Pardo@siliconimage.com>
Subject: Re: sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE
Date: Thu, 23 Feb 2006 12:52:33 +0900 [thread overview]
Message-ID: <43FD3181.5010702@gmail.com> (raw)
In-Reply-To: <43FD2D9E.9020709@pobox.com>
Jeff Garzik 쓴 글:
> Tejun Heo wrote:
>> According to the errata information from Silicon Image, SiI3512 does
>> not have m15w bug, neither does ST3200822AS. So, this must be
>> something else and you're not an isolated case. One of my friends
>> reported the same problem but I currently can't test it as he sold his
>> motherboard *really* fast. :-( So, it would be very nice if you can
>> test fixes we'll be able to come up with.
>>
>> Carlos (Hi!), 3512 + some 7200.7 hangs. Can you think of any related
>> errata?
>
>
> I think I'm going to start patching sata_sil.c with a todo list, just to
> keep track of things.
>
> In particular, in ADDITION to errata recently sent by SiI, sata_sil
> could do better with reset, it needs to handle watchdog timer interrupt,
> and it desperately wants the irq-pio branch merged.
>
We also need to delist some drives from m15w list according to SIMG's
blacklist. Is there any reason why sata_sil wants irq-pio desparately
compared to other drivers? Actually it seems that all sata_sil
controllers seem to be capable of performing PIO using DMA which makes
PIO support unncessary.
--
tejun
next prev parent reply other threads:[~2006-02-23 3:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 18:03 sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE Jon Kåre Hellan
2006-02-23 2:07 ` Tejun Heo
2006-02-23 3:35 ` Jeff Garzik
2006-02-23 3:52 ` Tejun Heo [this message]
2006-02-23 3:58 ` Jeff Garzik
2006-02-23 6:59 ` Jon K Hellan
2006-02-23 7:19 ` Tejun Heo
2006-02-24 7:08 ` Jon K Hellan
2006-02-24 7:21 ` Tejun Heo
2006-02-24 7:26 ` Tejun Heo
2006-02-24 8:33 ` Jon Kåre Hellan
2006-02-24 18:07 ` Jon K Hellan
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=43FD3181.5010702@gmail.com \
--to=htejun@gmail.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=hellan@acm.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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.