b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Oncaphillis <oncaphillis@snafu.de>
To: b43-dev@lists.infradead.org
Subject: Degradation on b43 14e4:4315 ?
Date: Thu, 16 Jun 2011 10:16:14 +0200	[thread overview]
Message-ID: <4DF9BBCE.10702@snafu.de> (raw)

Hi,

  I'm using my b43 14e4:4315 on my acer notebook for quite a while now.
I've started to use a wireless git-kernel and helped a bit in debugging
initial problems with this device. Since the early Fedora 14 it seemed to
work out of the box, but now when Fedora 14 moved to 2.6.35.12+ kernels
I loose connections on heavy transfer.

  It doesn't seem to be related to DMA since for testing purposes I've
disabled DMA.

Where there developments during the 2.6.35.x developments which could
explain such behaviour ?

Thanks

O.

             reply	other threads:[~2011-06-16  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  8:16 Oncaphillis [this message]
2011-06-16  9:22 ` Degradation on b43 14e4:4315 ? Rafał Miłecki
2011-06-16 21:23   ` Oncaphillis
2011-06-16 22:08     ` Rafał Miłecki
2011-08-26 19:09       ` Rafał Miłecki

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=4DF9BBCE.10702@snafu.de \
    --to=oncaphillis@snafu.de \
    --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).