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
Is it me or this list is misconfigured ?
--srrk;
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
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 28/12/09 04:49, Larry Finger wrote:
Hi,
In the latest Broadcom driver, I found code that sets the timeout field of the
SSB configuration for some BCM4311 and all BCM4312 devices. Please test this
patch following a cold boot.
Sadly it does not work. Tested with the mainline kernel
On 12/28/2009 09:52 AM, Andrew Benton wrote:
Sadly it does not work. Tested with the mainline kernel. The DMA errors
persist.
Shucks!!! I was hoping for a late Christmas present. Unfortunately, more coal in
my stocking.
As usual, thanks for testing.
Larry
On Monday 28 December 2009 05:49:14 Larry Finger wrote:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO_SHIFT);
This does not make any sense.
Did you mean:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO);
+ tmp |= 3;
So you set
On 12/28/2009 12:33 PM, Michael Buesch wrote:
On Monday 28 December 2009 05:49:14 Larry Finger wrote:
+tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO_SHIFT);
This does not make any sense.
Did you mean:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO);
On Monday 28 December 2009 20:09:05 Larry Finger wrote:
I did get that wrong. The Broadcom code does the equivalent of
tmp = tmp ~0x77 | 3
Ok, so you need my version of the masking.
which is what my code ended up doing by accident, but REQ is set to zero.
Yeah, OK to me. It's a workaround
Hi,
In the latest Broadcom driver, I found code that sets the timeout field of the
SSB configuration for some BCM4311 and all BCM4312 devices. Please test this
patch following a cold boot.
Thanks,
Larry
Index: wireless-testing/drivers/ssb/driver_pcicore.c
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary. Such a situation is allowed on
my system, but it might be forbidden on Atom processors. Please try
this really ugly
On Monday 21 December 2009 22:31:10 Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary. Such a situation is allowed on
my system
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary
On Monday 21 December 2009 23:02:39 Larry Finger wrote:
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3
Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary. Such a situation is allowed on
my system, but it might be forbidden on Atom processors
On 12/21/2009 04:11 PM, Michael Buesch wrote:
On Monday 21 December 2009 23:02:39 Larry Finger wrote:
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error
On 12/21/2009 04:18 PM, William Bourque wrote:
Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary. Such a situation is allowed on
my
On Monday 21 December 2009 23:20:06 Larry Finger wrote:
Here, it was slot 74 that crossed the page boundary. At 110 bytes per
every 2 slots, that works out to 4070 bytes for 0 - 73. From that, I
infer that the cache starts on a page boundary.
Yeah well. For you.
--
Greetings, Michael.
On Mon, 21 Dec 2009 17:18:01 -0500
William Bourque william.bour...@polymtl.ca wrote:
Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try it.
Thanks,
Larry
In exploring the cause of DMA errors for BCM4312 devices on Atom
processors, other drivers that work write to PCI configuration
On Sat, 19 Dec 2009 10:43:29 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try
it.
Thanks,
Larry
I applied this to 2.6.32.2 and it didn't
On 19/12/09 19:55, Chris Vine wrote:
On Sat, 19 Dec 2009 10:43:29 -0600
Larry Fingerlarry.fin...@lwfinger.net wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try
it.
Thanks,
Larry
I
On 12/19/2009 05:11 PM, Andrew Benton wrote:
On 19/12/09 19:55, Chris Vine wrote:
I applied this to 2.6.32.2 and it didn't help with the DMA errors I am
afraid.
Chris
Same here, the patch didn't prevent the DMA errors, however, I did
notice that it only reported the error once, it
Larry Finger wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try it.
Thanks,
Larry
A little late but I just tested and I have the same bug.
However, unlike Andrew, the error keep
On 12/19/2009 10:15 PM, William Bourque wrote:
Larry Finger wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try it.
Thanks,
Larry
A little late but I just tested and I have the same
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
and wasn't sure if anything happened so I rmmod b43; modprobe b43
and copied the ssb_sprom file back to the desktop as
new_original_sprom and then did ssb-sprom -i Desktop/
new_original_sprom -P and my new ID's were displayed so it was time
to test this so I started trying the card in various
and wasn't sure if anything happened so I rmmod b43; modprobe b43
and copied the ssb_sprom file back to the desktop as
new_original_sprom and then did ssb-sprom -i Desktop/
new_original_sprom -P and my new ID's were displayed so it was time
to test this so I started trying the card in various
to test this so I started trying the card in various computers
and was elated with the success of things.
Results now in Mac OS X on a BW G3, a PowerPC Dual G5 Xserve and
an generic Intel x86 PC sporting a Core 2 Quad is that the card is
natively recognized and supported.
http
On Monday 09 June 2008 12:03:35 Dale Walsh wrote:
While the process has now become much simpler, I think it's extremely
dangerous if it doesn't perform some kind of verification on the data
that is being copied before it actually performs the firmware update.
It performs an 8bit CRC check.
On 10/10/07, John W. Linville [EMAIL PROTECTED] wrote:
On Wed, Oct 10, 2007 at 12:08:08PM -0400, sean darcy wrote:
Nothing at all about the 4311 card in dmesg.
Made sure NetworkManager was working. Restarted it. I can see the icon.
No connection. If I connect the wire it starts up the
Compaq Presario C714NR, Intel GM965
uname -r
2.6.23-0.224.rc9.git6.fc8
lspci
01:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan
mini-PCI (rev 02)
Installed b43-fwcutter and followed the instructions at
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware
Got
On Wed, Oct 10, 2007 at 12:08:08PM -0400, sean darcy wrote:
Nothing at all about the 4311 card in dmesg.
Made sure NetworkManager was working. Restarted it. I can see the icon.
No connection. If I connect the wire it starts up the wired connection.
Please post the output of this command:
sean darcy wrote:
Compaq Presario C714NR, Intel GM965
uname -r
2.6.23-0.224.rc9.git6.fc8
lspci
01:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan
mini-PCI (rev 02)
As John Linville suggested, rev 02 of the 4311's are not supported. At the
moment, the reverse
engineers
I was wondering whether there exists a test framework/there is a need
for automated tests, which could be run by everyone, without the
knowledge what is exactly going on in bcm43xx development. What kind
of test would be of any interest to you? Functional/performance
blackbox tests? Coverage tests
With this card:
LinkSys Wireless-G WPC54GS (ver.2))
Chip ID 0x4318, rev 0x2
Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID
Jim McCloskey wrote:
With this card:
LinkSys Wireless-G WPC54GS (ver.2))
Chip ID 0x4318, rev 0x2
Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243,
The patch below implements a quick-and-dirty approach to solving the problem of
DMA with more than 1 GB memory. Unfortunately, I don't have the hardware to test
it. The patch is intended for the wireless-2.6 tree. It will not work with
2.6.18-rcX. Please report your results, and the log messages
On Tuesday 19 September 2006 18:40, Larry Finger wrote:
The patch below implements a quick-and-dirty approach to solving the problem
of
DMA with more than 1 GB memory. Unfortunately, I don't have the hardware to
test
it. The patch is intended for the wireless-2.6 tree. It will not work
Am Dienstag 19 September 2006 18:50 schrieb Michael Buesch:
If you want 1G, get a device which supports this.
I am not affected by this issue but as mentioned earlier: could you fall back
to non-dma mode? If not, you should fail completely instead of trying to run
a setup that is know to not
, should it be possible to implement a test for 30-bit
hardware and more than 1 GB
memory early enough to switch the interface to pio mode?
Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
. I found what
Linville did for the b44
chip.
In your estimation, should it be possible to implement a test for 30-bit
hardware and more than 1 GB
memory early enough to switch the interface to pio mode?
Larry
Must admit the patch seemed like a stretch, but tried it anyway
On Tue, 2006-09-19 at 18:50 +0200, Michael Buesch wrote:
If you want 1G, get a device which supports this.
This is really not an option.
First and foremost reason is that I like many others use a notebook with
built in hardware. So the option to simply replace the hardware is
unrealistic at
Zahir Toufie wrote:
Must admit the patch seemed like a stretch, but tried it anyway, as
predicted, the same exception still exists.
OK, I have'nt been hacking the kernel for many years now but how does
the Win XP driver then work with ndiswrapper. Surely it should be
failing with a similar
This is the same issue as with PCI-E hardware. _Lots_ of people
request it, but nobody is going to implement and test it.
Well, I can't do it for you, as I don't have the hardware.
--
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
Michael,
In trying various things in mac_suspend, I accidentally messed up the test for IRQ ready so that the
code returned immediately. The bottom line was that nothing went wrong. There were no crashes and no
hangs. On that basis, I changed the code as shown in the following patch. This code
On Sunday 02 July 2006 17:45, you wrote:
Michael,
In trying various things in mac_suspend, I accidentally messed up the test
for IRQ ready so that the
code returned immediately. The bottom line was that nothing went wrong. There
were no crashes and no
hangs. On that basis, I changed
On Sat, 2005-12-31 at 02:37 +, David Woodhouse wrote:
At that point I can use dhclient successfully and Legacy IP works.
Hm, almost. If I leave a ping running, I see an occasional TX timeout,
followed by a reset -- and then I have to manually set the ESSID again
before it'll work any more.
I've just tried the current (20051230) snapshot on the 2.6.15-rc7-git4
(Fedora Rawhide) kernel on a PowerBook. I also used the patch from
http://marc.theaimsgroup.com/?l=linux-netdevm=113591302004639w=2
The resulting kernel package (which also installs on FC4 with --nodeps)
is at
48 matches
Mail list logo
