public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: towsonu2003@gmail.com
Cc: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: bcm43xx: iwlist scan: "no scan results" with 2.6.19.1
Date: Mon, 18 Dec 2006 12:05:21 -0600	[thread overview]
Message-ID: <4586D861.9040708@lwfinger.net> (raw)

I read your message on LKML and the bugzilla entry. For best results with bcm43xx problems, please 
post to the bcm43xx mailing list or to the netdev mailing list (both are on the CC list here).

Unfortunately, you built your 2.6.19.1 system with bcm43xx debugging disabled. It is impossible to 
say what happened, but usually when booting to Windows fixes a problem, the fault lies in the 
firmware, but the lack of debugging info doesn't even let us know what firmware was loaded.

With the info you provide and your inability to test patches, there isn't much we can do.

Larry

                 reply	other threads:[~2006-12-18 18:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4586D861.9040708@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=towsonu2003@gmail.com \
    /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