On 2015-01-01, Karsten Merker wrote:
> +++ b/build/boot/README.concatenateable_images
...
> +To create a complete image from the two parts on Linux systems, you can
> +use zcat (for .gz images), bzcat (for .bz2 images) or xzcat (for .xz
> +images) as follows:
> +
> + zcat firmware..img.gz partitio
On Thu, Jan 01, 2015 at 03:58:44PM +0100, Karsten Merker wrote:
> ---
> build/boot/README.concatenateable_images | 30 ++
> build/config/armhf/hd-media.cfg | 44
> +++-
> debian/changelog | 1 +
> 3 files changed, 7
Following is version 3 of my patchset for building bootable d-i
images for armhf targets.
Changes since V2
- add distinct debian/changelog entries to each commit
- add the "-n" flag to the gzip invocations in gen-hd-image to make
reproducible builds easier
- add copyright inf
---
build/boot/arm/bootscr.tftpboot | 21 +
build/config/armhf/netboot.cfg | 69 -
debian/changelog| 2 ++
3 files changed, 91 insertions(+), 1 deletion(-)
create mode 100644 build/boot/arm/bootscr.tftpboot
diff --git a/build/
---
build/boot/README.concatenateable_images | 30 ++
build/config/armhf/hd-media.cfg | 44 +++-
debian/changelog | 1 +
3 files changed, 74 insertions(+), 1 deletion(-)
create mode 100644 build/boot/README.concaten
Most systems encode the console baudrate in the ${console} variable, but
several i.MX6-based systems do not. As ${console} gets passed to the kernel,
we need to explicitly add the baudrate on i.MX6-based systems to avoid
a baudrate mismatch between u-boot and kernel.
---
build/boot/arm/bootscr.mai
The file boot/arm/u-boot-image-config contains the information
which u-boot components must be written to which offsets on the
disk to create a bootable image for various arm-based systems.
---
build/boot/arm/u-boot-image-config | 21 +
debian/changelog | 2 +
---
build/config/armhf.cfg| 2 +-
build/config/armhf/u-boot.cfg | 27 +++
debian/changelog | 1 +
3 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 build/config/armhf/u-boot.cfg
diff --git a/build/config/armhf.cfg b/build/config/ar
gen-hd-image creates partitioned harddisk images from a directory
tree and optionally installs a bootloader into the image. Supported
target filesystems are fat16, fat32 and ext2.
Its main use is building bootable images for armhf/armel/arm64
systems which use u-boot as their system firmware. U-b
Hello,
I just write to signal a systematic crash while booting the wheezy's and
jessie's installer.
Each time I try to boot on my machine with a USB stick for installation of
Debian, It crashes just after "Probing EDD (edd=off to disable) ... ok"
I tried in expert mode, the only thing it changes i
10 matches
Mail list logo