All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: John Willis <John.Willis@Distant-earth.com>
Cc: "linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	"linville\@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [PATCH] wl1251: add support for PG11 chips.
Date: Fri, 16 Oct 2009 10:19:59 +0300	[thread overview]
Message-ID: <87vdifbyao.fsf@nokia.com> (raw)
In-Reply-To: <01c201ca4d9c$c2c44500$484ccf00$@Willis@Distant-earth.com> (ext John Willis's message of "Thu, 15 Oct 2009 15:38:16 +0200")

John Willis <John.Willis@Distant-earth.com> writes:

> From: David-John Willis <John.Willis@Distant-earth.com>
>
> This simple patch adds support for the PG11 variant of the WL1251 chip as
> used on the OpenPandora OMAP3 device.
>
> Signed-off-by: David-John Willis <John.Willis@Distant-earth.com>

Thanks for the patch. And excellent news that it's working on your
device.

Minor comment:

> --- a/drivers/net/wireless/wl12xx/wl1251_main.c
> +++ b/drivers/net/wireless/wl12xx/wl1251_main.c
> @@ -185,6 +185,9 @@ static int wl1251_chip_wakeup(struct wl1251 *wl)
>  		break;
>  	case CHIP_ID_1251_PG10:
>  	case CHIP_ID_1251_PG11:
> +		wl1251_debug(DEBUG_BOOT, "chip id 0x%x (1251 PG11)",
> +			     wl->chip_id);
> +		break;
>  	default:
>  		wl1251_error("unsupported chip id: 0x%x", wl->chip_id);
>  		ret = -ENODEV;

This patch also enables PG10 support, but as that hardware revision is
untested I think it's better not to enable it. I'll edit the patch a bit
regarding this and then send it to John.

-- 
Kalle Valo

       reply	other threads:[~2009-10-16  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01c201ca4d9c$c2c44500$484ccf00$@Willis@Distant-earth.com>
2009-10-16  7:19 ` Kalle Valo [this message]
2009-10-16  8:37   ` [PATCH] wl1251: add support for PG11 chips Kalle Valo
2009-10-16 14:05     ` John W. Linville

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=87vdifbyao.fsf@nokia.com \
    --to=kalle.valo@iki.fi \
    --cc=John.Willis@Distant-earth.com \
    --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 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.