<Tartarus>
and I'd love to in turn make CI use that + some tiny image to in turn boot test
<Tartarus>
maybe the kernelci rootfs images
wooosaiiii has joined #u-boot
<calebccff>
Tartarus: alpine have a 245M netboot image. also while we don't have one yet but we could do a generic aarch64 postmarketOS image pretty easily with NBD root support (or just a really fat ramdisk depending on what you want to test)
<yang2>
I would like to build an Allwinner Sunxi Uboot image, which would boot my OS, which resides on the SD card. Currently I have an Uboot, which boots (old OS) eMMC.
jaganteki has quit [Quit: Client closed]
<yang2>
Is it possible to specify which partition to use for boot within U-boot?
<mps>
yang2: it is simple, install all needed software and in u-boot source tree do `make teres_i_defconfig` and `make`
<mps>
forgot to tell, you will need something like 'export BL31="/usr/share/arm-trusted-firmware/sun50i_a64/bl31.bin' before running make
Hypfer has quit [Read error: Connection reset by peer]
Hypfer3 has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
prabhakar has quit [Quit: Connection closed]
prabhakar has joined #u-boot
prabhakarlad has joined #u-boot
<yang2>
OK, thanks. I will try in a few hours.
deathcamel57 has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
goliath has quit [Quit: SIGSEGV]
monstr has quit [Remote host closed the connection]
<qschulz>
I need to do some kernel compatible fixup for an Ethernet PHY, so I need to read the PHY ID from U-Boot and then inject it
<qschulz>
I really struggle to find a way to do this properly
<qschulz>
get_phy_id always returns 0
<qschulz>
mii info from the cli as well
<qschulz>
but dhcp does probe the proper Ethernet PHY driver (and finds the proper PHY ID from the PHY itself)
jaganteki has quit [Quit: Client closed]
<qschulz>
manually calling the ethernet controller's start function does a bit too much (PHY negotiation for example)
<qschulz>
does anyone have any pointer/idea on how to do this?
mckoan is now known as mckoan|away
rvalue has quit [Ping timeout: 256 seconds]
prabhakarlad has joined #u-boot
rvalue has joined #u-boot
<calebccff>
can buildman handle config fragments?
persmule has quit [Ping timeout: 240 seconds]
<Tartarus>
As of a few hours ago, a defconfig can #include a fragment, so yes
<calebccff>
Tartarus: hah, nice. Although for my usecase it's more like the config fragment supplements the defconfig rather than constructing it
<calebccff>
e.g. for building u-boot to be chainloaded vs as the primary bootloader
persmule has joined #u-boot
slobodan has quit [Ping timeout: 260 seconds]
persmule has quit [Remote host closed the connection]
<Tartarus>
Right, so you would say board_chainload_defconfig would #include board-base.config and then set the chainload options, and board_full_defconfig or whatever #include board-base.config and set the direct boot options
<Tartarus>
And then buildman knows board_chainload and board_full as options to build
persmule has joined #u-boot
Stat_headcrabed has quit [Quit: Stat_headcrabed]
qqq has quit [Quit: Lost terminal]
ezulian has quit [Ping timeout: 260 seconds]
<calebccff>
hmm, ok I can get behind that
<calebccff>
Tartarus: any ideas why sandbox_flattree is running dm_* tests? It doesn't do it on master but does on my branch... the only remotely related thing I touch is adjusting the button test
<calebccff>
im afraid i don't even know where to start digging into it
<vagrantc>
yang2: if you want to use the installed crust, you probably ... shouldn't build it from source?
<mps>
I think crust is not needed for teres-i u-boot
<vagrantc>
you need some SCP, if i recall correctly
<yang2>
ok, I'll skip this step then
<vagrantc>
but that can be /dev/null
<vagrantc>
yang2: you'll have to set SCP= the patch the the installed scp.bin
<yang2>
right
<vagrantc>
yang2: debian does ship the teres_i in u-boot-sunxi
<mps>
ah yes, I forgot I set 'export SCP=/dev/null' for alpine
<vagrantc>
yang2: so you don't necessarily need to build it from source at all
<mps>
I forgot that I *set* 'export SCP=/dev/null'
<vagrantc>
yang2: unless you're trying a patched version or something ...
<mps>
( I forgot everything already ;-) )
<vagrantc>
that's what revision control is for :)
<mps>
we have it but who will look 'git log'
<yang2>
so what do I do now ? export SCP=/dev/null
<vagrantc>
yang2: what is your actual goal? :)
<yang2>
my goal is to build U-boot binary "boot-sunxi-with-spl.bin" and flash it on eMMC
<vagrantc>
to learn how to do it? to get some custom features? to boot an operating syste,?
<yang2>
so I can define to boot from SD card next time, currently with older U-boot it boots into eMMC OS
<mps>
( when you work with such things use aikido principles, put all in 'emtiness')
* vagrantc
raises an eyebrow at the mention of aikido :)
<mps>
emptiness*
<mps>
vagrantc: why?
<mps>
you don't like aikido?
<vagrantc>
mps: just something i've been doing for the last 25 years or so
<yang2>
I did it for only 2 years
<yang2>
still helps me, when I fall
<mps>
ah, nice, also I but about 20 years
<vagrantc>
started getting into free software and aikido at roughly similar times, love it when they intersect :)
<vagrantc>
yang2: well ... you can keep following the instructions ... and either point SCP at /dev/null or the installed scp.bin
<vagrantc>
yang2: you also probably did not need to compile arm-trusted-firmware from source either
<mps>
also I feel that aikido and open source have something in common
<mps>
though I started with open source 30 or more years ago
<yang2>
vagrantc: I would like to compile scp.bin, I cannot find the "installed" one...
<vagrantc>
so when you said "< yang2> I have crust installed (debian)" what did you mean?
<yang2>
vagrantc: I guess the package crust, should already have the scp.bin (corect?)
<vagrantc>
crust-firmware is the package name in debian, and yes, it has the relevent files ...
<vagrantc>
or you can install an or1k cross-compiler and build it yourself ...
<yang2>
vagrantc: oh yes, I was trying to accomplish that with or1k compiler, but I guess with all these packages installed, it's still missing something https://paste.debian.net/1303936/
<yang2>
crust-firmware has /usr/lib/crust-firmware/teres_i.bin
<yang2>
so do I rename this into scp.bin ?
<mps>
I bet it is 'export SCP=/usr/lib/crust-firmware/teres_i.bin'
<yang2>
ok
<vagrantc>
which is just a symlink to the generic build :)
<mps>
I use teres-i u-boot quite fine without SCP
<mps>
(TBH, my teres-i actually just accumulate dust for one year nearly)