Skip to contentSkip to conversation

ia32-base: Remove cpio and ext3 defaults

PATCH In review Richard Purdie 4 participants 4 messages Nov 21, 2013 – Nov 22, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ia32-base: Remove cpio and ext3 defaults

On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case.

When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases.

---

meta/conf/machine/include/ia32-base.inc +1 -1
index 8a20bca..e15f927 100644
@@ -10,7 +10,7 @@ MACHINE_FEATURES += "screen keyboard pci usbhost ext2 ext3 x86 \
 
 MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
 
-IMAGE_FSTYPES += "ext3 cpio.gz live"
+IMAGE_FSTYPES += "live"
 
 KERNEL_IMAGETYPE ?= "bzImage"
 
Acked-by Darren Hart on v1 1/1
#1 lore raw
Quoted 10 lines · Richard Purdie

On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case.

When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases.

I'm fine with this, although it raises the question if we ought to be doing anything more than tar rootfs in include files like this. there are ia32 machines where a live image is not useful (although rare). Most x86 BSPs would add live - but then again, most x86 BSPs will be starting to consolidate on the genericx86 BSPs anyway....

But, this is a clear improvement as is.

Quoted 16 lines

---

meta/conf/machine/include/ia32-base.inc +1 -1
index 8a20bca..e15f927 100644
@@ -10,7 +10,7 @@ MACHINE_FEATURES += "screen keyboard pci usbhost ext2 ext3 x86 \
 
 MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
 
-IMAGE_FSTYPES += "ext3 cpio.gz live"
+IMAGE_FSTYPES += "live"
 
 KERNEL_IMAGETYPE ?= "bzImage"
 
Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#2 lore raw
Quoted 10 lines · Richard Purdie
Quoted 9 lines

On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case.

When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases.

Quoted 7 lines
Quoted 1 line

I'm fine with this, although it raises the question if we ought to be doing anything more than tar rootfs in include files like this. there are ia32 machines where a live image is not useful (although rare). Most x86 BSPs would add live - but then again, most x86 BSPs will be starting to consolidate on the genericx86 BSPs anyway....

live image does not build in case of INCOMPATIBE_LICENSE = GPLv3

Holger

Quoted 32 lines

But, this is a clear improvement as is.

Review

Quoted 2 lines

---

(quoted diff) +0 -0

b/meta/conf/machine/include/ia32-base.inc

meta/conf/machine/include/ia32-base.inc MACHINE_FEATURES += "screen keyboard pci usbhost

Quoted 4 lines

index 8a20bca..e15f927 100644

meta/conf/machine/include/ia32-base.inc +0 -0
@@ -10,7 +10,7 @@ MACHINE_FEATURES += "screen keyboard pci usbhost

ext2 ext3 x86 \

meta/conf/machine/include/ia32-base.inc MACHINE_FEATURES += "screen keyboard pci usbhost ext2 ext3 x86 \

Quoted 10 lines
meta/conf/machine/include/ia32-base.inc +1 -1
 MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
 
-IMAGE_FSTYPES += "ext3 cpio.gz live"
+IMAGE_FSTYPES += "live"
 
 KERNEL_IMAGETYPE ?= "bzImage"
 
 

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#3 lore raw
Quoted 12 lines · Holger
Quoted 12 lines · Richard Purdie
Quoted 10 lines

On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case.

When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases.

Quoted 7 lines
Quoted 5 lines

I'm fine with this, although it raises the question if we ought to be doing anything more than tar rootfs in include files like this. there are ia32 machines where a live image is not useful (although rare). Most x86 BSPs would add live - but then again, most x86 BSPs will be starting to consolidate on the genericx86 BSPs anyway....

live image does not build in case of INCOMPATIBE_LICENSE = GPLv3

                                                ^^^?

is that just a mail list typo or a copy and paste error?

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================