Skip to content

Latest commit

 

History

History
110 lines (100 loc) · 3.67 KB

board-mappings.ini

File metadata and controls

110 lines (100 loc) · 3.67 KB
 
1
2
### Don't edit this file manually. Update it in git, if there's a good reason to do so ###
#
3
# This file is used by ssu to find out which device (or device variant) it's
4
5
6
7
# running on, and use this information to look for device family, and device
# specific adaptation(s). The last two values are used when resolving URLs,
# and therefore change depending on vendor setup.
#
8
# To avoid quoting in the search strings ssu will do each checks on the
9
10
11
12
13
14
15
# _value_, and return the key, if successful. The device model returned
# my either be the device model, or a variant. Before resolving the family
# and adaptations variants will be resolved through entries under the
# variants category.
#
# Valid categories for determining the model:
# - file.exists -- checks for existince of a file in the filesystem
16
# - hwrelease.device -- Compares MER_HA_DEVICE in /etc/hw-release
17
# - cpuinfo.contains -- searches /proc/cpuinfo for a string
18
19
# - uname-release.contains -- searches the kernels release string for
# a string (uname -r)
20
21
22
# - arch.equals -- compares with zyppers arch (like i586)
#
# Resolve order is:
23
# file.exists -> cpuinfo.contains -> hwrelease.device
24
# -> uname-release.contains -> arch.equals
25
26
27
28
#
# The found model (after resolving variants) will be used as category. The
# following keys are valid there:
# - family -- the device family, used for the family specific adaptation
29
# - adaptation-repos -- list of adaptation repositories for this family
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# The value of adaptation-repos gets converted into a QStringList, which
# uses commas as separator. If one of the adaptation names contains a comma
# it needs to be quoted:
# adaptation-repos=foo
# adaptation-repos="foo, bar", baz
# adaptation-repos=foo, bar, baz
#
# The adaptation list is used to create repo files for adaptation repos.
# A repository named 'adaptation0' operates on the first list element,
# 'adaptation2' on the 3rd, etc. The matching item in the list will be
# exported as adaptation variable.
#
# Freeform variable sections start with 'var-'. A variable section for an
# adaptation named 'n9xx' would be 'var-n9xx'. A variable section may
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
# contain freeform variables, and/or the keyword 'variables' to include any
# other section.
#
# Sections are resolved in the order specified, overwriting existing variables
# in the resolving order (set your systems log to DEBUG and check for warnings
# if you run into problems). The main section is resolved last, thus taking
# precedence over any section specified.
#
# Variables starting with _ are treated as 'local', and are not available for
# URL resolving. Additional variables can be declared as local by using the
# special key 'local' with a stringlist of variables.
#
# If available a default-section is used to initialize variables before
# resolving starts. To find a default section the section name is split at
# '-', and the first (for var- second) token replaced with 'default' (e.g.
# foo-bar -> default-bar; var-foo-bar -> var-default-bar). As additional
# dashes would mess this detection up you should try to avoid dashes in
# section identifiers where this functionality is desired.
#
# Valid examples are:
73
74
75
76
77
78
79
80
81
82
83
84
#
# The N9x mappings should be solved through sysinfo, but that's currently
# broken on Mer/Nemo
[file.exists]
SDK=/mer-sdk-chroot
[cpuinfo.contains]
N900=Nokia RX-51 board
N950=Nokia RM-680 board
N9=Nokia RM-696 board
85
86
87
88
[hwrelease.device]
mako=mako
grouper=grouper
89
90
91
92
93
94
95
96
[arch.equals]
generic-x86=i586
[variants]
N950=N9
[N9]
family=n950-n9
102
103
104
105
106
[SDK]
[generic-x86]
family=x86