From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 3/4] libertas: check for old, unsupported hardware
Date: Thu, 05 Jun 2008 07:46:59 -0400 [thread overview]
Message-ID: <1212666420.25730.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200806051308.35863.hs4233@mail.mn-solutions.de>
On Thu, 2008-06-05 at 13:08 +0200, Holger Schurig wrote:
> Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
Looks OK to me; how old are the B1 and earlier chips? Do we just not
have any samples to work with?
Acked-by: Dan Williams <dcbw@redhat.com>
> --- linux.orig/drivers/net/wireless/libertas/if_cs.c
> +++ linux/drivers/net/wireless/libertas/if_cs.c
> @@ -268,6 +268,12 @@
> #define IF_CS_SCRATCH_BOOT_OK 0x00
> #define IF_CS_SCRATCH_HELPER_OK 0x5a
>
> +/*
> + * Used to detect ancient chips:
> + */
> +#define IF_CS_PRODUCT_ID 0x0000001C
> +#define IF_CS_CF8385_B1_REV 0x12
> +
>
> /********************************************************************/
> /* I/O and interrupt handling */
> @@ -864,6 +871,12 @@
> p_dev->irq.AssignedIRQ, p_dev->io.BasePort1,
> p_dev->io.BasePort1 + p_dev->io.NumPorts1 - 1);
>
> + /* 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");
> + ret = -ENODEV;
> + goto out2;
> + }
>
> /* Load the firmware early, before calling into libertas.ko */
> ret = if_cs_prog_helper(card);
next prev parent reply other threads:[~2008-06-05 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:08 [PATCH 3/4] libertas: check for old, unsupported hardware Holger Schurig
2008-06-05 11:46 ` Dan Williams [this message]
2008-06-05 12:02 ` Holger Schurig
2008-08-19 19:44 ` 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=1212666420.25730.4.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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