zombah has quit [Quit: Leaving]
amitk has joined #linux-exynos
aballier has joined #linux-exynos
zombah has joined #linux-exynos
dlan has quit [Ping timeout: 255 seconds]
dlan has joined #linux-exynos
LanDi has joined #linux-exynos
LanDi has quit [Quit: fui !]
Tenkawa has joined #linux-exynos
Tenkawa has joined #linux-exynos
<indy> hi all
<Tenkawa> h
<Tenkawa> i
<indy> what is status of u-boot?
<sjoerd> For which board
<indy> snow
<Tenkawa> not sure..
<sjoerd> works
* Tenkawa runs debian on his snow board
<Tenkawa> I think I'm running verified boot though
<Tenkawa> I still wrap my kernel
* indy has spi flashed u-boot
<indy> no vboot
<indy> i'm investigating that mysterious https://www.dropbox.com/s/6pzvraf3ko14sz9/nv_image-snow.bin.gz which i have flashed on spi
<indy> to somehow get there new one
<indy> and be able boot latest kernel
<javier__> indy: mainline u-boot works very well on snow, pit and pi afaict
<javier__> I've been using it for some time without issues
<sjoerd> Having it flashed in SPI might make it behave differenlty
<sjoerd> Rather then puttig in on the kernel parittions
<javier__> sjoerd: right, I missed that indy wanted to flash it on the SPI
<javier__> maybe is relying on the ro chromiumos u-boot to do some init
<sjoerd> I'm also not sure whether flahsing to SPI means he replaced the RO or RW part
<javier__> indeed
<indy> sjoerd, even you remove hw write protection, first 2mb of spi flash is still marked as ro and must be removed using chromium flashrom
<indy> or
<indy> i uboot
<zombah> if this is archlinux u-boot, flashing it to spi replace both if write protection removed
<indy> zombah, yes it is uboot from archlinux forum
<zombah> its newer chromeos u-boot build, it chainloads mainline u-boot fine here
<indy> zombah, how?
* indy is not against chainloading
<zombah> run vboot_twostop command it, its works mostly same as factory uboot
Tenkawa has quit [Remote host closed the connection]
<zombah> text menu asking for ctrl+u to boot custom uboot from sd/usb
<zombah> but becarful you need original spi backup safe, because it contain your hardware keys if you plan to use chromeos anytime ever
<zombah> with this custom u-boot compiled by archlinux guys, chromeos will continue work from emmc, but will not upgrade/etc
<indy> zombah, i made backup of spi flash before i 'crossed rubicon', but lost that backup :)
<indy> so it was really crossing rubicon, no way back
<indy> zombah, and i don't plan use chromeos
<zombah> indy: you can still use chromeos installed or install chromium which can work without security keys
<zombah> indy: its useful for tests etc, to see how hardware work there, thats only cases i use it after i have linux on snow
<indy> zombah, can i run chromeos from sdcard?
<zombah> indy: probably, i never tried myself
<zombah> indy: but only chromium os variant, chromeos will not install without keys partition in spi i think
<indy> zombah, well, my intention is to continue in 'civil war', not to cross rubicon back
<zombah> indy: 8)
<indy> i would like to find way to update u-boot spl and u-boot in spi to have there newest u-boot
<zombah> indy: boot linux from sdcard and reflash spi, you need chromeos flashrom for that
<indy> zombah, easily extractable from latest recovery image from google
<zombah> indy: you have way to recover in case of spi flashing fail?
<zombah> indy: if not better stay with current u-boot in spi if it work for you
<indy> not yet, i plan to buy soic clip
afaerber_ has joined #linux-exynos
<zombah> indy: then better stay with your current u-boot as first stage bootloader
<indy> zombah, so how to chainload it?
<indy> that vboot_twostop can boot also from emmc?
<zombah> indy: turn off, insert usb flash stich with archlinux alarm image into ehci usb port, turn on it will start to boot
afaerber has quit [Ping timeout: 252 seconds]
<indy> zombah, i completely removed original environment, i have only 10 environment variables
<indy> zombah, vboot_twostop is onetime command or i need to stop u-boot?
<zombah> indy: for me this u-boot always start in u-boot console unless i have disk with vmlinux.uimg inserted
<zombah> indy: i dont have chromebook right now, but i can share enviroments later in the evening today
<zombah> but as i remember there was some example setup on archlinux site
<zombah> indy: this is my boot load of vboot_twostop usage from serial console http://paste.opensuse.org/44607835 vboot_twostop is line 54
<zombah> indy: boot log i mean
<zombah> indy: line 272 is mainline u-boot start from sdcard
<indy> zombah, so it should also boot from emmc?
<zombah> indy: i have chomeos on emmc, it boots with vboot_twostop if i not interrupting it with ctrl+u, which boots linux from any external media
<indy> zombah, but on spi you have original chromeos firmware
<zombah> indy: no i have image archlinux made, the link you posted above
<zombah> nv_image-snow.bin
<indy> zombah, what you have in u-boot environment?
<zombah> indy: i will create paste of enviroment settings closer to midnight
<indy> zombah, and how you make upstream uboot image?
<javier__> indy: fwiw I have the original chromiumos u-boot and created a signed FIT image with mainline u-boot
<zombah> indy: but better use image from some linux distro for start
<javier__> indy: so the u-boot in the SPI flash loads a FIT image with mainline u-boot from the eMMC and that loads a mainline kernel
<zombah> here is example of script which create partition table and kernel image for vboot_twostop loading http://paste.opensuse.org/61821836
<zombah> bootloader image, not kernel to be sure
<indy> zombah, javier__ must be signed?
<javier__> indy: yes
<indy> that's why i want mainline uboot on spi
<javier__> indy: but what's wrong with signing the u-boot? there are packages with the keys on most distros
<indy> "it seems that perfection is attained, not when there is nothing more to add, but when there is nothing more to take away. - a. de saint exupery"
<javier__> and is not like you update u-boot daily
<javier__> anyway, I just wanted to let you know my setup since a chain loading setup works perfectly for me
<indy> javier__, currently it means repartitioning emmc, therefore backup everything from home :)
zombah has quit [Quit: Leaving]
<javier__> ojn: the patch "ARM: dts: Make DP a consumer of DISP1 power domain on Exynos5420" I posted yesterday fixes the error you found on peach pi and pit
<javier__> ojn: it would be great if you can test it and confirm that's the case
<javier__> we didn't find it before because on kernelci, the kernel doesn't panic even after the imprecise external abort error
<javier__> so kernelci was reporting it as a pass
<indy> javier__, which .bin file i need? make snow_config && make built u-boot.bin and u-boot-dtb.bin and two bins in spl/
liquidAcid has joined #linux-exynos
<sjoerd> indy: -dtb.bin
<indy> what about those spl bins
<sjoerd> you don't need those if you're chainloading u-boot only if you need the spl stage
<indy> for cheinloading do i need to create from them uboot image using mkimage or directly use bin?
<indy> chain
<sjoerd> the script zombah posted earlier does the right thing
<indy> it is about signing some img file
gladiac has quit [Remote host closed the connection]
gladiac has joined #linux-exynos
amitk has quit [Quit: leaving]
zombah has joined #linux-exynos
<zombah> indy: u-boot enviroments from my setup http://paste.opensuse.org/43510925
zombah has quit [Quit: Leaving]
MahNaz has joined #linux-exynos
<MahNaz> is it possible to find the interrupt numbers for Exynos5420 or Exynos5422?
<liquidAcid> MahNaz, should be somewhere in plat-samsung i guess