From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: linux-wireless@vger.kernel.org
Cc: mcgrof@winlab.rutgers.edu
Subject: Build instructions for cross-compilation environment
Date: Wed, 15 Jul 2009 13:09:34 -0700 [thread overview]
Message-ID: <4A5E377E.6090705@redfish-solutions.com> (raw)
Hi.
I'm the lead developer for Astlinux.
We're doing a kernel bump from 2.6.26.8 to 2.6.27.26, and wanted to take
the opportunity to start using compat-wireless at the same time, because
we need (amongst other things) better mac80211/cfg80211/nl80211 and
AP-mode for the Ath5k chipset (AR5413, et al).
The README included in the tarball (compat-wireless-2.6.30.tar.bz2)
discusses building replacement drivers on the same system and placing
them into updates/.
I'd like to cross-compile this on a system and replace the drivers that
have been deposited by the plain-vanilla kernel build.
Also, a list of what CONFIG_xxx symbols I need to turn off to ensure
that there is no "residue" left over from the kernel build to interfere
with the compat-wireless build would be helpful (or alternatively,
what's the bare essential list of CONFIG_xxx symbols that need to be
enabled to "hook" compat-wireless into an existing kernel).
Looking at the Makefiles, it doesn't seem that cross-compilation is
ready out-of-the-box:
MADWIFI=$(shell $(MODPROBE) -l ath_pci)
OLD_IWL=$(shell $(MODPROBE) -l iwl4965)
Please reply to me directly (or even on Cc). I tried to join the list a
couple of weeks ago, but my request hasn't yet been processed.
Thanks,
-Philip
next reply other threads:[~2009-07-15 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:09 Philip A. Prindeville [this message]
2009-07-15 21:51 ` Build instructions for cross-compilation environment Bob Copeland
2009-07-15 22:11 ` Luis R. Rodriguez
2009-07-15 22:40 ` Philip A. Prindeville
2009-07-16 16:19 ` Luis R. Rodriguez
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=4A5E377E.6090705@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@winlab.rutgers.edu \
/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.