monstr has quit [Read error: Connection reset by peer]
goliath has joined #u-boot
monstr has joined #u-boot
mckoan|away is now known as mckoan
warpme has joined #u-boot
frieder has joined #u-boot
naoki has joined #u-boot
slobodan has joined #u-boot
ikarso has joined #u-boot
per1cycle has joined #u-boot
per1cycle has joined #u-boot
per1cycle has quit [Changing host]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<per1cycle>
Hey, I'm currently working on mainline(ize) the vendor's uboot to upstream, and I've watch this video https://youtu.be/5E0sdYkvq-Q?si=dufqJ1VELtMS8XdK to know the basic workflow. i wonder what is the effect should achieve next? my board is sipeed licheepi3a(with spacemit k1 soc same as bpif3)
per1cycle has quit [Quit: Client closed]
per1cycle has joined #u-boot
sszy has joined #u-boot
per1cycle has quit [Changing host]
per1cycle has joined #u-boot
ellyq_ has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
ellyq_ has joined #u-boot
warpme has joined #u-boot
xroumegue has quit [Ping timeout: 260 seconds]
mmu_man has quit [Ping timeout: 255 seconds]
xroumegue has joined #u-boot
persmule has quit [Remote host closed the connection]
mmu_man has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
per1cycle_ has joined #u-boot
per1cycle has quit [Quit: Client closed]
slow99 has quit [Quit: slow99]
slow99 has joined #u-boot
<qschulz>
do we have documentation on all the environment variables that do something in U-Boot?
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<qschulz>
i'm asking because we're about to add a new one for the number of random bytes to feed as seed to the rng on Rockchip
mmu_man has quit [Ping timeout: 246 seconds]
OLGA39 has joined #u-boot
OLGA39 has quit [Client Quit]
mmu_man has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
warpme has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
wooosaiiii has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
<qschulz>
well, yes :) but there's code already that uses that # sign
<sjg1>
qschulz: It's largely because it would be even odder to have to define DEBUG and/or LOG_DEBUG depending on whether debug() or log_debug() is used in the file. What do you suggest?
<qschulz>
sjg1: I want to be able to print log_debug/debug without triggering an assert() :)
<qschulz>
so, I would suggest to decouple debug() from DEBUG
<Forty-Bot>
I would rather decouple assert() from DEBUG
<qschulz>
or we should just not have debug() anymore and migrate to log_debug() entirely and then have LOG_DEBUG not define DEBUG?
<qschulz>
Forty-Bot: or that, don't know what's best practice/most used for enabling assert() in C projects
<LeSpocky>
std assert() behaviour depends on definition of NDEBUG