narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
doppo_ has quit [Ping timeout: 246 seconds]
doppo has joined #linux-amlogic
naoki has joined #linux-amlogic
camus has quit [Quit: camus]
camus has joined #linux-amlogic
jacobk has joined #linux-amlogic
gis has quit [Ping timeout: 246 seconds]
gis has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
doppo has quit [Ping timeout: 248 seconds]
doppo has joined #linux-amlogic
f_[xmpp] has quit [Ping timeout: 248 seconds]
rektide has quit [Ping timeout: 268 seconds]
jacobk has quit [Ping timeout: 250 seconds]
fiii8 has joined #linux-amlogic
ldevulder has joined #linux-amlogic
fiii has quit [Quit: Ping timeout (120 seconds)]
fiii8 is now known as fiii
naoki has quit [Quit: naoki]
rockosov has quit [Ping timeout: 250 seconds]
rockosov has joined #linux-amlogic
elastic_dog has quit [Ping timeout: 246 seconds]
elastic_dog has joined #linux-amlogic
f_ has joined #linux-amlogic
<rockosov> jbrunet: narmstrong: Hello Neil and Jerome! I've sent new version of A1 clk driver (v11), please take a look - https://lore.kernel.org/all/20230321193014.26349-1-ddrokosov@sberdevices.ru/
<rockosov> But I have one question about other drivers in our hands which are depending on clk driver. Can we send it now? Or it's better to wait clk driver merged?
kenny has quit [Ping timeout: 248 seconds]
f_ has quit [Ping timeout: 240 seconds]
jelly has quit [Ping timeout: 252 seconds]
<narmstrong> rockosov: for the drivers yes sure, for the DT which depends on the clock bindings you should wait until the clk bindings are accepted on the clk-meson tree
<narmstrong> But you can send all the other drivers changes without any problem
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #linux-amlogic
<rockosov> narmstrong: Thank you for clarification!
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_1 has joined #linux-amlogic
jacobk has joined #linux-amlogic
elastic_dog has quit [Ping timeout: 246 seconds]
elastic_dog has joined #linux-amlogic
tsegers has quit [Remote host closed the connection]
tsegers has joined #linux-amlogic
rockosov has quit [Read error: Connection reset by peer]
tsegers has quit [Remote host closed the connection]
tsegers has joined #linux-amlogic
jelly has joined #linux-amlogic
vagrantc has joined #linux-amlogic
rockosov has joined #linux-amlogic
jacobk has quit [Ping timeout: 250 seconds]
f_ has joined #linux-amlogic
f_[xmpp] has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
hays has joined #linux-amlogic
<hays> I've come across what seems to be two valid ways to flash the bootloader for s922x devices. One is to flash a u-boot.bin.sd.bin at offset 0 with a hole at {440..512} (or sometimes 444..512 is given). The other way is to flash u-boot.bin from offset 512, not touching those first 512 bytes
<hays> is there a right or wrong way to do this? and what's going on with those ranges from 440 to 512?
<hays> closest i can get to an answer is here https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout where "structure of modern standard MBR" table shows (potentially) 0-440 all being essentially reserved for bootstrap code, then 440-512 is your "disk signature" and paritition entries.
f_ has quit [Quit: Lost terminal]
<narmstrong> hays: yep it should be 440, but this is to keep legacy, it seems the first 440bytes aren’t useful anymore on s922x, but nothing actually confirmed this
<narmstrong> On spi, usb and emmc boot partition we omit those 440bytes so I think it’s really useless now, in fact I never understood what are those bytes…
<hays> do you know the difference between the uboot.bin.sd.bin and uboot.bin images?
<hays> the difference in size is a tantalizing 488 bytes
<hays> oh wait
<hays> nevermind, I have my answer.
ldevulder has quit [Quit: Leaving]
<narmstrong> hays: it’s the same, .sd.bin has 512 bytes prepended with those 440 bytes inside
Lyude has quit [Ping timeout: 248 seconds]
Lyude has joined #linux-amlogic
anessen97 has joined #linux-amlogic
blasty__ has quit [Ping timeout: 268 seconds]
blasty__ has joined #linux-amlogic