From: chris at martin.cc <chris@martin.cc>
To: b43-dev@lists.infradead.org
Subject: Switching to 4.174.64.19 firmware for G-PHY cards?
Date: Thu, 3 Mar 2011 10:02:51 +1100 [thread overview]
Message-ID: <AANLkTi=n6fL8c4ZX9_DBOLi6VqB1h=dSh6LF7RTOO-KU@mail.gmail.com> (raw)
In-Reply-To: <4D6EBDE0.8020005@lwfinger.net>
----------------------------------------------------------
Chris Martin
m: +61 419 812 371
----------------------------------------------------------
On Thu, Mar 3, 2011 at 9:00 AM, Larry Finger <Larry.Finger@lwfinger.net>
wrote:
> On 03/02/2011 06:20 AM, chris at martin.cc wrote:
>>
>> 2011/3/2 Rafa? Mi?ecki<zajec5@gmail.com>:
>>>
>>> I checked for kernels in OpenWRT.
>>> OpenWRT 10.03 is 2.6.32.10
>>> OpenWRT 10.03.1-rc4 is 2.6.32.25
>>>
>>> I can see 2.6.32(.0) at least have:
>>> b43: Add LP PHY Analog Switch Support
>>> that's good.
>>>
>>> Maybe compiling b43 with debugging could help to understand what is
>>> going on? Could insmod b43.ko pio=1 be workaround?
>>>
>>
>> Just to clarify. I tested 10.03-rc4 - and trunk wicth is 2.6.36.x
>> I will also confirm the versions tomorrow
>
> Chris,
>
> This problem is getting more and more curious.
>
> I have two systems with 14e4:4315 LP PHY cards. One is x86_64 and the
other
> is i386. I added kmemleak checking to each and have been running
networking
> for about 3 hours on the 64-bit system, and 18 hours for 32 bit. Neither
> shows any memory leaks associated with b43. Both are using 508.1084
> firmware. Most of the tests were in STA mode, but a few minutes with one
> hosting an AP for the other has not shown any leaks.
>
> I imagine that memory is pretty tight on the openWRT system. Does "free"
> work there? If so, what are the results just before you start the
bridging?
>
> Larry
next prev parent reply other threads:[~2011-03-02 23:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 12:21 Switching to 4.174.64.19 firmware for G-PHY cards? Rafał Miłecki
2010-12-07 12:28 ` Rafał Miłecki
2010-12-07 15:32 ` Larry Finger
2010-12-07 19:21 ` Hauke Mehrtens
2011-03-01 13:33 ` Rafał Miłecki
2011-03-02 0:11 ` chris at martin.cc
2011-03-02 0:20 ` Rafał Miłecki
2011-03-02 3:30 ` chris at martin.cc
2011-03-02 9:58 ` Rafał Miłecki
2011-03-02 10:52 ` Rafał Miłecki
2011-03-02 11:22 ` Jonas Gorski
2011-03-02 12:20 ` chris at martin.cc
2011-03-02 22:00 ` Larry Finger
2011-03-02 23:02 ` chris at martin.cc [this message]
2011-03-03 4:43 ` chris at martin.cc
2011-03-03 7:58 ` Rafał Miłecki
2011-03-03 11:50 ` Rafał Miłecki
2011-03-03 23:49 ` chris at martin.cc
2011-03-07 12:35 ` Rafał Miłecki
2011-03-04 0:37 ` chris at martin.cc
2011-03-07 12:26 ` Rafał Miłecki
2011-03-08 1:12 ` chris at martin.cc
2011-03-07 13:12 ` Rafał Miłecki
2011-03-07 16:41 ` Rafał Miłecki
2011-03-08 1:25 ` chris at martin.cc
2011-03-08 13:26 ` Rafał Miłecki
2011-03-09 0:44 ` chris at martin.cc
2011-03-09 0:47 ` Rafał Miłecki
2011-03-09 0:47 ` chris at martin.cc
2011-03-03 4:55 ` chris at martin.cc
2011-03-02 23:00 ` chris at martin.cc
2011-03-02 12:14 ` chris at martin.cc
2011-03-02 13:12 ` Rafał Miłecki
2011-03-02 23:12 ` Jonas Gorski
2011-03-03 3:40 ` chris at martin.cc
2011-03-03 7:55 ` Rafał Miłecki
2011-03-03 15:52 ` Larry Finger
2011-03-03 5:34 ` chris at martin.cc
2011-03-03 4:23 ` chris at martin.cc
2011-03-02 10:08 ` Rafał Miłecki
2011-03-02 12:17 ` chris at martin.cc
2011-03-03 3:44 ` chris at martin.cc
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='AANLkTi=n6fL8c4ZX9_DBOLi6VqB1h=dSh6LF7RTOO-KU@mail.gmail.com' \
--to=chris@martin.cc \
--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;
as well as URLs for NNTP newsgroup(s).