Please test if this fixes hwcrypto.
Note that we will require v4 firmware with this patch.
I will remove v3 firmware support, because it's _really_
a huge pain to support both firmware versions.
If someone wants to have v3 support, please fork my tree.
Or alternatively simply install v4 firmware, w
On Tuesday 14 November 2006 15:40, Johannes Berg wrote:
> On Wed, 2006-11-15 at 01:29 +1100, Paul TBBle Hampson wrote:
>
> > Just to summarise results so far:
> >
> > (Current version)
> > bcm43xx-d80211 w/v3 firmware and TKIP: Garbled broadcast RX
> > bcm43xx-d80211 w/v4 firmware and TKIP: Garbl
On Sun, Nov 12, 2006 at 09:34:27AM +0100, Michael Buesch wrote:
> On Sunday 12 November 2006 02:24, Paul TBBle Hampson wrote:
>> On Sat, Nov 11, 2006 at 04:07:05PM +0100, Michael Buesch wrote:
> >> On Saturday 11 November 2006 07:32, Paul Hampson wrote:
> >>> Michael Buesch bu3sch.de> writes:
>>
On Wed, 2006-11-15 at 01:40 +1100, Paul TBBle Hampson wrote:
> bcm43xx-d80211 w/v3 firmware and WEP-104: Garbled _everything_ RX
> Of course, that's to be expected. WEP only uses broadcast keys, and
> we knew they were failing in software mode.
Hmm, not sure about this, but it sort of confirms my
On Wed, 2006-11-15 at 01:29 +1100, Paul TBBle Hampson wrote:
> Just to summarise results so far:
>
> (Current version)
> bcm43xx-d80211 w/v3 firmware and TKIP: Garbled broadcast RX
> bcm43xx-d80211 w/v4 firmware and TKIP: Garbled broadcast RX
> bcm43xx-d80211 w/v4 firmware and WEP-104: Correct br
On Wed, Nov 15, 2006 at 01:29:59AM +1100, Paul TBBle Hampson wrote:
> Just to summarise results so far:
> (Current version)
> bcm43xx-d80211 w/v3 firmware and TKIP: Garbled broadcast RX
> bcm43xx-d80211 w/v4 firmware and TKIP: Garbled broadcast RX
> bcm43xx-d80211 w/v4 firmware and WEP-104: Correc
On Sun, 12 Nov 2006 09:34:27 +0100, Michael Buesch wrote:
> TKIP hw encryption needs some modifications to the d80211 stack.
> There are patches available, but I think they are not merged, yet.
> John, do you know the state on these patches?
Waiting for Hong Liu to respond to Johannes' comments.
13 Kas 2006 Pts 00:54 tarihinde şunları yazmıştınız:
> On Mon, 2006-11-13 at 00:41 +0200, Ismail Donmez wrote:
> > > Thanks for information, this firmware would also solve the recent
> > > roothole.
> >
> > s/roothole/security vulnerability would be better =)
>
> Ummm, the problem was in the driver
On Mon, 2006-11-13 at 00:41 +0200, Ismail Donmez wrote:
> > Thanks for information, this firmware would also solve the recent roothole.
>
> s/roothole/security vulnerability would be better =)
Ummm, the problem was in the driver, not the firmware. You can't have
security problems like that in th
13 Kas 2006 Pts 00:40 tarihinde şunları yazmıştınız:
> 12 Kas 2006 Paz 23:47 tarihinde, Michael Buesch şunları yazmıştı:
> > On Sunday 12 November 2006 21:43, Ismail Donmez wrote:
> > > Hi,
> > >
> > > 12 Kas 2006 Paz 10:34 tarihinde şunları yazmıştınız:
> > > > Ah, and also note that you _need_ fi
12 Kas 2006 Paz 23:47 tarihinde, Michael Buesch şunları yazmıştı:
> On Sunday 12 November 2006 21:43, Ismail Donmez wrote:
> > Hi,
> >
> > 12 Kas 2006 Paz 10:34 tarihinde şunları yazmıştınız:
> > > Ah, and also note that you _need_ firmware from a v4 binary driver
> > > to have hardware encryption
On Sunday 12 November 2006 21:43, Ismail Donmez wrote:
> Hi,
> 12 Kas 2006 Paz 10:34 tarihinde şunları yazmıştınız:
> > Ah, and also note that you _need_ firmware from a v4 binary driver
> > to have hardware encryption with bcm43xx.
>
> Last time I heard only v3 firmware was supported. Is that cha
Hi,
12 Kas 2006 Paz 10:34 tarihinde şunları yazmıştınız:
> Ah, and also note that you _need_ firmware from a v4 binary driver
> to have hardware encryption with bcm43xx.
Last time I heard only v3 firmware was supported. Is that changed?
Regards,
ismail
-
To unsubscribe from this list: send the li
On Sunday 12 November 2006 02:24, Paul TBBle Hampson wrote:
> On Sat, Nov 11, 2006 at 04:07:05PM +0100, Michael Buesch wrote:
> > Please _don't_ remove CCs.
>
> Sorry, I was sending via the gmane web interface, I guess it doesn't
> honour CCs.
>
> This one's via muttng's NNTP support to gmane, so
On Sat, Nov 11, 2006 at 04:07:05PM +0100, Michael Buesch wrote:
> Please _don't_ remove CCs.
Sorry, I was sending via the gmane web interface, I guess it doesn't
honour CCs.
This one's via muttng's NNTP support to gmane, so I _think_ it's going
to the right places.
> On Saturday 11 November 2006
Please _don't_ remove CCs.
On Saturday 11 November 2006 07:32, Paul Hampson wrote:
> Michael Buesch bu3sch.de> writes:
>
> > On Thursday 09 November 2006 23:23, Paul Hampson wrote:
> > > I've been backporting the bcm43xx-d80211 driver to whatever the released
> > > 2.6 kernel was using the rt2x0
Michael Buesch bu3sch.de> writes:
> On Thursday 09 November 2006 23:23, Paul Hampson wrote:
> > I've been backporting the bcm43xx-d80211 driver to whatever the released
> > 2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to
> > current wireless-dev but with a workaround for not
On Thursday 09 November 2006 23:23, Paul Hampson wrote:
> Hi,
>
> Long time lurker, first time poster. ^_^
>
> I've been backporting the bcm43xx-d80211 driver to whatever the released
> 2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to
> current wireless-dev but with a workaro
Ivo Van Doorn gmail.com> writes:
> > I've been backporting the bcm43xx-d80211 driver to whatever the released
> > using the rt2x00 project's d80211 stack
> Just a note about that stack, it should only be used on kernel 2.6.17
> and higher.
Thanks, I've noted that at the berlios wiki.
--
Paul "T
Hi,
I've been backporting the bcm43xx-d80211 driver to whatever the released
2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to
current wireless-dev but with a workaround for not having a ieee80211_dev
pointer and still using the _tfm interface instead of the _cypher interface
Hi,
Long time lurker, first time poster. ^_^
I've been backporting the bcm43xx-d80211 driver to whatever the released
2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to
current wireless-dev but with a workaround for not having a ieee80211_dev
pointer and still using the _tfm i
21 matches
Mail list logo
