mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org, greg@kroah.com,
	akpm@linux-foundation.org
Subject: Re: [RFC] scripts: add gen-linux-conf for remote kernel configuration
Date: Thu, 12 Nov 2009 16:31:26 -0800	[thread overview]
Message-ID: <43e72e890911121631q2e4afd17k59dfb30bc1d309f2@mail.gmail.com> (raw)
In-Reply-To: <9b2b86520911121531y70e05d4rcd361ec33799bc0a@mail.gmail.com>

On Thu, Nov 12, 2009 at 3:31 PM, Alan Jenkins
<sourcejedi.lkml@googlemail.com> wrote:
> On 11/12/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
>> The new 'make localmodconfig' proves very useful but on low end
>> systems we do not want to 'git clone' an entire kernel tree or
>> download a whole kernel but just cross compile the kernel on a
>> bigger machine. The .config generated with 'make localmodconfig'
>> is still very helpfup though so to aid users and developers
>> with that add a script which builds a tarball with only the
>> necessary kernel glue stuff to be able to generate a local
>> minimum kernel configuration with 'make localmodconfig'.
>>
>> With this you can copy to your target device a relatively
>> small tarball (1.2 MB currenty) and, allows you to modify
>> the kernel config for your tree (mconf, conf, etc) and
>> finally run 'make localmodconfig'.
>>
>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>> ---
>>
>> I had an itch to scratch and that was to use 'localmodconfig'
>> on a small netbook but I didn't want to clone a whole tree
>> or even compile an entire kernel on it. This did the trick,
>> thought others might find it useful.
>>
>> A little grimy the bash script, but hey it works and its simple
>> enough. I tried to reduce the Makefile count to only arch/ but
>> found that that didn't do the trick. Perhaps this can be optimized
>> more, suggestions welcomed. Maybe it should be written in Go :)
>>
>> What would be *real* nice is to give an IP address of a box and
>> have it build and fetch a localmodconfig .config for you.
>>
>>   Luis
>
> Thanks for posting this.
>
> When I tried this for my netbook, my approach was to copy
> /proc/modules and /boot/config from the netbook.  As a shameless hack,
> I temporarily bind mounted /proc/modules on the build system.  I guess
> the cleaner way would be to copy the result of "lsmod", and have
> localmodconfig accept "LSMOD_FILE=file".
>
> Naturally I think my approach is simpler, despite not having actually
> implemented it properly :).  What do you think about it?

It does sound simpler, but you'd still need the netbook's config and
upgrade it to the the desired kernel's config, so you'd need to
address that too. Just lsmod won't cut it I think.

  Luis

      reply	other threads:[~2009-11-13  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 23:03 Luis R. Rodriguez
2009-11-12 23:31 ` Alan Jenkins
2009-11-13  0:31   ` Luis R. Rodriguez [this message]

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=43e72e890911121631q2e4afd17k59dfb30bc1d309f2@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sourcejedi.lkml@googlemail.com \
    /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

all inboxes | Powered by JetHome®