projects / profile / ivi / meta-ivi.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 074adbf) | patch
ks: start using setup-mbr-ivi 97/13697/2 accepted/tizen/ivi/20131213.205418 submit/tizen/20131213.163434 submit/tizen/20131213.205520 submit/tizen/20131214.052310 submit/tizen/20131214.052513
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
Thu, 12 Dec 2013 11:55:09 +0000 (13:55 +0200)
committerArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
Thu, 12 Dec 2013 12:40:10 +0000 (14:40 +0200)
commit53b078d9dc51e250550ddf2c0bcf6bc575e80c0c
treeebc915db3917c15e2b7089322c1e751e7299b717tree | snapshot
parent074adbffb714e89bdd3310d76e3cddd339102932commit | diff
ks: start using setup-mbr-ivi

Similarly to how we use 'setup-efi-ivi' for EFI images, start using
'setup-mbr-ivi' for MBR images. This means that MIC won't generate
extlinux.conf for us anymore, but the 'setup-mbr-ivi' script will.

The required MIC changes have been deployed on the build servers. This fixes
TIVI-1818.

Change-Id: I501ddf3f475959f386c8d2254161b8fb14f75028
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
ks/ivi-mbr-i586-emul.yaml diff | blob | history
ks/ivi-mbr-i586.yaml diff | blob | history
ks/ivi-min-mbr-i586.yaml diff | blob | history
scripts/mbr.post [new file with mode: 0644] blob
Domain: SCM / Uncategorized;