Hi!
..
bcm43xx: Could not generate tssi2dBm table
Ah, cool! :-)
ACPI: PCI interrupt for device :02:02.0 disabled
And that's the end of the story.
What is this tssi2dBm table?
Recently st3 added some code for dynamic generation of the tssi2dbm
table based on the paXbY values in sprom.
I am running rev 991 on an iBook G4 (openfirmware id PowerBook6,5) and
Airport Extreme. I can associate with the base station, but I obtain
TX timeouts after the driver has transmitted approximately 410
packets, where 410 is 80% of the number of DMA slots (512).
Upon further investigation, it
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not being called here -- I see precisely the same as you. It stops
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
Hello everyone - almost have the driver functional,
but am running into this message when I try to
iwconfig the device up:
SoftMAC: cannot associate without being authenticated,
requested authentication
The machine is a beige G3 Powermac running Debian
Sarge 3.1r0. The driver tarball i have is
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
On Sunday 01 January 2006 22:21, Matteo Frigo wrote:
Michael Buesch [EMAIL PROTECTED] writes:
You have a device with a wlcore rev 5, which uses
one DMA engine for TX status blobs.
This code is untested and indeed likely to be wrong.
I have no facilities to test it (neither has any
This patch seems to do the trick. I am ignoring the
bcm43xx_rx_transmitstatus() mechanism and calling
bcm43xx_dma_handle_xmitstatus() directly.
patch
Description: Binary data
Hi BCM43xx hackers.
I'm one of the OpenWrt developers and I'm currently working on
integrating your driver into our development branch. I've written a
patch which adds support for a BCM43xx core integrated into the main SB
of the BCM47xx SoC. It applies against the dscape branch, which I
On Sunday 01 January 2006 23:52, you wrote:
This patch seems to do the trick. I am ignoring the
bcm43xx_rx_transmitstatus() mechanism and calling
bcm43xx_dma_handle_xmitstatus() directly.
Ok, very good. I will apply this patch and also remove
the dead bcm43xx_rx_transmitstatus code.
Thanks.
10 matches
Mail list logo