public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dan Kegel <dank@kegel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix allnoconfig on arm with small tweak to kconfig?
Date: Tue, 14 Sep 2004 09:29:52 +0100	[thread overview]
Message-ID: <20040914092951.A15258@flint.arm.linux.org.uk> (raw)
In-Reply-To: <41464C8E.3060004@kegel.com>; from dank@kegel.com on Mon, Sep 13, 2004 at 06:42:38PM -0700

On Mon, Sep 13, 2004 at 06:42:38PM -0700, Dan Kegel wrote:
> Russell King wrote:
> > If you want something that's guaranteed to work, use one of the
> > per-platform default configurations.  Nothing else carries any
> > guarantee what so ever on ARM.
> 
> I did give that a shot, but every one I tried seemed to be
> broken.  (I may have been using a too-new compiler, and I probably
> suffer from impatient newbie-itis.)  Can you suggest which commands
> to use to retrieve a working default configuration?

Obviously I can't comment on the problems you're seeing with those due
to the lack of details.  However, last time I built a pure bk-based
tree (4 days ago), the following worked:

- ebsa110
- netwinder
- imx
- integrator
- lubbock
- rpc
- s3c2410
- versatile

However, many of these have sub-classes of either cpus or machines,
and running allnoconfig against these will again generate invalid
configurations.

So:

$ make netwinder_defconfig
$ make

will build a working kernel.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-09-14  8:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13  7:53 Fix allnoconfig on arm with small tweak to kconfig? Dan Kegel
2004-09-13  8:15 ` Russell King
2004-09-13 15:22   ` Dan Kegel
2004-09-13 18:51     ` Russell King
2004-09-13 19:29       ` Herbert Poetzl
2004-09-13 21:06         ` Nicolas Pitre
2004-09-13 21:34         ` Russell King
2004-09-14  1:42       ` Dan Kegel
2004-09-14  8:29         ` Russell King [this message]
2004-09-17  8:39           ` Dan Kegel

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=20040914092951.A15258@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.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