<mkorpershoek>
it's indeed using venv, as Sout_ suggested.
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Sout_>
looking at the docker file, virtualenv -p /usr/bin/python3 /tmp/venv but dont know the difference between virtualenv and venv
<cambrian_invader>
venv is just the name of a directory
mckoan is now known as mckoan|away
mmu_man has joined #u-boot
joeskb7 has quit [Ping timeout: 252 seconds]
joeskb7 has joined #u-boot
<Sout_>
err meant virtualenv vs python -m venv. Googling seems like virtualenv is a more feature full venv.
<cambrian_invader>
venv is implemented in python, virtualenv is not
<Sout_>
ah k.
ldevulder has quit [Ping timeout: 272 seconds]
dgilmore has quit [Read error: Connection reset by peer]
Peng_Fan has quit [Read error: Connection reset by peer]
Tartarus has quit [Read error: Connection reset by peer]
dgilmore has joined #u-boot
LetoThe2nd has quit [Read error: Connection reset by peer]
lool has quit [Read error: Connection reset by peer]
lool has joined #u-boot
Peng_Fan has joined #u-boot
Tartarus has joined #u-boot
LetoThe2nd has joined #u-boot
<Tartarus>
mkorpershoek: oh nice, thanks!
<Tartarus>
I would note we use "virtualenv" in all the CI scripts, so maybe for consistency do that?
<sjg1>
Tartarus: Sorry I had to drop off for another meeting. Let me know what you want to do with bloblist
<sjg1>
calebccff: Re the devicetree selection, if there is something I can dig into I am happy to spend some time on it. Please let me know how I can help
goliath has quit [Quit: SIGSEGV]
<Tartarus>
sjg1: I think re bloblist in the end we'll be in the same spot. But please work towards getting rid of BLOBLIST_FIXED with the same priority as adding OF_BLOBLIST because I believe in the long term, with "Is there a bloblist" de-coupled from "make a bloblist" everyone will be on the same page
<Tartarus>
That might even mean making some new BLOBLIST symbols, I dunno
<Tartarus>
I spent a few hours down this path a few months ago now
<sjg1>
Yes I'm always happy to work on follow-ups and yes I am pretty sure we can drop BLOBLIST_FIXED
<sjg1>
Tartarus: I'll wait to see if you apply my series, I suppose?
<Tartarus>
sjg1: I think you need to spin a new series to start with maybe? I'll check later this week
<sjg1>
Tartarus: Yes I need to try it on QEMU. I also found that my old standard passage series never got applied, so that could be causing part of the confusion here. I will have to see if I can resurrect it
<Tartarus>
sjg1: Ah right, your current series breaks passage and so that needs to be fixed, yes
<sjg1>
Tartarus: I would argue that unless there is a CI test that fails, we shouldn't worry about it too much. If no one can be bothered to add one, then it isn't that important. Also it seems that bloblist in TF-A is just a PR, not landed yet
<Tartarus>
Maybe just look at old series as reference and not directly uplifting, standard passage is working now and part of this divorce is that others are handling standard passage
<sjg1>
Tartarus: OK, I'll take a look at these two things
<Tartarus>
sjg1: I just got how to run the tests documented. It's not in CI because it wasn't a 5 minute job I could give someone else to do
<Tartarus>
s/the tests/the vexpress platform with FVP/
<Tartarus>
And we aren't going to knowingly break things that aren't in CI when people are still testing them
<sjg1>
Tartarus: Yes, OK
<sjg1>
Tartarus: (I don't mean that I agree with that philosophy, just that I'll do it in this case)
<clamor>
sjg1: I couldn't test your changes since they are not accessible nor via browser, nor via git clone. It requires signing up
mmu_man has quit [Ping timeout: 244 seconds]
clamor has quit [Ping timeout: 272 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
clamor has joined #u-boot
<marex>
Tartarus: telco was nice, but sigh, got interrupted multiple times