wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
swiftgeek has joined #u-boot
GNUtoo has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
umbramalison has quit [Quit: %So long and thanks for all the fish%]
umbramalison has joined #u-boot
minimal has quit [Quit: Leaving]
thopiekar_ has joined #u-boot
thopiekar has quit [Ping timeout: 268 seconds]
<sjg1>
apalos: OK. Could use some unit tests too
torez has quit [Quit: torez]
wooosaiii has quit [Remote host closed the connection]
<sjg1>
apalos: BTW if you want people to start adding SMBIOS to their board (bearing in mind that most won't care because who cares about this x86 junk :-) then you should ask them to do it. One way would be to disable the SMBIOS option by default and give an error if the option is enabled but the info is missing
wooosaiii has joined #u-boot
<sjg1>
apalos: One risk with adding 'inferred' information is that when people go ahead and add something properly, they will effectively create two versions of the same board and user space will need to handle both
akaWolf has quit [Ping timeout: 252 seconds]
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #u-boot
akaWolf has joined #u-boot
scientes has joined #u-boot
swiftgeek has quit [Ping timeout: 255 seconds]
swiftgeek has joined #u-boot
wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
wooosaii has joined #u-boot
wooosaiii has quit [Read error: Connection reset by peer]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
scientes has quit [Quit: Client closed]
scientes has joined #u-boot
scientes has quit [Ping timeout: 252 seconds]
frieder has joined #u-boot
thopiekar_ has quit [Ping timeout: 252 seconds]
zibolo has joined #u-boot
thopiekar has joined #u-boot
ldevulder has joined #u-boot
ldevulder has quit [Quit: Leaving]
mkorpershoek has joined #u-boot
julienm has joined #u-boot
ldevulder has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
tre has joined #u-boot
guillaume_g has joined #u-boot
thopiekar has joined #u-boot
julienm has quit [Quit: Client closed]
matthias_bgg has joined #u-boot
<apalos>
sjg1: yea but atm 95% of the u-boot supported boards report "Unknown"
<apalos>
so I don't think we'll manage to duplicate much
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
jagan has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
bih420[m] has quit [Quit: You have been kicked for being idle]
jagan has quit [Quit: Connection closed]
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
akaWolf has quit [Ping timeout: 268 seconds]
jclsn has quit [Quit: WeeChat 3.5]
thopiekar has quit [Ping timeout: 252 seconds]
akaWolf has joined #u-boot
thopiekar has joined #u-boot
jclsn has joined #u-boot
<hanetzer>
suppose a broad family of socs support spi nand/nor, emmc/sdcard, usb, and serial boot. in the parent ARCH_FOO, like ARCH_ROCKCHIP, should these be select/imply/default, or should those sort of choices be done in the subfamily FOO_BAR, like ROCKCHIP_RK3288 ?
<hanetzer>
Domon: some socs have a means with which you can send u-boot into them over serial. depends on the soc.
<Domon>
hanetzer: Sad, but my SOC only support boot from NOR and NAND :/
<hanetzer>
Domon: what's the soc?
<Domon>
hanetzer: BCM47623
<hanetzer>
ah, broadcom
thopiekar has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
thopiekar has joined #u-boot
<hramrach>
hanetzer: it depends on the board design - the pins may not be avialable on some boards
<hramrach>
eg. the bcm chip on rPi can boot from USB but there is a hub mounted on most rPi boards preventing that option
<hanetzer>
hramrach: so, should I 'imply' things the soc is 'capable' of, and select what the board is capable of?
<hramrach>
probably board. Understandably there might be some reference design that many boards copy but not all of them
<hramrach>
Linux has twolevel options for many things - like FOO_HAS_BAR, BAR (depends on FOO_HAS_BAR)
thopiekar has quit [Ping timeout: 252 seconds]
<hramrach>
in this case you would do something like rk3288 support selects SOC_HAS_FOO_BOOT, and then enable FOO_BOOT per board if following this model
jagan has joined #u-boot
thopiekar has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
indy has quit [Ping timeout: 252 seconds]
<hanetzer>
ah yeh, that is true.
<hanetzer>
i2c md chip address[.0, .1, .2] << what is this 0 1 2?
indy has joined #u-boot
ldevulder has quit [Quit: Leaving]
ldevulder has joined #u-boot
monstr has joined #u-boot
apritzel has joined #u-boot
mmu_man has joined #u-boot
torez has joined #u-boot
minimal has joined #u-boot
hanetzer has quit [Quit: WeeChat 3.5]
jagan has quit [Quit: Connection closed]
<sjg1>
apalos: That is the current situation, which is fine. Who actually cares about the DMI stuff on ARM platforms anyway?
<sjg1>
apalos: With your change, everyone will get 'sometime' but not necessarily what the manufacturer intends. When they discover this and fix it, then we will have the same board hardware with two different values for the DMI into based on what U-Boot version they use. At least with 'unknown' that is obvious
<broonie>
sjg1: All the arm64 server stuff uses the whole x86 style firmware stack including interfaces like DMI.
<sjg1>
apalos: Perhaps there is a way to detect that the 'default' info it in use
<sjg1>
broonie: How many of those boards are in U-Boot?
<broonie>
sjg1: Ah, ECHAN - none.
<sjg1>
broonie: ECHAN?
<broonie>
wrong channel (I'd not registered that I was looking at the u-boot channel)
hanetzer has joined #u-boot
<minimal>
broonie: for Arm64 servers ARM (the company) defined SBSA (though I think its now called "ServerReady") where there's UEFI and ACPI, don't remember if DMI is part of that
<broonie>
minimal: Yeah, it's part of that whole pack of standards. ServerReady is a compliance testing/labelling programme for SBSA and related specs like SBBR.
<sjg1>
broonie: How does the DMI stuff get set in UEFI, or whatever you are using there?
<sjg1>
broonie: I would have understood -ECHAN, BTW :-)
<broonie>
sjg1: Dunno about the specific implementation off the top of my head. IIRC there's some standard way of discovering it from UEFI but ICBW.
<sjg1>
broonie: I might in the firmware build for UEFI, how is it represented in the source code...
<sjg1>
apalos: Anyway, I'm just wondering why we would enable SMBIOS for boards that don't need DMI...it is not an ARM embedded thing, so far as I know. So perhaps just getting authors to add the info as needed is the right thing?
jagan has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
prabhakarlad has quit [Quit: Client closed]
zibolo has quit [Ping timeout: 255 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
mckoan is now known as mckoan|away
mmu_man has joined #u-boot
matthias_bgg has quit [Read error: Connection reset by peer]
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
matthias_bgg has joined #u-boot
grgy has quit [Remote host closed the connection]
grgy has joined #u-boot
tre has quit [Remote host closed the connection]
wooosaii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
monstr has quit [Remote host closed the connection]
redbrain has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
wooosaiii has joined #u-boot
wooosaii has quit [Read error: Connection reset by peer]
<hramrach>
what info is the smbios supposed to provide?
<hramrach>
maybe if running the efi emulation it makes sense the pre-fill he part that can be inferred
<hramrach>
and fill the vendor name as u-boot or something to make it clear it's automagically generated and not provided by the board vendor
apritzel has quit [Ping timeout: 268 seconds]
<sjg1>
hramrach: That sounds good, at least it is then clear
<sjg1>
apalos: ^
frieder has quit [Remote host closed the connection]
Julia[m] has joined #u-boot
jagan has quit [Quit: Connection closed]
jagan has joined #u-boot
minimal has quit [Quit: Leaving]
mmu_man has quit [Ping timeout: 268 seconds]
jagan has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
torez has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
georgem_ has joined #u-boot
tom42_ has joined #u-boot
ccaione_ has joined #u-boot
bryanb_ has joined #u-boot
ullbeking_ has joined #u-boot
rhadye_ has joined #u-boot
NishanthMenon_ has joined #u-boot
lvrp16_ has joined #u-boot
guillaume has joined #u-boot
mlaga97_ has joined #u-boot
finga4 has joined #u-boot
clarity_ has joined #u-boot
ullbeking has quit [Ping timeout: 244 seconds]
bryanb has quit [Ping timeout: 244 seconds]
georgem has quit [Ping timeout: 244 seconds]
NishanthMenon has quit [Ping timeout: 244 seconds]
lvrp16 has quit [Ping timeout: 244 seconds]
ccaione has quit [Ping timeout: 244 seconds]
tom42 has quit [Ping timeout: 244 seconds]
clarity has quit [Ping timeout: 244 seconds]
finga3 has quit [Ping timeout: 244 seconds]
ddevault has quit [Ping timeout: 244 seconds]
cbmuser_ has quit [Ping timeout: 244 seconds]
hramrach has quit [Ping timeout: 244 seconds]
guillaume_g has quit [Ping timeout: 244 seconds]
flyback has quit [Ping timeout: 244 seconds]
mlaga97 has quit [Ping timeout: 244 seconds]
rhadye has quit [Ping timeout: 244 seconds]
lvrp16_ is now known as lvrp16
bryanb_ is now known as bryanb
NishanthMenon_ is now known as NishanthMenon
tom42_ is now known as tom42
georgem_ is now known as georgem
ccaione_ is now known as ccaione
rhadye_ is now known as rhadye
ddevault has joined #u-boot
flyback has joined #u-boot
hramrach has joined #u-boot
cbmuser_ has joined #u-boot
wooosaii has joined #u-boot
wooosaiii has quit [Read error: Connection reset by peer]
wooosaii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
wooosaii has quit [Remote host closed the connection]