<Forty-Bot>
Tartarus: well tbh I think there is not really a compelling use-case here
<Forty-Bot>
and it doesn't work in an orthogonal manner
<Forty-Bot>
also fwiw I had had pali manually CC'd since v1 and never thought about taking him off
<Forty-Bot>
I mean, you can just truncate
<Forty-Bot>
or do `dtc -a`
<marex>
Forty-Bot: how hard can it be to redirect all mail from lists.foo.bar to /dev/null on mailserver if you dont want to receive emails ...
<Forty-Bot>
idk
<Forty-Bot>
I have a filter which puts all my U-Boot emails in a folder
<Forty-Bot>
and marks the ones I'm not CC'd on as read
<marex>
Forty-Bot: like one line of config, so, I would say if someone has a problem with receiving ML traffic due to previous contributions, there is easy fix for that
<marex>
Forty-Bot: and it is not being unpleasant in the ML
<Forty-Bot>
well, he obviously feels that he has been wronged and that justifies the unpleasantness
apritzel has quit [Ping timeout: 264 seconds]
FergusL has quit [Quit: FergusL]
FergusL has joined #u-boot
sakman has joined #u-boot
mmu_man has quit [Ping timeout: 255 seconds]
jclsn has quit [Ping timeout: 264 seconds]
jclsn has joined #u-boot
sakman_ has joined #u-boot
sakman has quit [Ping timeout: 240 seconds]
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #u-boot
persmule has quit [Remote host closed the connection]
qqq has joined #u-boot
Clamor has joined #u-boot
pgreco has joined #u-boot
pgreco_ has quit [Ping timeout: 255 seconds]
camus has quit [Read error: Connection reset by peer]
camus1 has joined #u-boot
camus1 is now known as camus
Mis012- has quit [Remote host closed the connection]
Mis012 has joined #u-boot
Mis012- has joined #u-boot
Mis012 has quit [Remote host closed the connection]
monstr has joined #u-boot
ezulian has joined #u-boot
<cbmuser>
marex: Hi! If you're interested in SuperH, I would like to invite you to #linux-sh on Libera! And, yes, I'm the guy from the mailing list ;-).
tnovotny has joined #u-boot
mckoan|away is now known as mckoan
goliath has joined #u-boot
frieder has joined #u-boot
sszy has joined #u-boot
Stalevar has quit [Read error: Connection reset by peer]
Stalevar has joined #u-boot
mripard has quit [Quit: mripard]
mripard has joined #u-boot
ldevulder has quit [Quit: Leaving]
ldevulder has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
<cbmuser>
maybe I could load the u-boot image to "0xa0000000", then run "pmb" and then "go 0xa0000000"?
<Clamor>
That may work
<cbmuser>
I will give that a try later today with the known good image
<Clamor>
How many stages your u-boot has?
<cbmuser>
no idea, to be honest
<cbmuser>
I'm just getting started with hacking on u-boot
<Clamor>
Good luck then
<Forty-Bot>
the number of stages is probably the same as the number of times you see "U-Boot" printed during a boot
<Clamor>
Forty-Bot: you are not wrong ;)
<marex>
cbmuser: you likely need to remove lowlevel init from it, since that inits the DRAM
<cbmuser>
ah
<cbmuser>
Forty-Bot: I chuckled ;-)
<Clamor>
cbmuser: Do you have buildable sources which are known to produce working u-boot?
Clamor has quit [Ping timeout: 258 seconds]
Clamor has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
goliath has quit [Quit: SIGSEGV]
robher has quit [Server closed connection]
robher has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
persmule has joined #u-boot
slobodan has joined #u-boot
prabhakar has quit [Ping timeout: 240 seconds]
<Tartarus>
calebccff, Forty-Bot, I'm being imprecise in patchwork, please agree amongst yourselves on where the qcom clock changes come in. This isn't the linux kernel and I don't demand strict breakdowns via trees so long as relevant custodians have seen/reviewed the changes, that's what I think is the most important part.
monstr has quit [Remote host closed the connection]
<kabel>
hey guys, does somebody have contact with realtek?
<broonie>
Their audio people are reasonably active with upstream Linux, but I guess if you're asking here it's for a very different part of Realtek.
prabhakarlad has joined #u-boot
<calebccff>
Tartarus: Forty-Bot: I'm happy to take it all through Qualcomm. The ordering of the clock and pinctrl series matters to avoid conflicts in mach-snapdragon so it might be easier that way - and it will keep qcom-next bootable. The only conflict potential then would be in drivers/clk/{Makefile,Kconfig} I think
<calebccff>
That said, this is all very new to me; I'm happy to fit myself in whichever way causes the least hassle
<marex>
kabel: network realtek ?
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
vagrantc has joined #u-boot
<dsimic>
if someone has access to networking people from realtek, that would be great