From: Johannes Berg <johannes@sipsolutions.net>
To: Steve deRosier <steve@cozybit.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: libertas_tf
Date: Tue, 07 Sep 2010 23:02:45 +0200 [thread overview]
Message-ID: <d09bb244b842cf15a1513899d19bd39d@localhost> (raw)
In-Reply-To: <AANLkTimgvEShOKnA3TTf0_3p2ghP2OL8ngKPBgpkf+zf@mail.gmail.com>
On Tue, 7 Sep 2010 13:52:47 -0700, Steve deRosier <steve@cozybit.com>
wrote:
> I've got it working on 2.6.34-rc5-wl, branched off commit
> ~8425ee8329f33 sometimes near the end of April 2010. I've
> significantly reworked some MAC addr stuff, including forcing the
> module to request the MAC addr from the hardware and using that to set
> the addr before the calls to setup mac80211.
Ah, ok, but that's the thing I was worried about ... if you're now giving
it the MAC address before setting up the mac80211 stuff, you should be fine
(and we can remove the workaround from mac80211, yay)
> I'm now working on getting it all up to head, so patches should be
> coming soon. Actually, on that note, how would you prefer I get them
> to you? We're talking about an entire new module, libertas_tf_sdio,
> and lots of patches to the existing libertas_tf modules. Something
> like 40+ patches. Would you prefer a patchset posted, or me to squash
> a bunch into fewer but larger patches, or would you prefer to pull
> from my git tree?
Sounds like a lot of stuff... John will have to answer that. I think
posting it piecemeal as much as possible would probably be preferable.
johannes
next prev parent reply other threads:[~2010-09-07 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 19:21 libertas_tf Johannes Berg
2010-09-07 17:35 ` libertas_tf Steve deRosier
2010-09-07 18:39 ` libertas_tf Johannes Berg
2010-09-07 20:52 ` libertas_tf Steve deRosier
2010-09-07 21:02 ` Johannes Berg [this message]
2010-09-09 14:10 ` libertas_tf 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=d09bb244b842cf15a1513899d19bd39d@localhost \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=steve@cozybit.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).