summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2013-11-08setup-gummitoot-conf: handle commented-out default entriesHEADtizen_3.0.m14.2_ivi_releasesubmit/tizen_ivi_stable/20131119.035428submit/tizen_ivi_stable/20131119.033328submit/tizen_ivi_panda/20140403.012230submit/tizen/20131108.115107accepted/tizen_ivi_stable/20131119.040312accepted/tizen/ivi/panda/20140403.015816accepted/tizen/20131111.231301accepted/tizen/20131108.201436tizen_ivi_pandatizen_3.0.m14.2_ivitizenaccepted/tizen_ivi_pandaaccepted/tizen_iviaccepted/tizen/iviArtem Bityutskiy1-2/+2
The 'setup-gummiboot-conf' script does not handle commented-out default entreis ("# default"). The reason is that the corresponding regexp was incorrect, because it did not searh from the beginning of the line, because of missing "^" symbol. This patch fixes the problem. Change-Id: I0bc8cd92bba127fcbea3908046c3bc209fbf02d1 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-11-07packaging: release out (non-existing kernels handling)submit/tizen/20131107.132544accepted/tizen/20131107.180534Artem Bityutskiy2-1/+5
Change-Id: I8e6f9b451307a14281c73b48b6eda92c4be23405 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-11-07setup-gummiboot-conf: fix non-existing kernels handlingArtem Bityutskiy1-5/+7
This patch is a bug-fix and it fixes the case when the default entry in 'loader.conf' does not actually exist in 'loader/entries'. Instead of failing, we should just find the newest existing version of the kernel. Change-Id: I61e169f37b5487b8abd6188a771f37f2f08ab328 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-11-07packaging: release out (no .conf suffix)submit/tizen/20131107.070245Artem Bityutskiy2-1/+6
Change-Id: I446da12022d6762acf0c87c382684a9836ff81c8 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-11-07setup-gummiboot-conf: fix the default entry name (again)Artem Bityutskiy1-1/+1
The default entry on loader.conf should _not_ contain the ".conf" suffix. This patch fixes 'setup-gummiboot-conf' correspondingly. Change-Id: If07685002f0025354f5f474e65c0730fdb23af24 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-10-11packaging: release out (correct loader.conf)submit/tizen/20131011.141814accepted/tizen/20131011.172934Artem Bityutskiy2-1/+6
Change-Id: I3149033a6680bc15206645c0e3315fa9b16b13df Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-10-11Fix the default entry nameArtem Bityutskiy2-2/+2
The default entry on loader.conf should _not_ contain the ".conf" suffix, so let's remove it. Amend the 'setup-gummiboot-conf' file accordingly. Change-Id: I25717a17e65e1c7c854a32651c344987f23a76dd Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-09-30packaging: release outsubmit/tizen/20130930.055640accepted/tizen/20130930.163554Artem Bityutskiy1-0/+3
Change-Id: I6f93fca567adaa5436a38bca1a4a9fb415e73bcf Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-09-25setup-efi-ivi: minor spelling fixes in commentssubmit/tizen/20130930.055400Artem Bityutskiy1-2/+2
Change-Id: I1ea5c767a6979e8b14fabb0c408b243e390eabeb Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-09-25setup-efi-ivi: a minor bug-fixArtem Bityutskiy1-1/+1
The 'kernels' variable is supposed to contain a list of kernels, but it actually only contains the latest kernel. This is not a problem since so fare we only use this script when there is only one kernel, but nevertheless, worth fixing. Change-Id: I1dea6cc09de20dd0fae21a9eebd614f6fdb50549 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-09-25setup-efi-ivi: always use the mount prefix variableArtem Bityutskiy1-10/+12
Installer framework exports the INSTALLERFW_MOUNT_PREFIX varable which basically tells what is the root directory for the system image. Usually this is just "/". But it may be something else too, for example, when we install the system to a different disk, all the disk partitions will be temporarily mounted somewhere like /mnt/install_disk/, and this will be the mount prefix. So, the problem is that we did not use the mount prefix for searching for gummiboot. It is really expected to be present on the target system/environment, not in the system/environment we are currently running. This patch fixes the issue. Change-Id: Ic414087fcac454109b8c50aa01643a00886bcb8c Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-08-01packaging: release out (fix x64 path)submit/tizen_ivi_release/20131120.032744submit/tizen_ivi_milestone/20131113.054520submit/tizen_ivi_genivi/20140131.070648submit/tizen_ivi_generic/20140131.065504submit/tizen/20130801.103707ivi_oct_m2accepted/tizen_ivi_release/20131120.050005accepted/tizen/ivi/genivi/20140131.070856accepted/tizen/20130801.171426tizen_ivi_releasetizen_ivi_geniviArtem Bityutskiy2-1/+4
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-07-31Merge "fix 64bit efi bootloader path" into tizenArtem Bityutskiy1-1/+1
2013-07-30setup-gummiboot-conf: fix the scriptsubmit/tizen/20130730.133812accepted/tizen/20130730.200410Artem Bityutskiy1-37/+0
The script does not really work and fails when it is run in Tizen OS. The reason is that some functions it calls are udnefined. And the reason for that is that I forgot to remove some debugging cruft, and the leftovers cause breakages. Remove that unused junk. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-07-29fix 64bit efi bootloader pathWilliam Douglas1-1/+1
Signed-off-by: William Douglas <william.douglas@intel.com>
2013-06-26setup-gummiboot-conf: remove junk newlinesubmit/tizen/20130626.130844accepted/tizen/20130626.173122Artem Bityutskiy1-1/+1
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: add a missing white-space in loader.confArtem Bityutskiy2-1/+38
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-gummiboot-conf: use INSTALLERFW_MOUNT_PREFIXArtem Bityutskiy1-5/+15
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: use less hard-codingArtem Bityutskiy1-11/+5
We do require that the boot partition is under /boot. But let's do it in less places. Once we know the boot partition number (N), use the INSTALLERFW_PARTN_MOUNTPOINT instead. Also, remove the vfat type checking - it is an unneeded complication. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-gummiboot-conf: improve commentariesArtem Bityutskiy1-13/+13
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26packaging: release out (setup-efi-ivi improvements)Artem Bityutskiy2-1/+5
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: generate configuration for all kernelsArtem Bityutskiy2-21/+27
Generate gummiboot configuration files for all installed kernels, not only for th newest kernel. Make the newest kernel to be the default, though. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: document which environment variables we depend onArtem Bityutskiy1-4/+17
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: use -u shell optionArtem Bityutskiy1-3/+3
It is a good practice to use the -u shell option because it helps writing cleaner and more secure scripts. Start using it. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: do not assume that boot partition in in /bootArtem Bityutskiy1-3/+5
Do not assume that the boot partition is currently mounted under /boot. In pc-installer environment it can be mounted under a different directory. Instead, use the INSTALLERFW_MOUNT_PREFIX variable to find the path to the boot partition. This should let pc-installer use this script as well. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-gummiboot-conf: handle the case of absent default entryArtem Bityutskiy1-2/+6
When the kernel which corresponds to the current default entry is removed, the script fails. Fix this. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-gummiboot-conf: add new scriptsubmit/tizen/20130626.093738Artem Bityutskiy3-1/+99
This script updates gummiboot configuration files. Can be used when a new kernel was installed or a kernel was uninstalled. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: amend the kernel entry fileArtem Bityutskiy1-4/+4
Massage the kernel entry file to make it a little bit more compatible with what other automatic scripts will generate. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: use printf instead of echoArtem Bityutskiy2-5/+6
This is better because echo is very different in different shells, and interpret various special bytes differently, and its behavior may sometimes be very surprizing. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26packaging: release out (rename kernel entry)submit/tizen/20130626.050955Artem Bityutskiy2-3/+7
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: rename the gummiboot kernel entryArtem Bityutskiy1-2/+2
Use 'vmlinuz-$VERSION' instead of 'vmlinuz-default'. This makes it easier to deal with several kernels. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-26setup-efi-ivi: add Copyright/License informationArtem Bityutskiy1-0/+4
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-06-25Initial commitsubmit/tizen/20130625.144120accepted/tizen/20130625.160256Artem Bityutskiy4-0/+124
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>