ikarso has quit [Quit: Connection closed for inactivity]
mmu_man has quit [Remote host closed the connection]
mmu_man has joined #u-boot
pedro_pt has quit [Quit: Client closed]
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
goliath has quit [Quit: SIGSEGV]
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 256 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 256 seconds]
mmu_man has joined #u-boot
naoki has joined #u-boot
hanetzer has quit [Ping timeout: 264 seconds]
hanetzer has joined #u-boot
vagrantc has joined #u-boot
mmu_man has quit [Ping timeout: 276 seconds]
<ac_slater>
anyone know a trick or whatever to break from a loop? I have a pretty A/B boot scheme but some variables are created and thus I cant really use setenv where everything expands. So I'm trying do to a `while true; do ... ; break; done` kinda thing but `break` isn't there....
<ac_slater>
I guess break is in newest Uboot
<ac_slater>
oh nevermind , 'builtin_no_written'
wooosaiiii has quit [Remote host closed the connection]
<zear>
cambrian_invader, thanks for replying in the thread as well
<marex>
cambrian_invader: the leds {} node is a subnode of the PHY node
<cambrian_invader>
marex: I think function is too generic a name for how you use it
<marex>
cambrian_invader: oh ?
<cambrian_invader>
the function is just a name, it doesn't drive behavior
<cambrian_invader>
so e.g. the function should be LED_FUNCTION_LAN
<marex>
cambrian_invader: and what does drive behavior in the LED subsystem bindings ?
<cambrian_invader>
userspace :)
<cambrian_invader>
but in Linux, it's linux,default-trigger along with trigger-sources
<marex>
cambrian_invader: that is for software controlled LEDs, the PHY LEDs are hardware controlled here
<cambrian_invader>
there's no distinction
<cambrian_invader>
hardware is only supposed to accelerate software
GNUtoo has quit [Remote host closed the connection]
<marex>
cambrian_invader: I suppose with the broadcom PHY, you can set function which would indicate they are software controlled, and then use triggers and all that infra
GNUtoo has joined #u-boot
<cambrian_invader>
well, the function would be "lan" and then maybe you'd set u-boot,trigger to be something like "link-100" or whatever
<cambrian_invader>
but that's not really expressive enough, since maybe you want it to be "link-10 or link-100"
<cambrian_invader>
so maybe a list?
<marex>
that function would be "LINKSPD-1" and the hardware would do the blinking
<marex>
or the function could be some user controlled something, and then yes, you would be able to toggle it as GPIO LEDs
<marex>
or how do you propose the hardware accelerated bindings would look like ?
<cambrian_invader>
like above
<marex>
cambrian_invader: I really want to avoid custom bindings there
<marex>
cambrian_invader: anything generic ?
<marex>
cambrian_invader: and btw wasnt linux,... and u-boot,... type of configuration in DT frowned upon ?
<cambrian_invader>
yeah, but Linux has userspace do the config
<cambrian_invader>
so IMO this is a great place to do this
<marex>
cambrian_invader: that kinda sucks, because I also want to use the same LED configuration in U-Boot
<marex>
(and uh, I'm really only 50% here attention-wise, sorry)
sakman1 has joined #u-boot
sakman has quit [Ping timeout: 260 seconds]
sakman1 is now known as sakman
<marex>
cambrian_invader: do you want me to CC you on that RFC kernel patch ?
<marex>
cambrian_invader: the ^ input is useful I think, I just dont have the capacity to process it right now, sorry