From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Michael Madore <Michael.Madore@aslab.com>,
linux-ide@vger.kernel.org, albertcc@tw.ibm.com
Subject: Re: [PATCH linux-2.6.13-rc3] Mod15Write quirk against v2.6.13
Date: Mon, 22 Aug 2005 06:44:45 +0900 [thread overview]
Message-ID: <4308F5CD.7060001@gmail.com> (raw)
In-Reply-To: <4308EDB5.6060102@pobox.com>
Hello, Jeff.
Jeff Garzik wrote:
> Tejun Heo wrote:
>
>> Jeff Garzik wrote:
>>
>>> Tejun Heo wrote:
>>>
>>>> Also, Jeff, I know you're very busy, but what do you think about
>>>> taking m15w workaround into ata tree? It's been around for a while
>>>> now and I haven't received any complaints (except for this one) yet.
>>>> The workaround is ugly but it surely helps and I'm willing to maintain
>>>> it.
>
>
>>> I think your mod15write solution is too messy to deal with long-term.
>>> Maintenance burden is much lower on us without it. It's not too
>>> difficult to simply avoid certain combinations of hardware.
>
>
>> No problem, I'll maintain it out of tree.
>
>
> You're welcome to maintain it as an independent branch of
> libata-dev.git, if you would prefer.
>
I think I'll just keep it out of tree. I don't think many libata
developers would be interested in m15w workaround.
>
>>> Note! As Carlos @ Silicon Image points out, the blacklist should
>>> only apply to SiI 3112, not 3512/3114/etc. That's an open FIXME that
>>> would benefit users.
>
>
>> Cool, I'll submit a patch right away.
>
Can you please tell me which are affected and which are not?
{ 0x1095, 0x3112, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
{ 0x1095, 0x0240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
{ 0x1095, 0x3512, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
{ 0x1095, 0x3114, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3114 },
{ 0x1002, 0x436e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
{ 0x1002, 0x4379, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
{ 0x1002, 0x437a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 },
Thanks.
--
tejun
next prev parent reply other threads:[~2005-08-21 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1121894035.4885.15.camel@drevil.aslab.com>
2005-07-28 14:12 ` [PATCH linux-2.6.13-rc3] Mod15Write quirk against v2.6.13 Tejun Heo
2005-08-21 19:19 ` Jeff Garzik
2005-08-21 20:45 ` Tejun Heo
2005-08-21 21:10 ` Jeff Garzik
2005-08-21 21:44 ` Tejun Heo [this message]
2005-08-22 10:19 ` Bartlomiej Zolnierkiewicz
2005-08-22 11:46 ` [PATCH libata:upstream] sil: apply M15W quirk selectively Tejun Heo
2005-08-22 19:36 ` Jeff Garzik
2005-08-22 21:39 ` Tejun Heo
2005-08-22 21:45 ` Jeff Garzik
2005-08-22 22:27 ` [PATCH libata:upstream] sil: apply M15W quirk selectively (take 2) Tejun Heo
2005-08-23 5:06 ` Jeff Garzik
2005-08-21 19:34 ` [PATCH linux-2.6.13-rc3] Mod15Write quirk against v2.6.13 Jeff Garzik
2005-08-21 19:56 ` Tejun Heo
2005-08-21 20:11 ` Jeff Garzik
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=4308F5CD.7060001@gmail.com \
--to=htejun@gmail.com \
--cc=Michael.Madore@aslab.com \
--cc=albertcc@tw.ibm.com \
--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.