Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2022.07 is OUT / Merge Window is OPEN, -next is CLOSED / Release v2022.10 is scheduled for 3 October 2022 / http://www.denx.de/wiki/U-Boot / Channel archives at https://libera.irclog.whitequark.org/u-boot
<marex> xypron: they still sell those sispmctl usb-controlled outlets ?
<marex> oh wow, they still do
qschulz has quit [Quit: qschulz]
qschulz has joined #u-boot
umbramalison has quit [Quit: %So long and thanks for all the fish%]
umbramalison has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
pavelow has quit [Quit: No Ping reply in 180 seconds.]
pavelow has joined #u-boot
vagrantc has quit [Quit: leaving]
LeSpocky has quit [Ping timeout: 252 seconds]
LeSpocky has joined #u-boot
mmu_man has quit [Ping timeout: 272 seconds]
hanetzer has quit [Ping timeout: 272 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
hanetzer has joined #u-boot
akaWolf has quit [Ping timeout: 272 seconds]
akaWolf has joined #u-boot
hanetzer has quit [Ping timeout: 245 seconds]
hanetzer has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
rvalue has quit [Ping timeout: 245 seconds]
rvalue has joined #u-boot
alpernebbi has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
Xeroine has joined #u-boot
mmu_man has joined #u-boot
Xeroine has quit [Ping timeout: 260 seconds]
gsz has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
Xeroine has joined #u-boot
akaWolf has quit [Ping timeout: 252 seconds]
akaWolf has joined #u-boot
haritz has quit [Remote host closed the connection]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
BWhitten has joined #u-boot
vagrantc has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
gsz has joined #u-boot
haritz has joined #u-boot
haritz has joined #u-boot
___nick___ has joined #u-boot
haritz has quit [Remote host closed the connection]
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
akaWolf has quit [Ping timeout: 252 seconds]
haritz has joined #u-boot
haritz has joined #u-boot
akaWolf has joined #u-boot
mmu_man has joined #u-boot
gsz has quit [Quit: leaving]
thopiekar has quit [Ping timeout: 240 seconds]
thopiekar has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
urja has quit [Quit: WeeChat 3.4]
urja has joined #u-boot
<sjg1> Tartarus: I sent another patch for common.h - if we can turn it around quickly I could do more for this release. There are about 15 patches to land. I could send more than one at a time if that would help, but any other PRs can often invalidate it, which is why I ask about timing
persmule has quit [Ping timeout: 268 seconds]
persmule has joined #u-boot
<marex> sjg1: hey
<marex> sjg1: are you around for a short binman question ?
<marex> sjg1: it's essentially a post-processing of imx8m flash.bin generated using binman
<marex> sjg1: it calls external tool, cst, for which you need to generate custom input text file
<marex> sjg1: I wonder whether this can be wrapped into binman/bintool, I'm sure it can
<marex> sjg1: that would help trimming all the scripted savagery
<sjg1> marex: Yes it looks like that could be done with a new entry type
<marex> new entry type ?
<marex> sjg1: so this would be a new entry in the fitImage ?
<sjg1> marex: It could be. From what I can tell you need cst to sign things
<marex> sjg1: yes, I need to sign the SPL after its been augmented with mkimage header , i.e. adding anything to fitImage is useless at that point
<sjg1> marex: It signs data from other entries and produces a signature: https://source.denx.de/u-boot/custodians/u-boot-imx/-/blob/master/tools/binman/test/074_vblock.dts
<marex> and I need to sign fitImage components, which is the second half of it (the design there is demented)
<marex> sjg1: I think the vblock is the second half ?
<marex> the nxp approach signs the blobs within the fitImage and the tree, so it seems to partly duplicate what fitImage already supports
<sjg1> marex: You can fairly easily sign FIT parts, if the FIT is built by binman. The contents of a FIT are just other entries, so one of those entries can be the signature stuff
<sjg1> marex: gbb is another entry type (etype) supported by binman
<marex> sjg1: no, one of the entries cannot be the signature stuff
<marex> sjg1: the CST blob has to be exactly 0x1000 bytes past the fitImage tree and the DEK (encryption) blob must be 0x2000 bytes past the CST blob
xroumegue has joined #u-boot
<marex> oh, and a generated IVT has to be placed at fitImage tree + 0x1000 - 0x20
xroumegue has quit [Client Quit]
<sjg1> marex: Then use offset = <(0x1000 - 0x20)> in the IVT entry
<marex> sjg1: I don't understand
<sjg1> marex: The fit is just an entry in the description, as is anything else. Here's an example that adds entries before and after the FIT: https://source.denx.de/u-boot/custodians/u-boot-imx/-/blob/master/tools/binman/test/161_fit.dts
<sjg1> marex: For more general understanding, the docs and this video might help: https://www.youtube.com/watch?v=L84ujgUXBOQ
<marex> sjg1: I need to place the generated blobs at specific offsets, not at random offsets where binman somehow decides to place them
<marex> sjg1: also, I am not looking for introduction to DT or how to describe things in DT, I am looking for prior art how to implement what I need
xroumegue has joined #u-boot
<sjg1> marex: Yeah well that is the point of the 'offset' property. It is relative to its parent entry
<sjg1> marex: I've given you the prior art I can think of
Xeroine has quit [Ping timeout: 252 seconds]
<sjg1> marex: You might also find all the rockchip stuff happy as they have been moving things to binman too
___nick___ has quit [Ping timeout: 245 seconds]
jpox has joined #u-boot
<Forty-Bot> why does nxp name all of its secure boot stuff "cst"
<Forty-Bot> even when they're completely different tools...
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
<marex> Forty-Bot: Code Signing Tool
<marex> Forty-Bot: they also have CSF, Code Signing File I think
<Forty-Bot> I know what it stands for
<marex> and they also have a lot of other TLAs
<Forty-Bot> but it bugs me that there's like 3 different tools with the same name
<marex> security and TLAs are cool
<marex> Forty-Bot: there is only one CST for HAB
<Forty-Bot> yeah, but there's another cst for qoriq
<Forty-Bot> named the same thing, but totally different tool
<marex> Forty-Bot: is that AHAB CST ?
<Forty-Bot> no, it's some other format
<marex> jeez
<marex> Forty-Bot: maybe they wanted it to be more convoluted and confusing, security by obscurity :)
<marex> it's so secure you cannot even get to the security, let alone mess with it
<Forty-Bot> the thing is
<Forty-Bot> they just call openssl
<Forty-Bot> and the whole tool is a wrapper for the binary format
<marex> Forty-Bot: but its binary, proprietary, seeeeekrit
<marex> (it did cross my mind to just rewrite it from scratch)
<Forty-Bot> if I had 6 months I'd do it
<marex> its probably not that complex
<marex> what is higher on my list of crap to fix is the DDR calibrator
<Forty-Bot> yeah, but I don't have self control
<Forty-Bot> yes
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Read error: Connection reset by peer]
GNUtoo has quit [Write error: Connection reset by peer]
persmule has joined #u-boot
GNUtoo has joined #u-boot
BWhitten has quit [Ping timeout: 245 seconds]
gsz has joined #u-boot
haritz has quit [Ping timeout: 240 seconds]
jpox has quit [Ping timeout: 240 seconds]
haritz has joined #u-boot
haritz has joined #u-boot
haritz has quit [Remote host closed the connection]
haritzondo has joined #u-boot
haritzondo has quit [Client Quit]
haritz has joined #u-boot
haritz has joined #u-boot