All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Contents of the "origin/ulf/linux-2.6.30.2" branch. Help with testing wanted.
Date: Wed, 12 Aug 2009 17:13:54 +0200	[thread overview]
Message-ID: <h5um7k$ioq$2@ger.gmane.org> (raw)
In-Reply-To: <200908121433.31479.marcin@juszkiewicz.com.pl>

On 12-08-09 14:33, Marcin Juszkiewicz wrote:

>> I introduced the possibility to build linux using
>> make<board>_defconfig, instead of using a
>> defconfig in a board directory under linux.
>> LINUX26_DEFCONFIG needs to be defined.
>
> Interesting, will check. I see a problem anyway because linux_*.bb
> recipes by default use defconfig as part of SRC_URI. But we can use
> empty file to satisfy it.

The defconfig-in-OE bit is there because the in-kernel ones are either

a) broken
b) lacking drivers for nearly everything

I suspect you'll be introducing a huge regression when it comes to 
things like uinput, netfilter, usb drivers, etc.

regards,

Koen




  parent reply	other threads:[~2009-08-12 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 18:55 Contents of the "origin/ulf/linux-2.6.30.2" branch. Help with testing wanted Ulf Samuelsson
2009-08-12 12:33 ` Marcin Juszkiewicz
2009-08-12 13:32   ` Ulf Samuelsson
2009-08-21 11:53     ` Marcin Juszkiewicz
2009-08-22  7:41       ` Ulf Samuelsson
2009-08-23 10:55         ` Marcin Juszkiewicz
2009-08-22 17:45       ` Ulf Samuelsson
2009-08-23 10:41         ` Marcin Juszkiewicz
2009-08-23 11:31           ` Ulf Samuelsson
2009-08-12 15:13   ` Koen Kooi [this message]
2009-08-12 15:56   ` Phil Blundell
2009-08-12 22:09     ` Ulf Samuelsson
2009-08-13  7:12       ` Koen Kooi
2009-08-13  7:10     ` Ulf Samuelsson
2009-08-13 17:34       ` Contents of the "origin/ulf/linux-2.6.30.2" branch. Status update Ulf Samuelsson

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='h5um7k$ioq$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.