b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Problems with b43 wirelesss
Date: Sun, 20 Jun 2010 20:37:23 +0200	[thread overview]
Message-ID: <AANLkTikTuXmetpuYBFcINQupADFNkBsZql5unUbs5ikw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikSK3zNyWPRhHPZeFrfO3iQW97w9CCoUqolLf-z@mail.gmail.com>

2010/6/20 Magnus Therning <magnus@therning.org>:
> 2010/6/20 G?bor Stefanik <netrolller.3d@gmail.com>:
>> On Sun, Jun 20, 2010 at 7:02 PM, Magnus Therning <magnus@therning.org> wrote:
> [...]
>>> It works perfectly well for me with the broadcom proprietary driver.
>>> Except of course that it pains my heart to have to use it.
>>
>> Can you provide comparative mmiotraces?
>
> I'm sure I could, if I only knew how :-)
>
> Point me to some information about how it's done and I'll try to get it done
> today.
>
> /M

Check out http://www.mjmwired.net/kernel/Documentation/tracers/mmiotrace.txt

When tracing b43, it is important to also unload ssb before starting
the trace - it is ssb that does the IO mapping for b43, so if ssb
remains loaded, mmiotrace won't catch the MMIO mappings of the device.

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

  reply	other threads:[~2010-06-20 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 21:51 Problems with b43 wirelesss Magnus Therning
2010-06-19  9:33 ` Rafał Miłecki
2010-06-19 12:35   ` Magnus Therning
2010-06-19 13:26     ` Larry Finger
2010-06-20 16:57       ` Magnus Therning
2010-06-20  0:59     ` William Bourque
2010-06-20 17:02       ` Magnus Therning
2010-06-20 18:18         ` Gábor Stefanik
2010-06-20 18:31           ` Magnus Therning
2010-06-20 18:37             ` Gábor Stefanik [this message]
2010-06-24 22:27               ` Magnus Therning

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=AANLkTikTuXmetpuYBFcINQupADFNkBsZql5unUbs5ikw@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --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).