All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] ath9k: use correct init values for ar9100 devices
Date: Wed, 04 Mar 2009 17:20:04 +0100	[thread overview]
Message-ID: <49AEAA34.8080806@openwrt.org> (raw)
In-Reply-To: <18862.36430.959276.440720@gargle.gargle.HOWL>

Sujith ?rta:
> Gabor Juhos wrote:
>> Apart from the last line, this patch simply swaps the two initval sets as i see
>> it. Would not be simpler to rename them, and then change this line only?
>>
> 
> I didn't bother to check if the initvals were to be swapped or not.

Well, I was curious, so I did it. :)

After some cut&paste job, here is the diff between the original and the new
initvals from your patch:

diff --git a/drivers/net/wireless/ath9k/initvals.h
b/drivers/net/wireless/ath9k/initvals.h
index d492363..d5a8aec 100644
--- a/drivers/net/wireless/ath9k/initvals.h
+++ b/drivers/net/wireless/ath9k/initvals.h
@@ -658,7 +657,7 @@ static const u32 ar5416Addac_9100[][2] = {
     {0x0000989c,  0x00000000 },
     {0x0000989c,  0x00000000 },
     {0x0000989c,  0x00000000 },
-    {0x000098cc,  0x00000000 },
+    {0x000098c4,  0x00000000 },
 };

 static const u32 ar5416Modes[][6] = {
@@ -862,7 +861,7 @@ static const u32 ar5416Common[][2] = {
     { 0x00008134, 0x00000000 },
     { 0x00008138, 0x00000000 },
     { 0x0000813c, 0x00000000 },
-    { 0x00008144, 0x00000000 },
+    { 0x00008144, 0xffffffff },
     { 0x00008168, 0x00000000 },
     { 0x0000816c, 0x00000000 },
     { 0x00008170, 0x32143320 },

> The patch was a line-by-line copy of the latest initvals. :-)
> Figured this would also make it easier to roll out future updates.

Ok. This version will cause more noise, but it is fine for me.

> 
>>> +#define AR_SREV_VERSION_9100		0x014
>> 0x14?
> 
> Yep, this can be fixed.

I have to send a new patch, or you will take care of it?

Regards,
Gabor

WARNING: multiple messages have this Message-ID (diff)
From: Gabor Juhos <juhosg@openwrt.org>
To: Sujith <m.sujith@gmail.com>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [ath9k-devel] [RFC] ath9k: use correct init values for ar9100 devices
Date: Wed, 04 Mar 2009 17:20:04 +0100	[thread overview]
Message-ID: <49AEAA34.8080806@openwrt.org> (raw)
In-Reply-To: <18862.36430.959276.440720@gargle.gargle.HOWL>

Sujith =EDrta:
> Gabor Juhos wrote:
>> Apart from the last line, this patch simply swaps the two initval se=
ts as i see
>> it. Would not be simpler to rename them, and then change this line o=
nly?
>>
>=20
> I didn't bother to check if the initvals were to be swapped or not.

Well, I was curious, so I did it. :)

After some cut&paste job, here is the diff between the original and the=
 new
initvals from your patch:

diff --git a/drivers/net/wireless/ath9k/initvals.h
b/drivers/net/wireless/ath9k/initvals.h
index d492363..d5a8aec 100644
--- a/drivers/net/wireless/ath9k/initvals.h
+++ b/drivers/net/wireless/ath9k/initvals.h
@@ -658,7 +657,7 @@ static const u32 ar5416Addac_9100[][2] =3D {
     {0x0000989c,  0x00000000 },
     {0x0000989c,  0x00000000 },
     {0x0000989c,  0x00000000 },
-    {0x000098cc,  0x00000000 },
+    {0x000098c4,  0x00000000 },
 };

 static const u32 ar5416Modes[][6] =3D {
@@ -862,7 +861,7 @@ static const u32 ar5416Common[][2] =3D {
     { 0x00008134, 0x00000000 },
     { 0x00008138, 0x00000000 },
     { 0x0000813c, 0x00000000 },
-    { 0x00008144, 0x00000000 },
+    { 0x00008144, 0xffffffff },
     { 0x00008168, 0x00000000 },
     { 0x0000816c, 0x00000000 },
     { 0x00008170, 0x32143320 },

> The patch was a line-by-line copy of the latest initvals. :-)
> Figured this would also make it easier to roll out future updates.

Ok. This version will cause more noise, but it is fine for me.

>=20
>>> +#define AR_SREV_VERSION_9100		0x014
>> 0x14?
>=20
> Yep, this can be fixed.

I have to send a new patch, or you will take care of it?

Regards,
Gabor

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-03-04 16:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 18:10 [ath9k-devel] [RFC] ath9k: use correct init values for ar9100 devices Gabor Juhos
2009-03-03 18:10 ` Gabor Juhos
2009-03-04  4:30 ` [ath9k-devel] " Sujith
2009-03-04  4:30   ` Sujith
2009-03-04  5:35   ` [ath9k-devel] " Sujith
2009-03-04  5:35     ` Sujith
2009-03-04 13:38     ` [ath9k-devel] " Gabor Juhos
2009-03-04 14:21       ` Sujith
2009-03-04 14:21         ` Sujith
2009-03-04 16:20         ` Gabor Juhos [this message]
2009-03-04 16:20           ` Gabor Juhos
2009-03-05  1:49           ` Sujith
2009-03-05  1:49             ` Sujith
2009-03-05 10:43             ` Gabor Juhos
2009-03-05 10:43               ` Gabor Juhos
2009-03-05 15:00               ` Sujith
2009-03-05 15:00                 ` Sujith
2009-03-04 13:41   ` Gabor Juhos
2009-03-04 13:41     ` Gabor Juhos
2009-03-04 14:29     ` [ath9k-devel] " Sujith
2009-03-04 14:29       ` Sujith
2009-03-04 14:57       ` Gabor Juhos
2009-03-04 14:57         ` Gabor Juhos
2009-03-05  1:51         ` Sujith
2009-03-05  1:51           ` Sujith
2009-03-05  2:15           ` Luis R. Rodriguez
2009-03-05  2:15             ` Luis R. Rodriguez

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=49AEAA34.8080806@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=ath9k-devel@lists.ath9k.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.