From: feldmaus <feldmann_markus@gmx.de>
To: linux-wireless@vger.kernel.org
Subject: Re: Do not get BCM4303 to work
Date: Sat, 03 Jan 2009 19:49:36 +0100 [thread overview]
Message-ID: <gjobt8$v22$1@ger.gmane.org> (raw)
In-Reply-To: <gjob72$t2j$1@ger.gmane.org>
I forgot to wrote my Kernel Options
CONFIG_LEDS_CLASS=m
CONFIG_LEDS_TRIGGERS=y
CONFIG_MAC80211_LEDS=y
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
CONFIG_INPUT_POLLDEV=m
My b43legacy Driver is built as modul.
Regards Markus
next prev parent reply other threads:[~2009-01-03 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 6:15 Do not get BCM4303 to work feldmaus
2008-09-08 7:34 ` maximilian attems
2008-09-08 19:05 ` Larry Finger
2008-09-12 23:02 ` feldmaus
2008-09-13 0:30 ` Larry Finger
2008-09-26 16:32 ` feldmaus
2008-09-26 17:27 ` Larry Finger
2008-09-26 21:07 ` feldmaus
2008-09-26 23:40 ` Larry Finger
2009-01-03 18:37 ` feldmaus
2009-01-03 18:49 ` feldmaus [this message]
2009-01-03 19:00 ` feldmaus
2009-01-03 19:05 ` Larry Finger
2009-01-03 19:39 ` feldmaus
2009-01-04 11:34 ` feldmaus
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='gjobt8$v22$1@ger.gmane.org' \
--to=feldmann_markus@gmx.de \
--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 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).