From: aruna.hewapathirane@gmail.com (Aruna Hewapathirane)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Minimul Config file for Dev Environment
Date: Sat, 30 Jul 2016 23:06:42 -0400 [thread overview]
Message-ID: <CAFSeFg9oqNGv8M6eczC089DdAjZyGQhY3gFD1V7oaMua0=zG3A@mail.gmail.com> (raw)
In-Reply-To: <20160730195458.GA13338@jittu>
> Hi Folks,
> I usually compile the linux kernel by copying current system .config
file. But the
> problem it compile bunch things that I don't which is required. My aim
> is setup filesystem environmrnt setup on my laptop.
> Could somebody point the minimal .config file that will save from me
> reading all the options and compile the kernel quickly and test it.
1 - Plug in and turn on *all* your external devices, this step is to ensure
that
the laptop kernel loads all the required modules for your devices.
2 - On the laptop run:
lsmod > /tmp/jitendra-laptop
This will store the currently loaded modules in the laptop to the file:
/tmp/jitendra-laptop
3 - Pass it in as a LSMOD parameter to make:
make LSMOD=/tmp/jitendra-laptop localmodconfig
4 - Done !
5 - Install ccache. It will improve your build time dramatically. It caches
objects. So it will reduce subsequent builds.
Some interesting history about localmodconfig is here:
http://www.h-online.com/open/features/Good-and-quick-kernel-configuration-creation-1403046.html
Good luck - Aruna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160730/716dcb3f/attachment.html
next prev parent reply other threads:[~2016-07-31 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 19:54 Minimul Config file for Dev Environment Jitendra
2016-07-30 20:25 ` François
2016-07-30 23:16 ` Greg KH
2016-07-31 3:06 ` Aruna Hewapathirane [this message]
2016-07-31 10:24 ` Jitendra
2016-07-31 17:52 ` Aruna Hewapathirane
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='CAFSeFg9oqNGv8M6eczC089DdAjZyGQhY3gFD1V7oaMua0=zG3A@mail.gmail.com' \
--to=aruna.hewapathirane@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).