From: Marek Vasut <marek.vasut@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: [PATCH] Marvell CF8381 and CF8305
Date: Mon, 23 Mar 2009 18:09:42 +0100 [thread overview]
Message-ID: <200903231809.42587.marek.vasut@gmail.com> (raw)
In-Reply-To: <200903231706.16489.hs4233@mail.mn-solutions.de>
On Monday 23 of March 2009 17:06:16 Holger Schurig wrote:
> > +#define CF8305_MANFID 0x02db
> > +#define CF8305_CARDID 0x8103
>
> It's 8385, not 8305.
it's 8305 ... that's even older card ;)
>
> > /* Check if we have a current silicon */
> > - if (if_cs_read8(card, IF_CS_PRODUCT_ID) <
> > IF_CS_CF8385_B1_REV) { - lbs_pr_err("old chips like 8385 rev
> > B1 aren't supported\n"); + prod_id = if_cs_read8(card,
> > IF_CS_PRODUCT_ID);
> > + if (!(if_cs_hw_is_cf8305(p_dev) ||
> > + (if_cs_hw_is_cf8381(p_dev) &&
> > + prod_id >= IF_CS_CF8381_B3_REV)) &&
> > + (prod_id < IF_CS_CF8385_B1_REV)) {
> > + lbs_pr_err("old chips like 8385 rev B1 or "
> > + "8381 rev B3 aren't supported\n");
>
> I still find this if hard to read. Why not something like this:
>
> if ((if_cs_is_8385() && prod_id < IF_CS_CF8385_B1_REV) ||
> (if_cs_Is_8381() && prod_id < IF_CS_CF8381_B3_REV)) {
> ....
> }
>
> > static struct pcmcia_device_id if_cs_ids[] = {
> > + PCMCIA_DEVICE_MANF_CARD(CF8305_MANFID, CF8305_CARDID),
> > + PCMCIA_DEVICE_MANF_CARD(CF8381_MANFID, CF8381_CARDID),
> > PCMCIA_DEVICE_MANF_CARD(0x02df, 0x8103),
> > PCMCIA_DEVICE_NULL,
> > };
>
> Now we end with two entries of 0x02df, 0x8103 :-/
next prev parent reply other threads:[~2009-03-23 17:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 0:27 [PATCH] Marvell CF8381 Marek Vasut
2009-03-22 4:11 ` Marek Vasut
2009-03-22 8:04 ` Johannes Berg
2009-03-22 13:01 ` Marek Vasut
2009-03-22 13:03 ` Johannes Berg
2009-03-23 12:27 ` Holger Schurig
2009-03-23 16:15 ` Dan Williams
2009-03-23 21:58 ` Marek Vasut
2009-03-23 23:08 ` Dan Williams
2009-03-23 23:42 ` Marek Vasut
2009-03-24 10:26 ` Dan Williams
2009-03-24 20:01 ` John W. Linville
2009-03-24 20:33 ` Marek Vasut
2009-03-23 12:13 ` Holger Schurig
2009-03-23 14:34 ` Marek Vasut
2009-03-23 15:57 ` [PATCH1/2] Fix return value handling Marek Vasut
2009-03-23 15:59 ` Marek Vasut
2009-03-23 16:11 ` Dan Williams
2009-03-23 15:59 ` [PATCH] Marvell CF8381 and CF8305 Marek Vasut
2009-03-23 16:00 ` Marek Vasut
2009-03-23 16:06 ` Holger Schurig
2009-03-23 17:09 ` Marek Vasut [this message]
2009-03-23 17:19 ` Dan Williams
2009-03-23 17:39 ` Marek Vasut
2009-03-23 16:58 ` Dan Williams
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=200903231809.42587.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@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.