1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
|
flash-kernel
------------
flash-kernel is a script which will put the kernel and initramfs in
the boot location of embedded devices that don't load the kernel and
initramfs directly from /boot. flash-kernel supports devices that
boot from flash memory (hence the name) as well as some devices that
require a special boot image on the disk.
Supported systems
- - - - - - - - -
The following systems are supported:
- Buffalo Linkstation Live
- Buffalo Linkstation Live, version 3 (LS-CHL)
- Buffalo Linkstation Mini
- Buffalo Linkstation Pro
- Buffalo/Revogear Kurobox Pro
- D-Link DNS-323
- Genesi Efika Nettop
- Genesi Efika Smartbook
- GLAN Tank
- GuruPlug
- HP t5325 Thin Client
- HP Media Vault mv2120
- Intel SS4000-E
- LaCie 2Big Network v2
- LaCie 5Big Network v2
- LaCie Internet Space v2
- LaCie Network Space v2
- LaCie Network Space Max v2
- LaCie d2 Network v2
- Linksys NSLU2
- Marvell DB-78x00-BP Development Board
- Marvell OpenRD-Base
- Marvell OpenRD-Client
- Marvell OpenRD-Ultimate
- Neo FreeRunner (GTA02)
- QNAP TS-109
- QNAP TS-110 Turbo NAS
- QNAP TS-119 Turbo NAS
- QNAP TS-209
- QNAP TS-210 Turbo NAS
- QNAP TS-219 and TS-219P Turbo NAS
- QNAP TS-409
- QNAP TS-410 and TS-410U Turbo NAS
- QNAP TS-419P and TS-419U Turbo NAS
- Seagate FreeAgent DockStar
- SheevaPlug
- SheevaPlug eSATA
- Thecus N2100
- Toshiba AC100
If you would like to see support for another device, please file a bug
report in the Debian Bug Tracking System and include all information
related to the boot process of your device. Instructions can be found
at http://bugs.debian.org/
Testsuite
- - - - -
Run the testsuite with:
FK_CHECKOUT=. ./test_flash-kernel
FK_CHECKOUT=. ./test_functions
You need the devscripts package for the checkbashisms test.
Database format
- - - - - - - -
To accomodate the differences between machines, db/*.db files contain
information on supported machines. The files look somewhat like
RFC 2822 data or Debian control data, i.e. header: value pairs,
with definitions separated by an empty line. Comments starting with a
pound are ignored.
The supported fields are:
* Machine: (required) value of the "Hardware:" line in /proc/cpuinfo and
is used as an unique identifier
* Kernel-Flavors: (optional) allowed flavors (suffixes) for the to be
installed kernel; if the vmlinuz file doesn't end with a listed
suffix, installation is aborted
* Machine-Id: (optional) linux mach-type to set before starting vmlinuz;
will be set by a small piece of ARM code prepended to the kernel image
* DTB-Id: (optional) specifies the name of the DTB file for this device
* DTB-Append: (optional) when yes the DTB specified by DTB-Id will be appended
to the kernel image.
* U-Boot-Kernel-Address, U-Boot-Initrd-Address: (optional) address where
to load in (physical) RAM the kernel and initrd, respectively; this
also indicates that U-Boot images should be generated with mkimage
* U-Boot-Script-Address: (optional) like U-Boot-Kernel-Address and
U-Boot-Initrd-Address but for an U-Boot boot script; see also
U-Boot-Script-Name
* U-Boot-Script-Name: (optional) name of U-Boot boot script to install
from the flash-kernel files
* Boot-Kernel-Path, Boot-Initrd-Path: (optional) where to put the
generated kernel and initrd files on the filesystem; see also
Boot-Device
* Boot-Script-Path: (optional) like Boot-Kernel-Path and
Boot-Initrd-Path but for an U-Boot boot script; see also
U-Boot-Script-Name and Boot-Device
* Boot-DTB-Path: (optional) like Boot-Kernel-Path and Boot-Initrd-Path
but for a DTB file. The DTB file named by DTB-Id will be copied
here; see also DTB-Id
* Required-Packages: (optional) list of packages which must be added
during installer phase for flash-kernel to work properly; failure to
add these packages aborts the installation
* Optional-Packages: (optional) list of packages which should be
added during installer pharse for flash-kernel to offer full
functionality; failure to add these packages just triggers a warning
* Bootloader-sets-root: (required) when "yes" indicates that the
bootloader passes a root= value to the kernel and that this should be
overriden in the initrd; when "no", flash-kernel only sets a default
value for the root device, which allows end-users to pass root= to
the kernel
* Method: (optional) indicates how to support this particular machine;
the default is "generic"; other available methods are: android, multi,
redboot, slug, symlink
* Boot-Device: (optional) block device to mount before installing
kernel, initrd and U-Boot script; Boot-Kernel-Path, Boot-Initrd-Path and
Boot-Script-Path are then taken relative to this boot device
|
