<narmstrong>
tomeu: did you dump the emmc ? if yes you can write it to the sdcard and it will boot
<tomeu>
ok, will do just that
<tomeu>
I'm unwrapping the other unit to do so now
<icecream95>
I think the 0x14-0x17 formats are ASTC. No idea why there are four which are all 4x4 block size.
megi has joined #panfrost
<icecream95>
Probably the unknown fields in the texture format struct encode the block size...
<icecream95>
Does Mesa have some sort of licensing deal with Khronos? The ARM ASTC encoder requires me to have "licences to develop such products under the relevant Khronos agreements" to encode images.
<chewitt>
the signed u-boot needs to be in a specific location for the SoC to see/load it
<chewitt>
that's in the URL
<icecream95>
0x14 is definitely ASTC. I've already got an [illegally encoded] texture displaying...
<icecream95>
0x15-0x17 seem to be exactly the same.
<tomeu>
chewitt: oh, I already have the bootloader in the SD card and works fine, but I also need to have the boot and root partitions there because I don't have anywhere else
<tomeu>
looks like the partition table also needs to be in the sector 0
<tomeu>
how can both the partition table and the bootloader coexist in the same sd card?
<icecream95>
Use GPT and only the secondary table at the end of the drive?
<chewitt>
MBR is sector 0, the SoC looks for something at a specific offset, which on GXL/GXM is 512 bytes or sectors (forget which) in
<chewitt>
if you write u-boot.bin.sd.bin starting sector 0 the offset is in the right place automatically
<tomeu>
oh, got it
<chewitt>
then create the partition scheme
<chewitt>
this overwrites sector 0, but there's enough space before you get to signed firmware
<chewitt>
(unlike older GXBB which looks for signed firmware in sector 0 .. bit of a design fubar)
yann has quit [Ping timeout: 240 seconds]
NeuroScr has quit [Quit: NeuroScr]
<tomeu>
hrm, looks like creating the partition table has overwritten the bootloader
yann has joined #panfrost
<icecream95>
Does anyone have any ideas for where the field for ASTC block size could be?
<chewitt>
^ that's the same as used in the image I posted
<chewitt>
which is using the vim2 fip sources (on a chance)
<chewitt>
and u-boot 2020.01
<tomeu>
isn't that overwriting the first sector?
<narmstrong>
the last byte of the first sector must be preserved
<tomeu>
I still don't get it: the first image is going to be written to bytes 0-444, thus overwiting the MBR
<narmstrong>
nop, the MBR is later
<tomeu>
ok, looks like writing the second block worked
megi has quit [Quit: WeeChat 2.7]
<urjaman>
the MBR partition table is bytes 446 to 509
<tomeu>
oh, that explains, thanks
<tomeu>
the second write seems to corrupt the GPT table somehow
<urjaman>
i thought you were only using the MBR
<urjaman>
the GPT is later
<tomeu>
a ok, that's it then
<urjaman>
the primary GPT is sectors 1 to 33
<tomeu>
ok, will try writing only after 33
<tomeu>
hrm, the bootloader seems to be in those sectors
<tomeu>
would a DOS partition table be better?
<urjaman>
that's what i meant when i said MBR
<tomeu>
ok, let's see
<tomeu>
no luck
<tomeu>
maybe I didn't copy out a big enough chunk of the working emmc
<tomeu>
was expecting 1M to be enough
davidlt has quit [Ping timeout: 260 seconds]
bbrezillon has quit [Quit: WeeChat 2.7]
bbrezillon has joined #panfrost
<narmstrong>
yeah GPT can't work with the amlogic boot binary, only MBR
megi has joined #panfrost
<alyssa>
icecream95: Woohoo!
<alyssa>
icecream95: Woohoo!
<alyssa>
Uh, double ok
<alyssa>
icecream95: I would expect ASTC parameters, if they're implicit, would be in an unknown from mali_texture_format or mali_texture_descriptor
<alyssa>
Of which there are many
<alyssa>
Anisotropic filtering parameters I would expect to be in mali_sampler_descriptor, perhaps in the upper unknown bits of filter_mode currently seen just as 0
<alyssa>
But that's Bifrost-only, I think
alpernebbi has joined #panfrost
davidlt has joined #panfrost
<tomeu>
narmstrong: btw, booting after writing the emmc contents to a sd card doesn't seem to work
BenG83 has joined #panfrost
<leinax>
tomeu: thanks, just enabled that setting
guillaume_g has quit [Quit: Konversation terminated!]
<BenG83>
so I found out how to switch glamor to use either GL or GLES2, but both variants break panfrost in xwayland, but was worth a shot...
<BenG83>
running out of easy things to poke at, I wonder what is the difference in xwayland/glamor using panfrost and native wayland applications
raster has quit [Quit: Gettin' stinky!]
stikonas has joined #panfrost
karolherbst has quit [Quit: duh 🐧]
jernej has quit [Ping timeout: 260 seconds]
karolherbst has joined #panfrost
warpme_ has quit [Quit: Connection closed for inactivity]
<alyssa>
HdkR: "Lenovo plans to start sales of the IdeaPad Duet Chromebook in April."
<alyssa>
Don't tell me you're thinking of a launch-day Bifrost driver? =P
<HdkR>
hah
<alyssa>
Be the change..
icecream95 has joined #panfrost
icecream95 has quit [Ping timeout: 260 seconds]
icecream95 has joined #panfrost
chewitt has quit [Quit: Zzz..]
<icecream95>
unknown3 in mali_texture_descriptor is two 8-bit fields, not 1 16-bit one.
<alyssa>
icecream95: Ah?
<icecream95>
Scratch that. It's just the two high bits of unknown3 seem to be flags that can be set to one, the rest of the bits have to be zero. No idea what the flags do yet...
<alyssa>
Weeeeeee.
<alyssa>
icecream95: isn't witchcraft fun? :O
<anarsoul>
sure it is
<icecream95>
Especially when you are trying to go through all the values in a 32-bit field...