Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Paul Stoaks" <paul@foresight-mands.com>
To: <linux-wireless@vger.kernel.org>
Subject: Noob question:  Development Environment
Date: Mon, 12 Nov 2012 09:49:54 -0800	[thread overview]
Message-ID: <071701cdc0fe$218fc9b0$64af5d10$@com> (raw)

Greetings.  Sorry to interrupt with a newbie question, but I need some help
on setting up a linux wireless development and test environment.  What I
would like to have is a stable development and test environment where I can
work for a period of months without having to upgrade the kernel version on
my development and test machines, but staying close to the bleeding edge
with the core wireless modules and drivers.

I have successfully built the wireless-testing tree from GIT, but have only
discovered how to install the entire kernel produced from the build, not
just the wireless modules.  What I would like to do is to install only the
wireless modules, as I can do with the compat-wireless tree.  I have gotten
compat-wireless to work for me with a lot of labor (refreshing patches), but
I'm unsure of the correct work-flow with it.

How are you folks accomplishing this?

Please feel free to point me to the archives or a web page.  I've groped all
around the internet and have failed to answer my questions.  (If you point
me to the archives, please give me a keyword to search on as I have looked
and been unsuccessful in finding the relevant information.)

Thank you very much!
Paul Stoaks



             reply	other threads:[~2012-11-12 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 17:49 Paul Stoaks [this message]
2012-11-12 18:13 ` Noob question: Development Environment Thomas Pedersen
2012-11-12 18:27   ` Javier Cardona
2012-11-12 18:44     ` Paul Stoaks

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='071701cdc0fe$218fc9b0$64af5d10$@com' \
    --to=paul@foresight-mands.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox