From: David Woodhouse <dwmw2@infradead.org>
To: b43-dev@lists.infradead.org
Subject: [QUESTION] 4331 support
Date: Sat, 27 Aug 2011 13:22:16 +0100 [thread overview]
Message-ID: <1314447737.14057.154.camel@shinybook.infradead.org> (raw)
In-Reply-To: <87k49zkq30.fsf@purkki.adurom.net>
On Sat, 2011-08-27 at 15:15 +0300, Kalle Valo wrote:
> David Woodhouse <dwmw2@infradead.org> writes:
>
> > On Sat, 2011-08-27 at 15:08 +0300, Kalle Valo wrote:
> >> > It should be possible for it to be based on the latest release from
> >> > Linus.
> >>
> >> But then it would not contain all the changes in wireless-testing.
> >
> > That is the point, yes.
>
> Then b43 would be out of sync from rest of wireless development, for
> example everything that's happening in mac80211 etc. To me that sounds
> bad.
No, that's fine ? it's quite normal. The generic hardware support, like
BCM4331 and new PHY support, is much better off that way.
Where we are making intrusive changes to mac80211 that require changes
to all drivers simultaneously, we can still do those in wireless-testing
on top of the changes from the b43 tree.
(Or if there was a proper git tree with the core mac80211 changes, a b43
tree could also just pull from that tree. But that probably isn't
necessary.)
--
dwmw2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110827/fc2189a0/attachment.bin>
next prev parent reply other threads:[~2011-08-27 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 11:16 [QUESTION] 4331 support Maxime Vincent
2011-08-22 14:33 ` David Woodhouse
2011-08-22 14:47 ` Larry Finger
2011-08-22 14:50 ` David Woodhouse
2011-08-27 12:08 ` Kalle Valo
2011-08-27 12:09 ` David Woodhouse
2011-08-27 12:15 ` Kalle Valo
2011-08-27 12:22 ` David Woodhouse [this message]
2011-08-22 20:50 ` Rafał Miłecki
2011-08-23 11:40 ` Maxime Vincent
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=1314447737.14057.154.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=b43-dev@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox