From: Christian Lamparter <chunkeey@googlemail.com>
To: David Cozatt <olbrannon@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: SMC 2802W -status unsupported
Date: Mon, 2 Aug 2010 10:46:32 +0200 [thread overview]
Message-ID: <201008021046.32453.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTi=XOECFnOgB5mmaDejVhH2aAEedYqz9tyeSz7Ge@mail.gmail.com>
On Sunday 01 August 2010 18:17:16 David Cozatt wrote:
> Accessing http://wireless.kernel.org/en/users/Drivers/p54 shows in unsupported
>
> * early PrismGT cards (e.g.: Netgear WG511v1, SMC 2802W)
>
> phy0: hwaddr 00:04:e2:63:c2:67, MAC:isl3890 RF:Duette3
>
> [...]
>
> Mine is the -164 version. Anything else needed to confirm working properly?
No,
but it would be great if we could have a copy of that EEPROM.
I've attached inline-patch that will dump its content to
the console via kernel messaging system.
If you are not entirely familiar with the procedure, then let
me know (off-list), I'm sure we can work that out.
Regards,
Christian
---
diff --git a/drivers/net/wireless/p54/eeprom.c b/drivers/net/wireless/p54/eeprom.c
index d687cb7..84eb993 100644
--- a/drivers/net/wireless/p54/eeprom.c
+++ b/drivers/net/wireless/p54/eeprom.c
@@ -544,6 +544,8 @@ int p54_parse_eeprom(struct ieee80211_hw *dev, void *eeprom, int len)
wrap = (struct eeprom_pda_wrap *) eeprom;
entry = (void *)wrap->data + le16_to_cpu(wrap->len);
+ print_hex_dump_bytes("P54E:", DUMP_PREFIX_OFFSET, eeprom, len);
+
/* verify that at least the entry length/code fits */
while ((u8 *)entry <= end - sizeof(*entry)) {
entry_len = le16_to_cpu(entry->len);
next prev parent reply other threads:[~2010-08-02 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 16:17 SMC 2802W -status unsupported David Cozatt
2010-08-01 16:35 ` Larry Finger
2010-08-02 8:46 ` Christian Lamparter [this message]
2010-08-01 19:59 David Cozatt
2010-08-01 20:34 ` Larry Finger
2010-08-02 6:17 ` Geoff Simmons
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=201008021046.32453.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=olbrannon@gmail.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;
as well as URLs for NNTP newsgroup(s).