Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with custom config of kernel 2.6.34.1
Date: Tue, 13 Jul 2010 21:27:52 +0200	[thread overview]
Message-ID: <4C3CBE38.2010400@gmx.net> (raw)
In-Reply-To: <000f01cb226b$51f11430$f5d33c90$@pauljones.id.au>

Am 13.07.2010 11:11, schrieb Paul Jones:
>>> I use the kernel version 2.6.33.6 without any problems. But since I
>>> updated to the newer version 2.6.34.1 I'm not able to use a custom
>>> config anymore.
>>>
>>> I loaded the old config into the kernel menuconfig and stored it as
>>> new file linux-2.6.34.1.config. When I launched the overall make
>>> process the kernel patches were applied fine, but the process runs
>>> into text mode configuration:
>>
>> Thanks for your report. Could you provide a step-by-step procedure to
>> reproduce the problem from scratch ?
I changed the brconfig from kernel 2.6.33.x to 2.6.34.x. I loaded my 
custom kernel configuration into the linux menuconfig and stored it as 
new file. Obviously this not sufficient to migrate from one config 
version to another (I remember once in time it was, maybe 2.4.x days?).

>
> Isn't that just make oldconfig running? What happens if you press enter to
> give the default answer to every question?
Paul is absolutly right. I gave the default answer to every question 
(only a few...) and wrote this config back to 
mycustomlinuxconf-2.6.34.x.config.

The next time I do not expect to answer questions on the commandline 
during overall make process.

Thanks both for your help.

Regards,
Marcus

@Thomas: Please note my patch for making u-boot (correcting two typos) 
from 7.7.2010 . The fix is very straight forward (only two changed lines).

      reply	other threads:[~2010-07-13 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 20:52 [Buildroot] Problems with custom config of kernel 2.6.34.1 Ossy
2010-07-13  6:55 ` Thomas Petazzoni
2010-07-13  9:11   ` Paul Jones
2010-07-13 19:27     ` Ossy [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=4C3CBE38.2010400@gmx.net \
    --to=ossy1980@gmx.net \
    --cc=buildroot@busybox.net \
    /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