Action Item #235

PiBox component rev: Buildroot

Added by Hammel about 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:17 Oct 2013
Priority:ImmediateDue date:
Assignee:Hammel% Done:

100%

Category:04 - Root File System
Target version:0.8.0
Severity:01 - Critical

Description

The default buildroot version is aging: 2013.02. The latest version is 2013.08.1. This needs to be tested to see if it will provide a correct build image for PiBox.

Updated: 2013.02/1.20.2 (Buildroot/Busybox version) was rev'd to 2013.11/1.21.1 in 2014-01. Now awaiting official Buildroot 2014.02 release.

Associated revisions

Revision c2f54908
Added by Hammel over 3 years ago

RM #235: Add support for building Buildroot 2013.11. This is not the default yet, however.

Revision 33a4ab8d
Added by Hammel over 3 years ago

RM #235: Bump Buildroot to 2013.11 as the default build.

Revision d5712c91
Added by Hammel over 3 years ago

RM #235: Bump Busybox to 1.21.1 in Buildroot 2013.11

Revision a43d7a3f
Added by Hammel over 3 years ago

RM #235, RM #269: Bump Busybox to 1.21.1, with mktemp added.

Revision 79b58a34
Added by Hammel over 3 years ago

RM #235: Add blkid with filesystem type support.

History

#1 Updated by Hammel about 4 years ago

  • % Done changed from 0 to 10

Buildroot 2013.08.1 has been tested with the build on Fedora 19 and appears to build correctly. It's test exposed a problem with the XBMC package provided by PiBox (which provides components necessary to run the XBMCbox opkg) but this is not related to the suitability of 2013.08.1 for use with PiBox.

The build is being tested on CentOS. After that the build image will be tested on the hardware. If those tests succeed then 2013.08.1 will become the default version of Buildroot for PiBox.

#2 Updated by Hammel about 4 years ago

  • % Done changed from 10 to 60

CentOS 6.4 build completed successfully. Fedora build works but I haven't had a complete build run without an issue. Most seem to be due to poor wireless connectivity.

New images need to be tested on hardware.

#3 Updated by Hammel over 3 years ago

  • % Done changed from 60 to 70

Ported packages and patches to 2013.11. Build completed and tested under the current xcc and kernel. Seems to work fine. I've made it the default.

Busybox needs to be rev'd to the latest in order to make sure mdev has all support possible for kernel 3.5.x+ (post-USBFS). Unfortunately Buildroot 2011.13 doesn't have support for latest Busybox (1.22.0). But support is in mainline. So I can pull patches for it now and then do another rev when 2014.02 comes out, which should be very soon. Or I can just procrastinate and wait for 2014.02.

#4 Updated by Hammel over 3 years ago

  • Priority changed from Low to Immediate
  • Target version changed from 1.0 - Atreides to 0.8.0
  • Severity changed from 04 - Low to 01 - Critical

Since there doesn't appear to be any down side to this, the bump to Buildroot 2014.02 and Busybox 1.22.x will be part of the 0.8.0 release.

#5 Updated by Hammel over 3 years ago

Just realized there are no patches for 1.22.x in Buildroot mainline. So I would need to add a patch to the Busybox package to add support for 1.22.x. Alternatively I could just use the daily snapshot. But I would need to make a config update for snapshot use in Buildroot.

#6 Updated by Hammel over 3 years ago

Building with Busybox 1.21.1. Will test this and, if working as well as 1.20.1 or better, bump to that release while waiting for Buildroot 2014.02.

#7 Updated by Hammel over 3 years ago

Bumped Busybox to 1.21.1, which is the latest possible from Buildroot 2013.11.

Test built and pushed to target. Seems to work fine. Changes pushed upstream.

#8 Updated by Hammel over 3 years ago

  • Description updated (diff)

#9 Updated by Hammel over 3 years ago

  • % Done changed from 70 to 80

1.21.1 mdev broke blockhandler.sh - see RM #271.

#10 Updated by Hammel over 3 years ago

  • % Done changed from 80 to 90

Added missing blkid to Busybox. This was originally in Buildroot 2013.02 but was pulled from 2013.11. Adding it into Busybox was easy but you have to specifically ask for filesystem type support.

This fixes finding and mounting mmcblk0p1 by mdev. However, it blockhandler.sh no longer mounts sda1 when the usb stick is inserted. So I still need to fix that in RM #271 before closing this issue.

#11 Updated by Hammel over 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

blockhandler fixed for 2013.11. Closing issue for rev 0.8.0.

Also available in: Atom PDF