ikarso has quit [Quit: Connection closed for inactivity]
malte has joined #u-boot
vagrantc has joined #u-boot
tlwoerner has quit [Ping timeout: 252 seconds]
tlwoerner has joined #u-boot
apritzel has quit [Ping timeout: 260 seconds]
mmu_man has quit [Ping timeout: 244 seconds]
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #u-boot
LainExperiments has joined #u-boot
LainExperiments has quit [Quit: Client closed]
LainExperiments has joined #u-boot
LainExperiments3 has joined #u-boot
LainExperiments has quit [Ping timeout: 240 seconds]
dsimic has quit [Ping timeout: 252 seconds]
dsimic has joined #u-boot
LainExperiments3 has quit [Quit: Client closed]
persmule has quit [Remote host closed the connection]
LainExperiments has joined #u-boot
clamor has joined #u-boot
LainExperiments4 has joined #u-boot
LainExperiments has quit [Ping timeout: 240 seconds]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
LainExperiments4 has quit [Ping timeout: 240 seconds]
LainExperiments has joined #u-boot
vagrantc has quit [Ping timeout: 268 seconds]
warpme has joined #u-boot
warpme has quit [Ping timeout: 265 seconds]
LainExperiments has quit [Ping timeout: 240 seconds]
rvalue has quit [Read error: Connection reset by peer]
persmule has quit [Remote host closed the connection]
rvalue has joined #u-boot
persmule has joined #u-boot
LainExperiments has joined #u-boot
gsz has joined #u-boot
monstr has joined #u-boot
pgreco has quit [Ping timeout: 272 seconds]
monstr has quit [Ping timeout: 252 seconds]
vagrantc has joined #u-boot
apritzel has joined #u-boot
iprusov has quit [Quit: WeeChat 4.1.1]
warpme has joined #u-boot
LainExperiments has quit [Quit: Client closed]
gsz has quit [Ping timeout: 252 seconds]
warpme has quit [Client Quit]
ikarso has joined #u-boot
apritzel has quit [Ping timeout: 268 seconds]
mckoan|away is now known as mckoan
vagrantc has quit [Quit: leaving]
iprusov has joined #u-boot
gsz has joined #u-boot
warpme has joined #u-boot
enok has joined #u-boot
<shadow>
Tartarus: no, it's just absent from devicetree-rebasing and the "parent" visionfive2 board target (in U-Boot) is now OF_UPSTREAM; previous to OF_UPSTREAM there were some bespoke fdt overrides in the U-Boot starfive visionfive2 board target SPL code which were "just barely enough" to get Mars CM Lite booted even though upstream Linux lacks this devicetree support
<shadow>
for reference I have Mars CM and Mars CM Lite hardware, and intend to send patches upstream to effect this support... eventually. Progress on that is delayed.
<shadow>
i.e. meanwhile I did send patches to enable USB support and was able to focus my attention on 1-2 things at a time, and Mars CM + Mars CM Lite was waiting a donation of Mars CM hardware I did receive. I set some time aside to do this but friends ask to go skiing and ... well, I rather go ski than read schematics and do LKML submission
enok has quit [Remote host closed the connection]
pivi has quit [Quit: leaving]
pivi has joined #u-boot
monstr has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
sszy has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
gsz has joined #u-boot
apritzel has joined #u-boot
clamor has quit [Read error: Connection reset by peer]
clamor has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
vfazio_ has quit [Remote host closed the connection]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
goliath has joined #u-boot
<sjg1>
calebccff: I just replied to your comments on the EFI-app series. I've already applied it, but I sent a fixup patch
<sjg1>
calebccff: I am around today if there's anything to follow up on. I didn't send emails indicating that I applied the series, but will do so soon
<calebccff>
sjg1: applied it to your fork? Can we get it in shape for upstream instead?
<calebccff>
I noticed you're carrying my efistub RFC as well, it needs a lot of rework to be ready for upstream, i don't want to clash with the EFI app stuff so it would be good to coordinate on that
mripard has quit [Quit: WeeChat 4.5.2]
<calebccff>
sjg1: please don't send me patches that don't apply on u-boot master or next (or clearly describe what other series they depend on) :(
mmu_man has joined #u-boot
<sjg1>
calebccff: Yes I hope that we can sync all of this up, but it's really up to Tom, not me
<sjg1>
calebccff: Re the patch, patman only sends the branch/base commit in the cover letter. I should change that. I'll send a v2
<sjg1>
calebccff: OK done
<calebccff>
sjg1: not that we should get into it, but i have no reason to believe EFI app or EFI stub support wouldn't be accepted upstream, once the code is in good enough shape
<sjg1>
calebccff: The code is fine as a starting point and I have been building on it without any issues. The two series already were over 100 patches so it just doesn't make sense to try to keep polishing it out-of-tree
<sjg1>
calebccff: We don't do 'perfection' thing for normal boards. We accept a series which enables just the UART and boots to a prompt
<calebccff>
sjg1: im sure my efi stub series could get it with just a few revisions. it also doesn't need "over 100 patches"??
<calebccff>
sjg1: more importantly, i don't get paid to review patches which aren't getting pulled into upstream (read: source.denx.de/u-boot/u-boot), and i find it incredibly disingenuous of you to send patches to my inbox which only apply to your increasingly divergent fork
<sjg1>
calebccff: Right, your EFI stub series is pretty small. I haven't counted the EFI patches in my tree, but it must be around 100
<sjg1>
calebccff: I don't get paid to review patches at all, nor to write them :-) I thought you would be happy with a follow-up patch, given you took the trouble to review the code
<sjg1>
calebccff: I wouldn't characterise my patches as crap, though. If they didn't have efi: on the front, that would likely have gone in by now
<sjg1>
calebccff: I always work very hard on the quality of my patches and I believe you should be able to see that from the U-Boot tree today
<calebccff>
sjg1: no i wasn't calling your patches crap lol, some of the ones in my branch though...
<calebccff>
sjg1: I was under the impression (until about halfway through when i tried actually applying your series) that it would actually apply, it doesn't
<calebccff>
sjg1: so i have 29 patches in my inbox with no indication that they only apply to YOUR fork of u-boot
<calebccff>
sjg1: can you not imagine that would frustrate me a little bit?
enok has joined #u-boot
enok has quit [Client Quit]
enok71 has joined #u-boot
enok71 has quit [Client Quit]
enok has joined #u-boot
enok has quit [Client Quit]
enok71 has joined #u-boot
enok71 is now known as enok
gsz has joined #u-boot
malte has quit [Ping timeout: 244 seconds]
malte has joined #u-boot
<Tartarus>
shadow: Thanks, I'll take it then, I just wanted to know if I would then need to revert it in -next for example because the platform is there.
malte has quit [Ping timeout: 248 seconds]
warpme has joined #u-boot
malte has joined #u-boot
malte has quit [Ping timeout: 260 seconds]
malte has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]