From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Jasin Colegrove <j.wholesalesupply@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: kernel .30 BROKE ATH5K with my AR5212 atheros.
Date: Thu, 9 Jul 2009 10:02:34 -0700 [thread overview]
Message-ID: <43e72e890907091002r2dd36efevbfbce06155beb7e5@mail.gmail.com> (raw)
In-Reply-To: <b6c5339f0907090955v7b99a7ebq26e7cc67ab2493f5@mail.gmail.com>
On Thu, Jul 9, 2009 at 9:55 AM, Bob Copeland<me@bobcopeland.com> wrote:
> On Thu, Jul 9, 2009 at 12:42 PM, Jasin
> Colegrove<j.wholesalesupply@gmail.com> wrote:
>>> BTW, can you (re?)post the "Atheros AR5212 chip found (MAC xxx,
>>> PHY xxxx)?"
>>>
>> What exact information do you want and where can I find it?
>
> Run 'dmesg'; a string like the above is printed out when the module
> loads. In case there was something broken specifically for your
> chipset, the mac/phy versions will help narrow it down.
>
>> $git bisect start v2.6.30-rc4 v2.6.29 -- drivers/net net/
>>
>> Is that what you where hinting at? I wasted a whole day trying to fix
>> errors in drivers/staging before I was told I could just disable
>> compilation of staging with one switch. Oh well...
>
> Yes, that's what I meant. And it does help to have a relatively
> slimmed down .config, especially when bisecting. :\
I'd add net/mac80211 and net/wireless in there as well, just to be safe.
Luis
next prev parent reply other threads:[~2009-07-09 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6c354a1a0906301524m389d49a9sfd812e1ea4740ff5@mail.gmail.com>
2009-06-30 22:50 ` Fwd: kernel .30 BROKE ATH5K with my AR5212 atheros Jasin Colegrove
2009-07-02 15:36 ` Bob Copeland
2009-07-05 12:13 ` Jasin Colegrove
2009-07-07 1:35 ` Jasin Colegrove
2009-07-07 3:07 ` Bob Copeland
2009-07-08 6:58 ` Jasin Colegrove
2009-07-08 11:42 ` Bob Copeland
2009-07-09 16:42 ` Jasin Colegrove
2009-07-09 16:55 ` Bob Copeland
2009-07-09 17:02 ` Luis R. Rodriguez [this message]
2009-07-09 17:48 ` Bob Copeland
2009-07-09 17:50 ` Luis R. Rodriguez
2009-07-09 18:36 ` Jasin Colegrove
2009-07-09 18:44 ` Bob Copeland
2009-07-14 15:34 ` Jasin Colegrove
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=43e72e890907091002r2dd36efevbfbce06155beb7e5@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=j.wholesalesupply@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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).