On Tue, Mar 23, 2010 at 11:23 PM, Chris Lopes clo...@gmail.com wrote:
I didn't try a cold reboot that did not involve the removal of
battery and power supply, so maybe it would work.
Honestly I am still perplexed (given modern hardware and software), as
to why/how:
1) Hibernate and
On Sat, Mar 13, 2010 at 7:48 PM, Michael Buesch m...@bu3sch.de wrote:
On Saturday 13 March 2010 19:38:01 Gábor Stefanik wrote:
I know this one it is compatible with aircrack supporting injection
Thank you for your invaluable help ..
thank
As a general rule, do not bug Michael
On Sat, Mar 13, 2010 at 7:05 PM, mic cat micac...@gmail.com wrote:
Hi all
i have 2 Broadcom network controller :
BCM4312 802.11 B/G 14E4:4315
This is supported in 2.6.32 and newer; though you may need to compile
with CONFIG_B43_FORCE_PIO if you have a netbook and/or a machine with
On Mon, Mar 8, 2010 at 11:28 AM, Marc Haber mh+bcm43xx-...@zugschlus.de wrote:
Hi Larry,
On Sat, Mar 06, 2010 at 07:57:57AM -0600, Larry Finger wrote:
On 03/06/2010 04:07 AM, Marc Haber wrote:
On Fri, Mar 05, 2010 at 05:54:24PM +, Chris Vine wrote:
You can get the Ideapad to work by
2010/3/8 Marc Haber mh+bcm43xx-d...@zugschlus.de:
Hi,
On Mon, Mar 08, 2010 at 12:54:44PM +0100, Gábor Stefanik wrote:
That message sounds like you are using iwlist to scan - try iw instead.
Yes, I am using iwlist. Has this changed? Have the tools like wicd
and/or network-manager already
On Thu, Mar 4, 2010 at 1:30 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 03/02/2010 03:57 PM, Michael Buesch wrote:
A bug in the PCI-E core code is able to show such behavior, because all
memory
transfers (MMIO and DMA) from the PCI device to the wireless core are
translated
by
On Thu, Mar 4, 2010 at 11:36 PM, Marc Haber mh+bcm43xx-...@zugschlus.de wrote:
On Thu, Mar 04, 2010 at 01:49:14PM -0500, William Bourque wrote:
Silly question, but did you try to up (ifconfig wlan0 up) the
interface before scanning?
I tried ip link set dev wlan0 up, which gave me a few more
Mailing list test, please ignore.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
2010/2/28 Nathan Schulte rekl...@gmail.com:
On Sat, Feb 27, 2010 at 7:03 PM, Nathan Schulte rekl...@gmail.com wrote:
2010/2/27 Larry Finger larry.fin...@lwfinger.net:
The printk's I sent yesterday can have timing info, but the timestamps
would not
be exactly coordinated - printk values seem
On Sun, Feb 28, 2010 at 7:00 PM, William Bourque
william.bour...@polymtl.ca wrote:
Chris Vine wrote:
This doesn't help on my netbook, I am afraid.
I confirm, it still crashes on my notebook as well. However the new
fallback to PIO behavior introduced earlier do a fine job getting it back
on
On Sun, Feb 28, 2010 at 7:00 PM, William Bourque
william.bour...@polymtl.ca wrote:
I confirm, it still crashes on my notebook as well. However the new
fallback to PIO behavior introduced earlier do a fine job getting it back
on track.
Btw, you are often refering to some documentation that
2010/2/28 Nathan Schulte rekl...@gmail.com:
2010/2/28 Gábor Stefanik netrolller...@gmail.com:
OK, this dump shows the 0x280a write happening with core 3, i.e. PCIE,
active. So, it is indeed probably the PCIE misc configuration
routine. Why it's 0x280a is still a mystery to me, it should
On Sat, Feb 27, 2010 at 5:37 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 02/27/2010 10:08 AM, Michael Buesch wrote:
On Saturday 27 February 2010 17:05:41 Larry Finger wrote:
On 02/27/2010 09:20 AM, Michael Buesch wrote:
On Saturday 27 February 2010 02:41:48 Gábor Stefanik wrote
2010/2/27 Nathan Schulte rekl...@gmail.com:
I've been following along with the linux-wireless thread, and wanted
to bring up a few points.
1) If the report in reference by Gábor: Well, we have a report from
someone with an Intel T7250, ... is mine, note that my processor is
actually a T5670
2010/2/28 Nathan Schulte rekl...@gmail.com:
2010/2/27 Gábor Stefanik netrolller...@gmail.com:
OK, I whipped up a quick test patch with changes found so far
implemented. Please test if this improves the situation.
Where can I find this patch?
-Nate
Oops... yes, I forgot it. Here
2010/2/28 Nathan Schulte rekl...@gmail.com:
2010/2/27 Gábor Stefanik netrolller...@gmail.com:
Oops... yes, I forgot it. Here it is!
No luck from me either.
And by the way, Lucas and I have the exact same hardware, so his is
indeed a T5670 as well.
-Nate
Are you sure it is exactly
On Fri, Feb 26, 2010 at 8:33 AM, Nathan Schulte rekl...@gmail.com wrote:
2010/1/25 Gábor Stefanik netrolller...@gmail.com
A few things to check:
-Is this on PhoenixBios?
I have the same laptop as Lucas, a Dell Vostro 1510. As Lucas has
mentioned, this is indeed a PhoenixBIOS
-Does
On Fri, Feb 26, 2010 at 12:12 PM, rekl...@gmail.com wrote:
On Feb 26, 2010 3:23am, Gábor Stefanik netrolller...@gmail.com wrote:
The firmware version included in 4.174.64.19 is 478.104 (notice that
is is not 4178.104, but 478.104 - the driver and firmware versions are
not related!).
Ah yes
2010/2/26 Nathan Schulte rekl...@gmail.com:
I apologize for so many messages. I wanted to note that the reasoning
for lsmod only showing the ntfs module, is due the fact that ntfs (and
b43 and ssb) are the only drivers compiled as modules.
When loading b43 without mmiotrace running, I receive
On Fri, Feb 26, 2010 at 4:04 PM, rekl...@gmail.com wrote:
On Feb 26, 2010 8:49am, Gábor Stefanik netrolller...@gmail.com wrote:
However, you did not do what I requested - before the 2nd mmiotrace,
load and unload wl (the hybrid driver), not b43 - it is wl that
appears to make the card work
2010/2/26 Larry Finger larry.fin...@lwfinger.net:
On 02/26/2010 09:27 AM, Gábor Stefanik wrote:
On Fri, Feb 26, 2010 at 4:13 PM, rekl...@gmail.com wrote:
On Feb 26, 2010 9:08am, Gábor Stefanik netrolller...@gmail.com wrote:
That's odd... the error only occurs when you stop the mmiotrace
2010/2/26 Chris Vine ch...@cvine.freeserve.co.uk:
On Fri, 26 Feb 2010 18:22:26 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
Note that enabling MMIO trace touches quite a few areas of the kernel
rather hard - for example, it AFAIK disables SMP. I wonder if acpi=off
or blacklisting
produced using wl. Or maybe the if-branch is the
wrong-way around - only Larry can tell.)
BTW does anyone know of a way to trace pci_read/write_config_dword
calls? Mmiotrace doesn't capture these.
2010/2/26 Chris Vine ch...@cvine.freeserve.co.uk:
On Fri, 26 Feb 2010 23:03:28 +0100
Gábor
2010/2/21 Rafał Miłecki zaj...@gmail.com:
2010/2/20 Larry Finger larry.fin...@lwfinger.net:
Some of the N PHYs need a revision in the handling of the PMU.
Signed-off-by: Larry Finger larry.fin...@lwfinger.net
---
John,
This will be needed for some of the N PHY devices - 2.6.34 amterial.
On Fri, Feb 19, 2010 at 7:02 PM, Larry Finger larry.fin...@lwfinger.net wrote:
Some of the N PHYs need a revision in the handling of the PMU.
Signed-off-by: Larry Finger larry.fin...@lwfinger.net
---
John,
This will be needed for some of the N PHY devices - 2.6.34 amterial.
Larry
---
On Sat, Feb 6, 2010 at 1:06 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 02/05/2010 10:27 AM, Gábor Stefanik wrote:
On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger larry.fin...@lwfinger.net
wrote:
On 02/04/2010 02:57 PM, Rafał Miłecki wrote:
---
Gábor: I think you missed specs here
Why would it be misconfigured?
On Sat, Feb 6, 2010 at 8:11 PM, strk s...@keybit.net wrote:
Is it me or this list is misconfigured ?
--srrk;
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 02/04/2010 02:57 PM, Rafał Miłecki wrote:
---
Gábor: I think you missed specs here. Could you check whole routine just for
sure, please? I don't understand whole radio and chanspec magic yet.
---
On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 02/04/2010 02:57 PM, Rafał Miłecki wrote:
---
Gábor: I think you missed specs here. Could you check whole routine just for
sure, please? I don't understand whole radio and chanspec magic yet.
---
2010/2/4 Rafał Miłecki zaj...@gmail.com:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/net/wireless/b43/phy_n.c | 4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/b43/phy_n.c
b/drivers/net/wireless/b43/phy_n.c
index
On Fri, Feb 5, 2010 at 7:09 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 02/05/2010 10:41 AM, Gábor Stefanik wrote:
On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger larry.fin...@lwfinger.net
wrote:
On 02/04/2010 02:57 PM, Rafał Miłecki wrote:
---
Gábor: I think you missed specs here
2010/2/5 Rafał Miłecki zaj...@gmail.com:
W dniu 5 lutego 2010 18:34 użytkownik Gábor Stefanik
netrolller...@gmail.com napisał:
2010/2/4 Rafał Miłecki zaj...@gmail.com:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/net/wireless/b43/phy_n.c | 4
1 files changed, 4
On Mon, Jan 25, 2010 at 9:15 PM, Lucas Thode ljth...@gmail.com wrote:
---start dmesg snippet---
[17189.121003] b43-pci-bridge :06:00.0: PCI INT A disabled
[17192.494272] cfg80211: Using static regulatory domain info
[17192.494279] cfg80211: Regulatory domain: US
[17192.494283]
2010/1/22 Rafał Miłecki zaj...@gmail.com:
John, I hope to have patch submission fixed, please let me know if there
is anything wrong still.
Nope, it is still base64-encoded.
I personally use Thunderbird 2 for patch submission (had weird
problems with Thunderbird 3 beta - not sure about the
You don't even need to mention it, as Git handles offset/fuzzy patches
automatically.
2010/1/18 Rafał Miłecki zaj...@gmail.com:
W dniu 18 stycznia 2010 01:28 użytkownik Gábor Stefanik
netrolller...@gmail.com napisał:
2010/1/18 Rafał Miłecki zaj...@gmail.com:
Signed-off-by: Rafał Miłecki zaj
2010/1/17 Rafał Miłecki zaj...@gmail.com:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/net/wireless/b43/phy_n.c | 112
+-
1 files changed, 110 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/b43/phy_n.c
2010/1/18 Rafał Miłecki zaj...@gmail.com:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
V2: updated to apply without fuzz
Actually, you do not need to do that - offset or fuzzy patches will
still be applied cleanly AFAIK, without any intervention.
(John, correct me if I'm wrong here...)
On Fri, Jan 15, 2010 at 2:12 AM, Miklos Vajna vmik...@frugalware.org wrote:
Hi,
I tried asking on #bcm-users, then found the wiki where it's suggested
to report to this list, so I'm doing so. Sorry for the noise on IRC.
A description of the problem at hand:
My card works fine when I use it
2010/1/6 Gábor Stefanik netrolller...@gmail.com:
2010/1/6 Rafał Miłecki zaj...@gmail.com:
V2: fix typo in deaf_count counting, improve b43_mac_[sr] calls,
rename function. Thanks Michael!
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/net/wireless/b43/phy_n.c | 58
2010/1/6 Rafał Miłecki zaj...@gmail.com:
W dniu 6 stycznia 2010 23:35 użytkownik Gábor Stefanik
netrolller...@gmail.com napisał:
2010/1/6 Rafał Miłecki zaj...@gmail.com:
V2: fix typo in deaf_count counting, improve b43_mac_[sr] calls,
rename function. Thanks Michael!
Signed-off-by: Rafał
On Wed, Jan 6, 2010 at 11:55 PM, Rafał Miłecki zaj...@gmail.com wrote:
2010/1/6 Rafał Miłecki zaj...@gmail.com:
I've decided to made LP-PHY init code review for compatibility with specs
and found some issues.
We lack some code for higher PHY revisions (up from 2/3) and for some
specific
On Thu, Jan 7, 2010 at 12:12 AM, Rafał Miłecki zaj...@gmail.com wrote:
W dniu 6 stycznia 2010 23:59 użytkownik Larry Finger
larry.fin...@lwfinger.net napisał:
On 01/06/2010 04:49 PM, Gábor Stefanik wrote:
2010/1/6 Rafał Miłecki zaj...@gmail.com:
W dniu 6 stycznia 2010 23:35 użytkownik Gábor
On Wed, Jan 6, 2010 at 12:00 AM, John Daiker daikerj...@gmail.com wrote:
I have a BCM4312 rev 01 (14e4:4315) card in my HP Mini netbook. I am having
troubles connecting to any WEP secured AP.
I know the trick about having to load with pio=1 for the device to stay
happy (and forget about
2010/1/6 John Daiker daikerj...@gmail.com:
On 01/05/2010 03:48 PM, Gábor Stefanik wrote:
On Wed, Jan 6, 2010 at 12:00 AM, John Daikerdaikerj...@gmail.com wrote:
I have a BCM4312 rev 01 (14e4:4315) card in my HP Mini netbook. I am
having
troubles connecting to any WEP secured AP.
I know
2010/1/4 Rafał Miłecki zaj...@gmail.com:
2010/1/3 Daniel Kuehn enha...@gmail.com:
I am the (un)lucky owner of a Macbook of late 2009 model, which has a
Broadcom combo card (BT + WLAN sharing 3 antennas) but neither the b43 or
broadcom-sta support it, I just get invalid parameters or the
On Sun, Jan 3, 2010 at 3:41 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 01/02/2010 08:11 PM, Daniel Kuehn wrote:
Hi,
I am the (un)lucky owner of a Macbook of late 2009 model, which has a
Broadcom combo card (BT + WLAN sharing 3 antennas) but neither the b43
or broadcom-sta support
Update your pci.ids file - what you have is a BCM4311/02 ABG.
Also, could you check a few more kernels in-between .29 and .32?
On Sat, Dec 26, 2009 at 8:01 PM, yha...@yhager.com wrote:
Hi,
First, some adminstrativa..
$ uname -srvmip
Linux 2.6.29 #4 Fri Aug 28 13:17:05 IDT 2009 i686 VIA
On Fri, Dec 18, 2009 at 11:53 AM, Erik esi...@gmail.com wrote:
I just bought a new laptop and installed Gentoo on it:
# dmesg|grep -i error
[ 4.113200] ssb: ERROR: PLL init unknown for device 4322
[ 4.113201] ssb: ERROR: PMU resource config unknown for device 4322
[ 4.702250]
On Tue, Dec 1, 2009 at 8:11 PM, Peter Stuge pe...@stuge.se wrote:
Rafał Miłecki wrote:
I know there were some series of notebooks accepting only one kind of
wireless cards. Not sure what vendor was that... Dell or HP maybe?
HP and IBM/Lenovo both have BIOS checks for particular PCI IDs and
On Sun, Nov 29, 2009 at 9:44 PM, Andrew Benton b3n...@gmail.com wrote:
On 29/11/09 18:41, Larry Finger wrote:
It seems that none of the special things that the wl driver does on my
system has any affect on the DMA errors. I would appreciate if one of
you would do the following:
1. Set
??? This only adds a printk...
On Sun, Nov 29, 2009 at 12:43 AM, Larry Finger
larry.fin...@lwfinger.net wrote:
Sorry about the problem with the previous try. This one does write the
PCI configuration the same as wl does.
Please see if this one helps.
Larry
Index:
On Wed, Nov 18, 2009 at 6:15 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 11/18/2009 08:34 AM, Oncaphillis wrote:
The first ioread16 actually succeeds, only the second one fails.
My lspci -vnn tells me that the memory is:
Memory at 5710 (64-bit, non-prefetchable) [size=16K]
On Thu, Nov 19, 2009 at 12:39 AM, Michael Buesch m...@bu3sch.de wrote:
Please keep it on-list. This is really important to get this debugged
properly.
On Thursday 19 November 2009 00:23:18 Oncaphillis wrote:
On 11/18/2009 11:59 PM, Michael Buesch wrote:
What kind of device is that? Some
On Fri, Nov 13, 2009 at 5:05 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 11/13/2009 05:16 AM, Michael Buesch wrote:
Ok, so my guess is that the DMA allocator simply returned high memory
that was unusable to the device. My new code explicitly checks for that (and
a
few other things)
2009/10/28 Linus Torvalds torva...@linux-foundation.org:
On Sun, 25 Oct 2009, Gábor Stefanik wrote:
Also, is there any reference to a failed channel switch in the log?
I've been debugging this some more, and it looks like there are more
issues at play than just the DMA problem
wrapper
Software RFKILL (required by calibration) is also implemented in
this round.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
Michael, could you please do the PHY reset part? I can't seem to
understand its relationship to wireless_core_reset... also, it's
heavily ssb-speak, which I
wrapper
Software RFKILL (required by calibration) is also implemented in
this round.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
(Mail re-sent as my mailer seems to have dropped it; apologies if
you receive it twice.)
Michael, could you please do the PHY reset part? I can't seem
2009/10/25 Michael Buesch m...@bu3sch.de:
On Sunday 25 October 2009 16:26:36 Gábor Stefanik wrote:
Michael, could you please do the PHY reset part? I can't seem to
understand its relationship to wireless_core_reset... also, it's
heavily ssb-speak, which I am not good at.
Where
On Sun, Oct 25, 2009 at 7:17 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
Ok, so I got myself (or rather, Patricia) a new Dell 11 inspiron laptop,
and everything seems to work, except for the wireless. It's a Broadcom
BCM4312b/g LP-PHY.
In fact, even the wireless works at least to
2009/10/25 Linus Torvalds torva...@linux-foundation.org:
On Sun, 25 Oct 2009, Gábor Stefanik wrote:
Could you please test the tag master-2009-08-26 from
wireless-testing? That one was the first version that worked, and in
that specific build, my card (exactly the same as yours) worked
On Sun, Oct 25, 2009 at 10:39 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sun, 25 Oct 2009, Linus Torvalds wrote:
Ok, this machine is a 1.3GHz Core 2 Duo, so no Atom crap.
Oh, and I compile for x86-64, in case anybody cares. But I assume all sane
developers have long since
On Sun, Oct 25, 2009 at 11:08 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sun, 25 Oct 2009, Chris Vine wrote:
On Sun, 25 Oct 2009 22:40:50 +0100 Gábor Stefanik netrolller...@gmail.com
suggested:
Another thing to test: boot into Windows (or any other OS where the [..]
You
2009/10/25 Larry Finger larry.fin...@lwfinger.net:
On 10/25/2009 05:28 PM, Gábor Stefanik wrote:
On Sun, Oct 25, 2009 at 11:08 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Sun, 25 Oct 2009, Chris Vine wrote:
On Sun, 25 Oct 2009 22:40:50 +0100 Gábor Stefanik
netrolller
On Sun, Oct 18, 2009 at 1:44 AM, Charles Moschel fre...@carolina.rr.com wrote:
On Sat, 17 Oct 2009 14:10:19 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
On 10/17/2009 01:12 PM, Charles Moschel wrote:
Also, what I noticed is that everyone with this problem appears to
have an Intel
On Fri, Oct 16, 2009 at 6:01 PM, Chris Vine ch...@cvine.freeserve.co.uk wrote:
On Fri, 16 Oct 2009 9:45:40 -0400
fre...@carolina.rr.com wrote:
2.6.32-rc? and wireless-compat was thought to work as well as
wireless-testing ... hmmm
Ah right. I had been trying 2.6.32-rc4 by itself and
Sounds interesting... especially now that N-PHY is actually being
reverse-engineered (or is it?).
The modded 4320 is an attempt to replace the built-in OS and use it
with b43 as a softmac device... am I right?
On 10/9/09, Michael Buesch m...@bu3sch.de wrote:
Hi,
I've currently got two
On Fri, Oct 9, 2009 at 6:22 PM, Michael Buesch m...@bu3sch.de wrote:
On Friday 09 October 2009 18:17:20 Larry Finger wrote:
On 10/09/2009 10:41 AM, Gábor Stefanik wrote:
G-PHY revision =2 is handled by b43legacy, not b43, so it shouldn't
be a problem.
That is not true.
--
Greetings
2009/10/6 Lance Hepler nlhep...@gmail.com:
2009/10/6 Gábor Stefanik netrolller...@gmail.com:
So, this error happens specifically on suspend/resume?
No, it'll happen pretty frequently the first time I try to connect,
but always after I suspend+resume. And once the DMA error pops up, It
just
On Fri, Oct 2, 2009 at 11:04 PM, fre...@carolina.rr.com wrote:
Hi Folks --
I've read in the archives about DMA errors with the LP-PHY, but there didn't
seem to be any conclusion. Any guidance on what I can test to get it working?
It's reproducable on my Lenovo G530 laptop. (Yes, I know
2009/9/29 Ed Spiridonov edo@gmail.com:
what is current LP PHY status?
Working in 2.6.32-rc1, though no calibration yet; so performance is
probably not on par with wl_hybrid or ndiswrapper.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
2009/9/29 Ed Spiridonov edo@gmail.com:
2009/9/29 Gábor Stefanik netrolller...@gmail.com:
2009/9/29 Ed Spiridonov edo@gmail.com:
what is current LP PHY status?
Working in 2.6.32-rc1, though no calibration yet; so performance is
probably not on par with wl_hybrid or ndiswrapper.
i
2009/9/29 Ed Spiridonov edo@gmail.com:
2009/9/29 Gábor Stefanik netrolller...@gmail.com:
2009/9/29 Ed Spiridonov edo@gmail.com:
2009/9/29 Gábor Stefanik netrolller...@gmail.com:
2009/9/29 Ed Spiridonov edo@gmail.com:
what is current LP PHY status?
Working in 2.6.32-rc1, though
On Thu, Sep 17, 2009 at 1:32 PM, Christian Schoenebeck
c...@users.sf.net wrote:
Hi!
What is the current development status for the BCM4322 chip? Is it working
in the meantime?
If not, I can also try to hack the b43 driver for supporting it, at least
if I get the necessary informations.
CU
2009/9/17 Thomas Ilnseher il...@gmx.de:
Am Donnerstag, den 17.09.2009, 18:02 +0200 schrieb Rafał Miłecki:
Hi,
I would like to ask about status of LP-PHY status. Could you explain
to simple end-user what is missing in current implementation? Is this
just calibration for performance, or
You are essentially implementing dead code at this point - this will
only ever be called if hardware-accelerated TX power control is
enabled - and HW TX power control is unsupported, even for G-PHYs.
On Wed, Sep 16, 2009 at 9:37 PM, Thomas Ilnseher il...@gmx.de wrote:
This patch adds the
2009/9/16 Thomas Ilnseher il...@gmx.de:
Am Mittwoch, den 16.09.2009, 21:40 +0200 schrieb Gábor Stefanik:
You are essentially implementing dead code at this point - this will
only ever be called if hardware-accelerated TX power control is
enabled - and HW TX power control is unsupported, even
On Mon, Sep 14, 2009 at 7:42 PM, Michael Buesch m...@bu3sch.de wrote:
On Monday 14 September 2009 18:56:08 Daniel Schmitt wrote:
well, same issue:
ssb: Sonics Silicon Backplane found on PCI device :00:02.0
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)
ssb: Core 1
The generic analog switch routine is not correct for LP-PHY according
to the latest specs. Implement the proper analog core switch routine.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
diff --git a/drivers/net/wireless/b43/phy_lp.c
b/drivers/net/wireless/b43/phy_lp.c
index 80da9c7
On Sun, Sep 13, 2009 at 7:05 PM, Daniel Schmitt
dan...@schmitt-united.de wrote:
Hello Group,
I posted a few days ago my problems with this WLAN minipci card:
Linux OpenWrt 2.6.28.10 #5 Thu Sep 10 20:36:33 CEST 2009 armv5teb unknown
00:02.0 0280: 14e4:4325 (rev 02)
Subsystem:
On Fri, Sep 11, 2009 at 10:54 PM, Thomas Ilnseher il...@gmx.de wrote:
Hi List,
I installed the latest version of OpenWRT on a ASUS WL-520GU.
I compiles a few kernel patches to make the OpenWRT kernel (2.6.28.10)
compatible with compat wireless.
Than I patched OpenWRT to build
2009/9/12 Gábor Stefanik netrolller...@gmail.com:
On Fri, Sep 11, 2009 at 10:54 PM, Thomas Ilnseher il...@gmx.de wrote:
Hi List,
I installed the latest version of OpenWRT on a ASUS WL-520GU.
I compiles a few kernel patches to make the OpenWRT kernel (2.6.28.10)
compatible with compat
On Thu, Sep 10, 2009 at 8:43 PM, Daniel Schmitt
dan...@schmitt-united.de wrote:
Hello bcm43xx developers,
I have problems using a bcm4306 rev 2 minipci card. I got the card out of
Microsoft mn700. I also have 2 atheros cards. They work.
Here is output of
uname -a: Linux OpenWrt 2.6.28.10 #5
On Thu, Sep 10, 2009 at 7:34 PM, Michael Buesch m...@bu3sch.de wrote:
From: Albert Herranz albert_herr...@yahoo.es
This adds support for Soft-MAC SDIO devices to b43.
The driver still lacks some fixes for SDIO devices, so it's currently
marked as BROKEN.
Is it actually completely broken; or
Do you have the threaded-IRQ patches applied? Also, what card is this?
(BCM4312?) Try upgrading your firmare (use v478 or the new v5xx one).
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
On Tue, Sep 8, 2009 at 7:50 PM, John Daikerdaikerj...@gmail.com wrote:
On 09/08/2009 07:54 AM, Larry Finger wrote:
Michael Buesch wrote:
On Tuesday 08 September 2009 15:47:32 Dave Young wrote:
I tested wireless-testing b43 driver, but got Fatal DMA error
then the controller keep
On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net wrote:
John Daiker wrote:
On 09/08/2009 07:54 AM, Larry Finger wrote:
Michael Buesch wrote:
On Tuesday 08 September 2009 15:47:32 Dave Young wrote:
I tested wireless-testing b43 driver, but got Fatal DMA error
then the
2009/9/8 Larry Finger larry.fin...@lwfinger.net:
Gábor Stefanik wrote:
On Tue, Sep 8, 2009 at 8:16 PM, Larry Fingerlarry.fin...@lwfinger.net
wrote:
Your PHY and your radio are the same as mine. In fact, the one thing I
noticed is that you are using i386 architecture, whereas mine is
x86_64
2009/9/6 Michael Buesch m...@bu3sch.de:
On Sunday 06 September 2009 20:42:00 Gábor Stefanik wrote:
On Sun, Sep 6, 2009 at 2:49 PM, Michael Bueschm...@bu3sch.de wrote:
PCMCIA support works well and is not experimental anymore.
Signed-off-by: Michael Buesch m...@bu3sch.de
---
drivers
On Fri, Sep 4, 2009 at 12:02 AM, Daniel Lenskidlen...@gmail.com wrote:
On Thu, 2009-09-03 at 16:37 -0500, Larry Finger wrote:
Daniel Lenski wrote:
Larry,
I agree on the ridiculously poor packaging... did I mention they're 1gb+
extracted?
I didn't look at what is contained within that
(CCing bcm43xx-dev.)
Could you post the dmesg output when this happens? (Enable debugging
in b43 before taking the log.)
2009/9/2 Brian J. Mc Hugh bjmch...@aya.yale.edu:
Hi Gábor,
I seem to remember you explaining there was a bluetooth problem and it
couldn't coexist. Is that right?
Brian
On Wed, Sep 2, 2009 at 11:57 PM, Brian J. Mc Hughbjmch...@aya.yale.edu wrote:
Hi Gábor and Broadcom,
In essense, my card seems to be receiving signal but transmitting none.
I was appreciate your help,
Thanks,
Brian
Here are the diagnostics;
#uname -r
2.6.26-2-686
#dmesg | grep b43
the Windows driver in ndiswrapper.
2009/9/2 Gábor Stefanik netrolller...@gmail.com
On Wed, Sep 2, 2009 at 11:57 PM, Brian J. Mc Hughbjmch...@aya.yale.edu
wrote:
Hi Gábor and Broadcom,
In essense, my card seems to be receiving signal but transmitting none.
I was appreciate your help
On Thu, Sep 3, 2009 at 1:55 AM, Alex Elsayedeternal...@gmail.com wrote:
I just recently got a new laptop with an Intel 5350, which means my
4328 [PCI-ID] (4321 official Broadcom designation) is not in use any
longer. I am in the Seattle area, but can send it by post if needed.
On Thu, Sep 3, 2009 at 2:37 AM, Brian J. Mc Hughbjmch...@aya.yale.edu wrote:
Hi Larry and Gabor,
Here is the file. Sorry about contacting both of you independently
Brian
Hmm, this SPROM has the BT coexistence bit unset - in that case, BT is
not the reason behind the bug.
Do you know the
, I still don't have wireless.
Brian
Could you try compiling equivalent kernels from Kernel.org? Just so
that we can rule out a Debian bug (e.g. in a distro-specific kernel
patch).
2009/9/2 Gábor Stefanik netrolller...@gmail.com
On Thu, Sep 3, 2009 at 2:37 AM, Brian J. Mc Hughbjmch
2009 02:15:55 Gábor Stefanik wrote:
static void lpphy_pr41573_workaround(struct b43_wldev *dev)
{
struct b43_phy_lp *lpphy = dev-phy.lp;
@@ -1357,28 +1488,440 @@ static void lpphy_pr41573_workaround(struct
b43_wldev *dev)
b43_lptab_read_bulk(dev
I suspect that this will trigger a response from a spambot.
reset
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
(required by calibration) is also implemented in
this round.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
Larry, please check if I got the math in PHY Cordic right!
drivers/net/wireless/b43/main.c |2 +-
drivers/net/wireless/b43/main.h |2 +
drivers/net/wireless/b43/phy_lp.c
(required by calibration) is also implemented in
this round.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
V2: Fix a mistake I made in the PHY Cordic routine.
drivers/net/wireless/b43/main.c |2 +-
drivers/net/wireless/b43/main.h |2 +
drivers/net/wireless/b43/phy_lp.c | 686
-Make use of the b43_phy_set/mask/maskset helpers.
-Fix a few errors in the code.
-Make the code more readable.
Signed-off-by: Gábor Stefanik netrolller...@gmail.com
---
The phy-analog == 3 to phy-rev == 3 change in A-PHY is intentional,
it's a bugfix/spec conformance fix.
drivers/net/wireless
1 - 100 of 194 matches
Mail list logo
