All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clyde McPherson <ccmcphe@verizon.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Wireless and RFKILL
Date: Tue, 09 Nov 2010 13:19:02 -0500	[thread overview]
Message-ID: <4CD99096.5020105@verizon.net> (raw)

Hi,

I build and use the compat-wireless source for use with SBC 
applications, and I have a question about the wireless portion of the 
code. Our SBCs do not have RFKILL capabilities, and since we use 
wireless we are forced to include it in our kernel due to the depends in 
wireless. What are the chances of adding #ifdef's for CONFIG_RFKILL on 
the code segments that require RFKILL, this way integrators like myself 
would not need to load and/or build the rfkill modules? This would also 
save us memory and storage that is limited on a SBC system.


Thanks much
Tex


             reply	other threads:[~2010-11-09 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 18:19 Clyde McPherson [this message]
2010-11-09 18:53 ` Wireless and RFKILL, this way integrators like myself Johannes Berg
2010-11-09 18:57 ` Wireless and RFKILL John W. Linville

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=4CD99096.5020105@verizon.net \
    --to=ccmcphe@verizon.net \
    --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.