linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Michael Madore <Michael.Madore@aslab.com>,
	linux-ide@vger.kernel.org, albertcc@tw.ibm.com
Subject: Re: [PATCH libata:upstream] sil: apply M15W quirk selectively
Date: Mon, 22 Aug 2005 15:36:57 -0400	[thread overview]
Message-ID: <430A2959.300@pobox.com> (raw)
In-Reply-To: <20050822114639.GA26607@htj.dyndns.org>

Tejun Heo wrote:
>  Hello, Jeff & Bartlomiej & all.
> 
> 
>>What about fixing 3114 for a start? :-)
> 
> 
>  Yeap, why not?  Here it is.
> --
> 
>  This patch adds chipset mask to sil_blacklist such that quirks can be
> applied selectively depending on chipset.  And add sil_3112_m15w
> chipset which is identical to sil_3112 except that mod15write quirk is
> applied.  As we don't know which PCI IDs are affected yet, I've
> changed all 3112's to sil_3112_m15w.  Later when we know which PCI IDs
> are affected, we can just change them to sil_3112 later.
> 
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>

Thanks for tackling this.  I would approach it in a different manner:

1) add to the enum at the top,
+	SIL_FLAG_M15W		= (1 << 30),

2) do
         sil_3112                = 0,
-       sil_3114                = 1,
+	sil_3112_m15w		= 1,
+	sil_3114		= 2,


3) in sil_pci_tbl[], change all the sil_3112 entries to sil_3112_m15w, 
EXCEPT for PCI ID 0x1095, 0x3512, which should remain sil_3112.



4) in sil_port_info[], duplicate sil_3112 entry to new entry 
sil_3112_m15w.  make sure order in sil_port_info[] array matches the 
values in step #2.


5) add SIL_FLAG_M15W to the list of host_flags in the new sil_3112_m15w 
entry created in step #4.


6) in sil_dev_config(), change
        if (quirks & SIL_QUIRK_MOD15WRITE) {
test to also test (ap->flags & SIL_FLAG_M15W)


Check over these steps to see if I missing anything...  at the very 
least, I have illustrated the approach that should be taken.

	Jeff



  reply	other threads:[~2005-08-22 19:37 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
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 [this message]
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=430A2959.300@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Michael.Madore@aslab.com \
    --cc=albertcc@tw.ibm.com \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.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 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).