From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: strange behaviour from "make localmodconfig" throws out ath9k stuff
Date: Sat, 27 Apr 2013 17:38:33 +0200 [thread overview]
Message-ID: <20130427153833.GC3355@free.fr> (raw)
In-Reply-To: <alpine.DEB.2.02.1304261459030.17575@oneiric>
Robert, All,
On Fri, Apr 26, 2013 at 03:05:02PM -0400, Robert P. J. Day wrote:
> probably a simple explanation for this, but my first time playing
> with "make localmodconfig" and it appears to be tossing all my
> ath9k-related module settings.
>
> currently running ubuntu on a 64-bit asus laptop with the following
> ath9k-related modules:
>
> $ lsmod | grep ath9k
> ath9k 149545 0
> mac80211 558577 1 ath9k
> ath9k_common 14054 1 ath9k
> ath9k_hw 408874 2 ath9k,ath9k_common
> ath 23828 3 ath9k,ath9k_common,ath9k_hw
> cfg80211 211955 3 ath9k,mac80211,ath
> $
>
> starting with current kernel "git pull", i do:
>
> $ make allmodconfig
>
> at which point i get:
>
> $ grep ATH9K .config
> CONFIG_ATH9K_HW=m
> CONFIG_ATH9K_COMMON=m
> CONFIG_ATH9K_DFS_DEBUGFS=y
> CONFIG_ATH9K_BTCOEX_SUPPORT=y
> CONFIG_ATH9K=m
> CONFIG_ATH9K_PCI=y
> CONFIG_ATH9K_AHB=y
> CONFIG_ATH9K_DEBUGFS=y
> CONFIG_ATH9K_DFS_CERTIFIED=y
> CONFIG_ATH9K_MAC_DEBUG=y
> CONFIG_ATH9K_RATE_CONTROL=y
> CONFIG_ATH9K_HTC=m
> CONFIG_ATH9K_HTC_DEBUGFS=y
> $
>
> which looks reasonable(?). then run:
>
> $ make localmodconfig
>
> have to answer maybe 4 questions manually, at which point i have:
>
> $ grep ATH9K .config
Can you send the output of your lsmod, please?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-04-27 15:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 19:05 strange behaviour from "make localmodconfig" throws out ath9k stuff Robert P. J. Day
2013-04-26 19:36 ` Yann E. MORIN
2013-04-27 0:47 ` Robert P. J. Day
2013-04-27 15:38 ` Yann E. MORIN [this message]
2013-04-27 17:30 ` Robert P. J. Day
2013-04-27 17:42 ` Yann E. MORIN
2013-04-27 17:48 ` Robert P. J. Day
2013-04-27 18:19 ` Robert P. J. Day
2013-04-28 20:28 ` Yann E. MORIN
2013-04-29 10:54 ` Robert P. J. Day
2013-04-29 14:11 ` Steven Rostedt
2013-04-29 14:28 ` Robert P. J. Day
2013-04-29 14:41 ` Steven Rostedt
2013-04-29 15:01 ` Robert P. J. Day
2013-04-29 15:13 ` Steven Rostedt
2013-04-29 15:19 ` Robert P. J. Day
[not found] ` <alpine.DEB.2.02.1304291121180.26536@oneiric>
2013-04-29 16:15 ` Steven Rostedt
2013-04-29 18:00 ` Steven Rostedt
2013-04-29 18:26 ` Robert P. J. Day
2013-04-29 18:41 ` Robert P. J. Day
2013-04-29 19:15 ` Robert P. J. Day
2013-04-29 20:43 ` Steven Rostedt
2013-04-29 20:50 ` Robert P. J. Day
2013-04-29 20:39 ` Robert P. J. Day
2013-04-29 23:40 ` Steven Rostedt
2013-04-29 14:02 ` Steven Rostedt
2013-04-27 17:47 ` Robert P. J. Day
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=20130427153833.GC3355@free.fr \
--to=yann.morin.1998@free.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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