All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: linux-wireless@vger.kernel.org
Subject: Re: Problem with BCM943224
Date: Thu, 10 Mar 2011 10:28:28 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110310T112254-310@post.gmane.org> (raw)
In-Reply-To: AANLkTim9hhX1VV93X7-+61hNsxit=AJiHgrt9ByWg9+V@mail.gmail.com

Rafał Miłecki <zajec5@...> writes:

> 
> It seems all reads are 1 (0xffffffff). Can this be some bug in driver?
> Can this be because I use adapter mini PCIe to PCIe x1? I remember
> such a situation when I connected adapter to PCIe x16 and used N-PHY
> card SSB based.
> 

I am using a Dell laptop (Latitude E6410) with 43224 installed and no
issues with it. We also have a test setup over here which is a desktop
model in which we use the 4313 in half-mini-pci to PCIe x1 adapter. Also
had 43224 in same adapter and both did not give issues with the si_attach,
which scans the chipset for the cores. Reading back 0xFFFFFFFF is reason
to abort this scan and end in a failure.

Gr. AvS



  parent reply	other threads:[~2011-03-10 10:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 10:59 Problem with BCM943224 Rafał Miłecki
2011-03-09 15:44 ` Larry Finger
2011-03-09 16:26   ` Rafał Miłecki
2011-03-09 16:38     ` Larry Finger
2011-03-09 16:50       ` Rafał Miłecki
2011-03-09 16:53       ` Gábor Stefanik
2011-03-09 17:11         ` Larry Finger
2011-03-09 18:04           ` Rafał Miłecki
2011-03-09 18:44             ` Larry Finger
2011-03-10  9:27             ` Stanislaw Gruszka
2011-03-17 15:34               ` Stanislaw Gruszka
2011-03-10 17:40       ` Rafał Miłecki
2011-03-10 18:35         ` Larry Finger
2011-03-10 10:28 ` Arend van Spriel [this message]
2011-03-10 10:56   ` Rafał Miłecki
2011-03-10 11:15     ` Arend van Spriel
2011-03-10 12:59       ` Rafał Miłecki
2011-03-11 14:18 ` 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=loom.20110310T112254-310@post.gmane.org \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.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.