All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clyde McPherson <ccmcphe@verizon.net>
To: b43-dev@lists.infradead.org
Subject: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
Date: Sat, 19 Jun 2010 18:45:27 -0400	[thread overview]
Message-ID: <4C1D4887.5080500@verizon.net> (raw)
In-Reply-To: <AANLkTinPItb-gl2adWe4VKL1G1FH-nBFSml8K9Kd2-bC@mail.gmail.com>

Gabor:
I hopt you are talking in general terms when you say don't force PIO 
mode. My platform is the ARM processor, and all my customers use the 
4318E CF (PCMCIA) card as their choice, since we don't have a PCI bus. 
My distributions all have force PIO mode on. I hope that is okay?

-Tex

,
> 2010/6/19 neubauten84<neubauten84@yahoo.it>:
>    
>> Ok..sorry for html mails..
>> I recompiled kernel from vanilla adding PIO mode forcing and nothing changes because I still have to use b43.conf with qos=0 option. If I don't bcm4312 doesn't connect.
>>      
> Do NOT enable PIO mode forcing! The only thing that does is ALWAYS use
> PIO - even when DMA is usable. In 2.6.35, you should see the driver
> loading in DMA mode, failing, and falling back to PIO. So, it is
> important NOT to disable DMA.
>
> Also, needing qos=0 is another problem, as QoS is supported in b43 AFAIK.
>
>    
>> I attached new dmesg with or without b43.conf file.
>>
>> The problem is not related to dma, I think, because even with pio forcing the connection (specially when is under pressure, when download traffic is high) at a time falls down and I have to reload b43.
>>
>> --- Ven 18/6/10, G?bor Stefanik<netrolller.3d@gmail.com>  ha scritto:
>>
>> Da: G?bor Stefanik<netrolller.3d@gmail.com>
>> Oggetto: Re: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
>> A: "neubauten84"<neubauten84@yahoo.it>
>> Cc: b43-dev at lists.infradead.org
>> Data: Venerd? 18 giugno 2010, 17:41
>>
>> 2010/6/18 neubauten84<neubauten84@yahoo.it>
>>      
>>> Linux neubauten84-laptop 2.6.35-4-generic #5-Ubuntu SMP Wed Jun 16 18:53:19 UTC 2010 i686 GNU/Linux
>>> Is there a newer ubuntu kernel?
>>>
>>>        
>> No. However. for debugging kernel issues, it is not a good idea to run
>> distro kernels - try an official kernel.org release.
>>
>> Also, please stop posting HTML emails to the list.
>>
>> --
>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>>
>>
>>
>>      
>
>
>    

  reply	other threads:[~2010-06-19 22:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 10:11 Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) neubauten84
2010-06-19 14:06 ` Gábor Stefanik
2010-06-19 22:45   ` Clyde McPherson [this message]
2010-06-20  4:48     ` Gábor Stefanik
  -- strict thread matches above, loose matches on Subject: below --
2010-06-16 10:36 neubauten84
2010-06-16 14:59 ` Gábor Stefanik
2010-06-16 20:05   ` neubauten84
2010-06-16 20:45     ` Gábor Stefanik
2010-06-17  7:52       ` neubauten84
2010-06-17 12:39         ` Gábor Stefanik
2010-06-17 13:46           ` neubauten84
2010-06-17 19:43             ` Gábor Stefanik
2010-06-17 20:20               ` neubauten84
2010-06-17 20:31                 ` Gábor Stefanik
2010-06-18  7:31                   ` neubauten84
2010-06-18 15:41                     ` Gábor Stefanik

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=4C1D4887.5080500@verizon.net \
    --to=ccmcphe@verizon.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.