[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Lennart Ramberg]

Hi,
I am struggling with making a grub 2-bootable Compact Flash for a BIOS
based PC target.
The closest I came so far in the target machine is:
  grub rescue >

Then I found 'grub-bios-setup' as a possibly better alternative, but got
stuck as below.
Is grub-bios-setup the way to go at all?
Thanks
Lennart

I'm using the stable buildroot-2014.05.
After make menuconfig and make my output/images/ contain
  bzImage
  grub.img
  rootfs.ext2
  rootfs.ext3 link
  rootfs.tar

and what I have done is: (Target CF put in the host in an USB CF-adapter,
sdX=sdc in my case.)
sudo fdisk /dev/sdX    and created one primary partition 1GB.
sudo mke2fs -j -m 0 /dev/sdX1
sudo tune2fs -c0 -i0 /dev/sdX1

sudo tar -xvf output/images/rootfs.tar -C
/media/lennart/30bdb69e-d518-4a8c-8b12-70fe8481dae7/
sudo grub-install /dev/sdX
Installation finished. No error reported.

Putting that in the target machine only brought me to 'grub rescue >', so I
tried grub-bios-setup, but got stuck on 'device.map':

lennart at OptiPlex ~/buildroot-2014.05 $
./output/host/usr/sbin/grub-bios-setup -b
./output/host/usr/lib/grub/i386-pc/boot.img -c ./output/images/grub.img -d
. /dev/sdc -v
./output/host/usr/sbin/grub-bios-setup: info: cannot open
`/boot/grub/device.map': No such file or directory.
./output/host/usr/sbin/grub-bios-setup: info: Looking for /dev/sdc.
./output/host/usr/sbin/grub-bios-setup: info: /dev/sdc is a parent of
/dev/sdc.
./output/host/usr/sbin/grub-bios-setup: info: Looking for /dev/sdc.
./output/host/usr/sbin/grub-bios-setup: info: /dev/sdc is a parent of
/dev/sdc.
./output/host/usr/sbin/grub-bios-setup: info: transformed OS device
`/dev/sdc' into GRUB device `hostdisk//dev/sdc'.
./output/host/usr/sbin/grub-bios-setup: info: getting the size of
././output/host/usr/lib/grub/i386-pc/boot.img.
./output/host/usr/sbin/grub-bios-setup: info: reading
././output/host/usr/lib/grub/i386-pc/boot.img.
./output/host/usr/sbin/grub-bios-setup: info: getting the size of
././output/host/usr/lib/grub/i386-pc/boot.img.
./output/host/usr/sbin/grub-bios-setup: info: getting the size of
././output/images/grub.img.
./output/host/usr/sbin/grub-bios-setup: info: reading
././output/images/grub.img.
./output/host/usr/sbin/grub-bios-setup: info: getting the size of
././output/images/grub.img.
./output/host/usr/sbin/grub-bios-setup: info: root is `(null)', dest is
`hostdisk//dev/sdc'.
./output/host/usr/sbin/grub-bios-setup: info: Opening dest.
./output/host/usr/sbin/grub-bios-setup: error: disk `hostdisk//dev/sdc' not
found.
lennart at OptiPlex ~/buildroot-2014.05 $
---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140627/408f629d/attachment.html>

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Thomas Petazzoni]

Dear Lennart Ramberg,

On Fri, 27 Jun 2014 12:32:03 +0200, Lennart Ramberg wrote:

> I am struggling with making a grub 2-bootable Compact Flash for a BIOS
> based PC target.
> The closest I came so far in the target machine is:
>   grub rescue >
> 
> Then I found 'grub-bios-setup' as a possibly better alternative, but got
> stuck as below.
> Is grub-bios-setup the way to go at all?

Have you checked the detailed instructions available in the help text
of the grub2 package (accessible through xconfig/menuconfig) ? From the
help text:

          Notes on using Grub2 for BIOS-based platforms
          =============================================

          1. Create a disk image
             dd if=/dev/zero of=disk.img bs=1M count=32
          2. Partition it (either legacy or GPT style partitions work)
             cfdisk disk.img
              - Create one partition, type Linux, for the root
                filesystem. The only constraint is to make sure there
                is enough free space *before* the first partition to
                store Grub2. Leaving 1 MB of free space is safe.
          3. Setup loop device and loop partitions
             sudo losetup -f disk.img
             sudo partx -a disk.img
          4. Prepare the root partition
             sudo mkfs.ext3 -L root /dev/loop0p1
             sudo mount /dev/loop0p1 /mnt
             sudo tar -C /mnt -xf output/images/rootfs.tar
             sudo umount /mnt
          5. Install Grub2
             ./output/host/usr/sbin/grub-bios-setup \
                        -b ./output/host/usr/lib/grub/i386-pc/boot.img \
                        -c ./output/images/grub.img -d . /dev/loop0
          6. Your disk.img is ready!

Of course, this help text is about creating a disk image, but it should
apply (with minor changes) to a real device.

Let me know if that works for you!

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Lennart Ramberg]

Thank you Thomas,

It helped to use sudo :-)
to get rid of that annoying
"cannot open `/boot/grub/device.map': No such file or directory."

Now, putting the thus created CF in the target system brings me (only) to:
grub>

Should I expect to automatically have come further?

--Details:---
I had disabled 'Run getty login prompt after boot'.
I selected to 'Install kernel image to /boot in target'.
So, my /boot contains only the directory grub and bzImage.
and /boot/grub contains only grub.cfg, which looks like:

grub.cfg:
set default="0"
set timeout="5"

menuentry "Buildroot" {
    linux /bzImage root=/dev/sda1 console=tty1
}
--End Details.-----

Regards
Lennart



On Fri, Jun 27, 2014 at 8:32 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Lennart Ramberg,
>
> On Fri, 27 Jun 2014 12:32:03 +0200, Lennart Ramberg wrote:
>
> > I am struggling with making a grub 2-bootable Compact Flash for a BIOS
> > based PC target.
> > The closest I came so far in the target machine is:
> >   grub rescue >
> >
> > Then I found 'grub-bios-setup' as a possibly better alternative, but got
> > stuck as below.
> > Is grub-bios-setup the way to go at all?
>
> Have you checked the detailed instructions available in the help text
> of the grub2 package (accessible through xconfig/menuconfig) ? From the
> help text:
>
>           Notes on using Grub2 for BIOS-based platforms
>           =============================================
>
>           1. Create a disk image
>              dd if=/dev/zero of=disk.img bs=1M count=32
>           2. Partition it (either legacy or GPT style partitions work)
>              cfdisk disk.img
>               - Create one partition, type Linux, for the root
>                 filesystem. The only constraint is to make sure there
>                 is enough free space *before* the first partition to
>                 store Grub2. Leaving 1 MB of free space is safe.
>           3. Setup loop device and loop partitions
>              sudo losetup -f disk.img
>              sudo partx -a disk.img
>           4. Prepare the root partition
>              sudo mkfs.ext3 -L root /dev/loop0p1
>              sudo mount /dev/loop0p1 /mnt
>              sudo tar -C /mnt -xf output/images/rootfs.tar
>              sudo umount /mnt
>           5. Install Grub2
>              ./output/host/usr/sbin/grub-bios-setup \
>                         -b ./output/host/usr/lib/grub/i386-pc/boot.img \
>                         -c ./output/images/grub.img -d . /dev/loop0
>           6. Your disk.img is ready!
>
> Of course, this help text is about creating a disk image, but it should
> apply (with minor changes) to a real device.
>
> Let me know if that works for you!
>
> Best regards,
>
> Thomas Petazzoni
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140630/80da00f0/attachment.html>

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Thomas Petazzoni]

Dear Lennart Ramberg,

On Mon, 30 Jun 2014 10:23:06 +0200, Lennart Ramberg wrote:

> Thank you Thomas,
> 
> It helped to use sudo :-)
> to get rid of that annoying
> "cannot open `/boot/grub/device.map': No such file or directory."
> 
> Now, putting the thus created CF in the target system brings me (only) to:
> grub>
> 
> Should I expect to automatically have come further?

Yes, it should show the menu thanks to the configuration file. What
exact steps have you followed to put the root filesystem and Grub on
your Compact Flash?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Lennart Ramberg]

Hi Thomas,

On Mon, Jun 30, 2014 at 11:49 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Lennart Ramberg,
>
> On Mon, 30 Jun 2014 10:23:06 +0200, Lennart Ramberg wrote:
>
> > Thank you Thomas,
> >
> > It helped to use sudo :-)
> > to get rid of that annoying
> > "cannot open `/boot/grub/device.map': No such file or directory."
> >
> > Now, putting the thus created CF in the target system brings me (only)
> to:
> > grub>
> >
> > Should I expect to automatically have come further?
>
> Yes, it should show the menu thanks to the configuration file. What
> exact steps have you followed to put the root filesystem and Grub on
> your Compact Flash?
>
>
>
Below I detail out what I did.
I also attach my .config (dotconfig) that resulted from my actions
described below.

I hope the below could be of use.

Regards
Lennart

On my host, LinuxMint16 dmesg tells me that my 1 GB CF (in a USB-CF
adapter) is /dev/sdc.

lennart at OptiPlex ~/buildroot-2014.05 $ sudo dd if=/dev/zero of=/dev/sdc
bs=1M count=32
lennart at OptiPlex ~/buildroot-2014.05 $ sudo fdisk /dev/sdc
(n, p, 1, 2048, 2001887, a, 1, w)
lennart at OptiPlex ~/buildroot-2014.05 $ sudo partprobe /dev/sdc
-------------------------------------------------------------
Thus:
lennart at OptiPlex ~ $ sudo fdisk /dev/sdc

Command (m for help): p

Disk /dev/sdc: 1024 MB, 1024966656 bytes
1 heads, 32 sectors/track, 62559 cylinders, total 2001888 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xae6de628

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048     2001887      999920   83  Linux

Command (m for help): q
-------------------------------------------------------------
lennart at OptiPlex ~/buildroot-2014.05 $ sudo umount /dev/sdc1
lennart at OptiPlex ~/buildroot-2014.05 $ sudo mkfs.ext3 -L root /dev/sdc1
lennart at OptiPlex ~/buildroot-2014.05 $ sudo mount /dev/sdc1 /mnt
lennart at OptiPlex ~/buildroot-2014.05 $ make distclean
lennart at OptiPlex ~/buildroot-2014.05 $ make menuconfig
Defaults, except as follows:

Target options:
Target Architecture (i386), Target Architecture Variant: i686

Build options:
[*] Enable compiler cache

Toolchain:
C library, (X) glibc

System configuration:
[ ] Run a getty (login prompt) after boot

Kernel:
[*] Linux Kernel
    Kernel version (3.14.4)
(i386) Defconfig name
[*]   Install kernel image to /boot in target

Target packages:
  Graphic libraries and applications (graphic/text):
     [*] X.org X Window System

  Libraries:
     Database: [*] sqlite
     Graphics: [*] cairo:     [*] png support
               [*] jpeg support
     Networking: [*] libcurl

  Text editors and viewers:
    [*] nano
      [ ]  optimize for size

Filesystem images:
    [*] ext2/3/4 root filesystem:   ext2/3/4 variant (ext3)
    (1000000) size in blocks (leave at 0 for auto calculation)

    [*] initial RAM filesystem linked into linux kernel

Bootloaders:
   [*] grub2

< Save >
...
lennart at OptiPlex ~/buildroot-2014.05 $ make
lennart at OptiPlex ~/buildroot-2014.05 $ sudo tar -C /mnt -xf
output/images/rootfs.tar
lennart at OptiPlex ~/buildroot-2014.05 $ sudo umount /mnt
lennart at OptiPlex ~/buildroot-2014.05 $ sudo
./output/host/usr/sbin/grub-bios-setup -b
./output/host/usr/lib/grub/i386-pc/boot.img -c ./output/images/grub.img -d
. /dev/sdc -v
...
./output/host/usr/sbin/grub-bios-setup: info: Scanning for dmraid_nv
devices on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for ldm devices on
disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: scanning hostdisk//dev/sda
for LDM.
./output/host/usr/sbin/grub-bios-setup: info: no LDM signature found.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for lvm devices on
disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: no LVM signature found.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for DISKFILTER
devices on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for mdraid1x devices
on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for mdraid09 devices
on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for mdraid09_be
devices on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for dmraid_nv
devices on disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for ldm devices on
disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: scanning hostdisk//dev/sda
for LDM.
./output/host/usr/sbin/grub-bios-setup: info: no LDM signature found.
./output/host/usr/sbin/grub-bios-setup: info: Scanning for lvm devices on
disk hostdisk//dev/sda.
./output/host/usr/sbin/grub-bios-setup: info: no LVM signature found.
./output/host/usr/sbin/grub-bios-setup: info: Partition 0 starts from 2048.
./output/host/usr/sbin/grub-bios-setup: info: Partition 4 starts from
480159744.
./output/host/usr/sbin/grub-bios-setup: info: Partition 5 starts from
116279296.
./output/host/usr/sbin/grub-bios-setup: info: the size of hostdisk//dev/sda
is 488281250.
./output/host/usr/sbin/grub-bios-setup: info: guessed root_dev
`hostdisk//dev/sda' from dir `.'.
./output/host/usr/sbin/grub-bios-setup: info: setting the root device to
`hostdisk//dev/sda,msdos6'.
./output/host/usr/sbin/grub-bios-setup: info: the first sector is <1,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <2,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <3,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <4,0,512>.
...
./output/host/usr/sbin/grub-bios-setup: info: saving <470,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <471,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <472,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <473,0,512>.
./output/host/usr/sbin/grub-bios-setup: info: saving <474,0,512>.
lennart at OptiPlex ~/buildroot-2014.05 $

Ready to test. Rebooted my PC with CF still in place gives just:
GNU GRUB version 2.00
blablabla
grub>

--- end ---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140630/18251a09/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dotconfig
Type: application/octet-stream
Size: 49940 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140630/18251a09/attachment-0001.obj>

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Thomas Petazzoni]

Dear Lennart Ramberg,

On Mon, 30 Jun 2014 21:53:32 +0200, Lennart Ramberg wrote:

> Below I detail out what I did.
> I also attach my .config (dotconfig) that resulted from my actions
> described below.
> 
> I hope the below could be of use.

[... snip lots of details ...]

> Ready to test. Rebooted my PC with CF still in place gives just:
> GNU GRUB version 2.00
> blablabla
> grub>
> 
> --- end ---

Thanks for this very detailed report. I'm able to reproduce the issue
now under Qemu. It's weird, I'm 100% sure I tested this when I
contributed the grub2 support. I'll have to investigate to find where
the problem lies.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] grub2: Specify boot partition

[Jérôme Pouiller]

Since boot partition was not specified, grub tools try to detect it
automatically. This patch add an option to force it.

Notice I am not sure -p option is usefull when -c option is used.

Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
---
 boot/grub2/Config.in | 5 +++++
 boot/grub2/grub2.mk  | 4 +++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/boot/grub2/Config.in b/boot/grub2/Config.in
index b37e024..0ebb3a0 100644
--- a/boot/grub2/Config.in
+++ b/boot/grub2/Config.in
@@ -111,6 +111,11 @@ config BR2_TARGET_GRUB2_X86_64_EFI
 
 endchoice
 
+config BR2_TARGET_GRUB2_BOOT_PARTITION
+	string "boot partition"
+	default "(hd0,msdos1)"
+	  Specifiy partition where /boot/grub/grub.cfg will be located.
+
 config BR2_TARGET_GRUB2_BUILTIN_MODULES
 	string "builtin modules"
 	default "boot linux ext2 fat part_msdos part_gpt normal biosdisk" if BR2_TARGET_GRUB2_I386_PC
diff --git a/boot/grub2/grub2.mk b/boot/grub2/grub2.mk
index 50f93ee..ab2b122 100644
--- a/boot/grub2/grub2.mk
+++ b/boot/grub2/grub2.mk
@@ -14,6 +14,7 @@ GRUB2_DEPENDENCIES = host-bison host-flex
 ifeq ($(BR2_TARGET_GRUB2_I386_PC),y)
 GRUB2_IMAGE = $(BINARIES_DIR)/grub.img
 GRUB2_CFG = $(TARGET_DIR)/boot/grub/grub.cfg
+GRUB2_PREFIX = /boot/grub
 GRUB2_TUPLE = i386-pc
 GRUB2_TARGET = i386
 GRUB2_PLATFORM = pc
@@ -35,6 +36,7 @@ endif
 
 GRUB2_BUILTIN_MODULES = $(call qstrip,$(BR2_TARGET_GRUB2_BUILTIN_MODULES))
 GRUB2_BUILTIN_CONFIG = $(call qstrip,$(BR2_TARGET_GRUB2_BUILTIN_CONFIG))
+GRUB2_BOOT_PARTITION = $(call qstrip,$(BR2_TARGET_GRUB2_BOOT_PARTITION))
 
 # Grub2 is kind of special: it considers CC, LD and so on to be the
 # tools to build the native tools (i.e to be executed on the build
@@ -71,7 +73,7 @@ define GRUB2_IMAGE_INSTALLATION
 		-d $(HOST_DIR)/usr/lib/grub/$(GRUB2_TUPLE) \
 		-O $(GRUB2_TUPLE) \
 		-o $(GRUB2_IMAGE) \
-		$(if $(GRUB2_PREFIX),-p $(GRUB2_PREFIX)) \
+		-p $(GRUB2_BOOT_PARTITION)$(GRUB2_PREFIX) \
 		$(if $(GRUB2_BUILTIN_CONFIG),-c $(GRUB2_BUILTIN_CONFIG)) \
 		$(GRUB2_BUILTIN_MODULES)
 	mkdir -p $(dir $(GRUB2_CFG))
-- 
2.0.0

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Jérôme Pouiller]

Hello Lennart,

On Monday 30 June 2014 10:23:06 Lennart Ramberg wrote:
> Thank you Thomas,
> 
> It helped to use sudo :-)
> to get rid of that annoying
> "cannot open `/boot/grub/device.map': No such file or directory."
Can you try patch that follows this mail (called "grub2: Specify boot 
partition")? Does it solve your issue?

[...]

-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

[Buildroot] [PATCH] grub2: Specify boot partition

[Thomas Petazzoni]

Dear J?r?me Pouiller,

On Tue,  1 Jul 2014 10:44:49 +0200, J?r?me Pouiller wrote:
> Since boot partition was not specified, grub tools try to detect it
> automatically. This patch add an option to force it.
> 
> Notice I am not sure -p option is usefull when -c option is used.

This should not be part of the commit log. If you want to express such
comments, they should go...

> 
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
> ---

... here.

Indeed, when the configuration is built into the image, I don't think
the prefix is very useful. But I believe that's OK.

> +config BR2_TARGET_GRUB2_BOOT_PARTITION
> +	string "boot partition"
> +	default "(hd0,msdos1)"

	depends on BR2_TARGET_GRUB2_I386_PC

since there is no need to specify a boot partition for the EFI boot
cases.

> +	  Specifiy partition where /boot/grub/grub.cfg will be located.

Fix that with:

	Specify the partition where the /boot/grub/grub.cfg is located.
	Use (hd0,msdos1) for the first partition of the first disk if
	using a legacy partition table, or (hd0,gpt1) if using GPT
	partition table.

Other than that, looks OK. Can you quickly resend a v2 ?

Thanks a lot for looking into this problem!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Lennart Ramberg]

On Tue, Jul 1, 2014 at 10:49 AM, J?r?me Pouiller <jezz@sysmic.org> wrote:

> Hello Lennart,
> ...
> Can you try patch that follows this mail (called "grub2: Specify boot
> partition")? Does it solve your issue?
>
> Hi Thomas & J?r?me,

Thanks for your quick reactions to my complaint.
I regret to say though, that I can't test any patch until I have found a
'Patching for .. eh.. dummies', or similar.
I.e. I have not yet learned how to apply a patch :-(

Regards
Lennart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140701/913c3142/attachment.html>

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Jérôme Pouiller]

Hello Lennart,

On Tuesday 01 July 2014 21:32:08 Lennart Ramberg wrote:
> On Tue, Jul 1, 2014 at 10:49 AM, J?r?me Pouiller <jezz@sysmic.org> wrote:
> > Hello Lennart,
> > ...
> > Can you try patch that follows this mail (called "grub2: Specify boot
> > partition")? Does it solve your issue?
> > 
> > Hi Thomas & J?r?me,
> 
> Thanks for your quick reactions to my complaint.
> I regret to say though, that I can't test any patch until I have found a
> 'Patching for .. eh.. dummies', or similar.
> I.e. I have not yet learned how to apply a patch :-(
If you use git, save mail containing patch as a file and use 

  git am PATH_TO_SAVED_MAIL_CONTAINING_PATCH


-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

[Buildroot] Is grub-bios-setup the way to go to make a bootable CF?

[Thomas Petazzoni]

J?r?me, Lennart,

On Tue, 01 Jul 2014 21:56:19 +0200, J?r?me Pouiller wrote:

> > Thanks for your quick reactions to my complaint.
> > I regret to say though, that I can't test any patch until I have found a
> > 'Patching for .. eh.. dummies', or similar.
> > I.e. I have not yet learned how to apply a patch :-(
> If you use git, save mail containing patch as a file and use 
> 
>   git am PATH_TO_SAVED_MAIL_CONTAINING_PATCH

Or, to apply directly J?r?me's patch from the Buildroot patchwork:

 cd buildroot/
 curl http://patchwork.ozlabs.org/patch/366158/mbox/ | git am

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com