On 12/11/2007 04:04 PM, Paul Sokolovsky wrote:
> any change to build configuration should be accompanied by recipe PR
> bump, so new kernel file will be produces.
How about an update of kernel patch? Do we have to bump the kernel
recipe PR as well?
Regards
Gordon
__
On 12/11/2007 12:46 PM, Graeme Gregory wrote:
> Sounds sensible to me as long as kernels are clearly labelled.
>
> Graeme
+1 from me for booting from SD on Tosa.
However, isn't this the altboot trying to achieve? Could somebody
comment on what's the key difference between the two methods?
Gord
This is a forwarded message
From: pfalcon commit <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Wednesday, December 12, 2007, 1:04:18 AM
Subject: [oe-commits] org.oe.dev angstrom-2007.1.conf: Use bluez 3.23.
===8<==Original message text===
angstrom-2007.1.conf: Use bluez 3
Hello openembedded-devel,
I already mentioned this in
http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-December/003695.html
, here's specific RFC:
I'd like to propose using the following filename pattern for deployed
kernel images: "${KERNEL_IMAGETYPE}-${PV}-${PR}-${MACHINE}", inste
On Tue, 11 Dec 2007 20:38:58 +0100
Koen Kooi <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Graeme Gregory schreef:
> > Sounds sensible to me as long as kernels are clearly labelled.
>
> I was thinking of something like:
>
> echo CMDLINE_VAR = "/dev/eleetroot"
Hello Dmitry,
Monday, December 10, 2007, 5:48:10 PM, you wrote:
> Hi,
> Currently I'm cleaning up the tosa keyboard stuff.
> I have two question:
> 1) What codes should I use for "misc" keys? Does the comment at
> include/linux/input_pda.h still apply to current kdrive? Or I can safely
use keyc
Hello Koen,
Tuesday, December 11, 2007, 7:56:59 PM, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> Hi,
> Would people be hugely offended if the autobuilder would start building
> extra kernels with different CMDLINEs?
> The general idea is that for some devices (e.g. c7x0) the i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graeme Gregory schreef:
> Sounds sensible to me as long as kernels are clearly labelled.
I was thinking of something like:
echo CMDLINE_VAR = "/dev/eleetroot" >> conf/auto.conf
bitbake virtual/kernel -c rebuild
mv $(readlink deploy/kernel-symlink) zi
Unless there's a way to vastly shrink down the X11 images for collie(5500),
it would make sense that the collie have the ability to boot to SD as the
native rootdevice. If I understand correctly, the poodle(5600) does this, so
it may not be entirely difficult to do for the collie as well.
--
Jaco
Sounds sensible to me as long as kernels are clearly labelled.
Graeme
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
On Dec 11, 2007 9:56 AM, Koen Kooi <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> Would people be hugely offended if the autobuilder would start building
> extra kernels with different CMDLINEs?
> The general idea is that for some devices (e.g. c7x0) the i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Would people be hugely offended if the autobuilder would start building
extra kernels with different CMDLINEs?
The general idea is that for some devices (e.g. c7x0) the installkit has
the default kernel + rootfs, and the download location has an
*
Hello there,
As some of you already know, I'm desperatly trying to get mipv6 working
on an Angstrom distro.
I've got openembedded updated to
"575e3741db66260805f359854a0513606534de50"
I'm using kernel 2.6.23 and MIPv6 2.0.2r0
I've tried to bitbake mipv6, but on configure stage it tells:
| confi
13 matches
Mail list logo
