sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<sb0>
hartytp, who is AUTProgram?
<sb0>
hartytp, this has already been suggested and discussed, and we're OK with that, but it is not funded
<sb0>
whitequark, now that flterm support has been removed from the bootloader, and that the sdram support in the bootloader and misoc have diverged, it is a pain to bypass the dysfunctional sayma flash on marmelada's board ...
<sb0>
whitequark, in general 1) things like the bootloader should be designed assuming that every single component on the target board is going to malfunction at some point and needs a bypass so that progress can continue to be made 2) replacing something is done only after it has feature and issue parity with the old solution
<whitequark>
(1) makes sense but in practice (2) just makes sure that nothing can ever be replaced with anything else without wasting a huge amount of time, or ever
<whitequark>
if you mean that the rust bootloader should support SFL, then just say that...
<sb0>
whitequark, yes it should support SFL
<sb0>
whitequark, I don't see how it "wastes" more time than plowing ahead with the replacement and then firefighting
<sb0>
(2) basically is planning things carefully
<sb0>
whitequark, when you replaced the compiler, there was a period where it worked significantly worse than mine and I had to explain why. ditto smoltcp, on a much worse scale. now the bootloader. it would be a pity not to see a pattern and learn lessons there.
<sb0>
whitequark, and this is not a criticism of the replacements themselves, which are clear improvements compared what a was there before, but of the careless way in which they are made, which causes a lot of practical problems and pain and frustration to users
<sb0>
whitequark, if you look at SED, which is one major replacement I made, you can see that it was 1) discussed beforehand with stakeholders 2) implemented in a branch 3) merged only after it passed unittests and was tested by different people
<sb0>
and I have raised the SFL issue earlier, but since there are so many things going on I didn't press on
rohitksingh_work has joined #m-labs
<whitequark>
SFL is just one thing the misoc bootloader supports. it has a lot more functionality that no one has missed.
<sb0>
yet? I use the mr/mw commands regularly
<sb0>
I just haven't written much relevant gateware lately
<sb0>
netboot can be dropped/delayed, or replaced with something better
<sb0>
also this whole thing is a distraction from the camera driver and the allaki failures
<sb0>
the camera driver and allaki are funded and visible to users, the bootloader replacement is neither
ncl has quit [Read error: Connection reset by peer]
ncl has joined #m-labs
rohitksingh_work has quit [Ping timeout: 260 seconds]
hartytp has joined #m-labs
<hartytp>
sbo: one of our students
<hartytp>
Not asking for anything from you right now
<hartytp>
And know this isn't funded
<hartytp>
Just giving you a heads up that we're doing it
<hartytp>
If you want us to push upstream when we're done then we will otherwise we will just use locally
<hartytp>
Your call
hartytp has quit [Ping timeout: 260 seconds]
<GitHub-m-labs>
[artiq] enjoy-digital commented on issue #967: It's working on a simple design (Nexys Video / SERWB overa HDMI cable and the two HDMI TX/RX ports / A master and a Slave in the same design). I'm doing more testing on that (P&R is only 30 seconds, so it's easier), cleaning up things, and i'll test/integrate in ARTIQ. https://github.com/m-labs/artiq/issues/967#issuecomment-379163341
<whitequark>
sb0: I was finally able get some work done today
<GitHub159>
llvm-or1k/artiq-6.0 a5472fd Eugene Zelenko: Add missing header for InstructionCombining.cpp, in order to export LLVMInitializeInstCombine as extern "C". Fixes PR35947....
<whitequark>
bb-m-labs: force build --props=llvm-or1k conda-all
<bb-m-labs>
Something bad happened (see logs)
<whitequark>
bb-m-labs: force build --props=package=llvm-or1k conda-all
<bb-m-labs>
build #111 forced
<bb-m-labs>
I'll give a shout when the build finishes
<whitequark>
okay, we're at LLVM 6.
<whitequark>
or rather, will be once the builds finish
<whitequark>
tests pass...
<whitequark>
allaki now.
<whitequark>
sb0: oh also when building packages now I'm enabling clang and rust on windows
<whitequark>
any objections to that?
<whitequark>
it means being able to install artiq-dev on windows.
<sb0>
whitequark, that's okay, but not a priority
<whitequark>
already done, it was copying a few lines...
<_florent_>
whitequark: i'd like to have access to a sayma to test serwb
<_florent_>
whitequark: if you want to use sayma3, can you power on the other sayma?
<_florent_>
whitequark: but working together on two different sayma will probably be a bit difficult since we need to power off/power on to workadound the 1.8v issue
<_florent_>
whitequark: i need one board the next 3-4 hours i think, after that it should be good
<GitHub-m-labs>
[artiq] hartytp commented on issue #967: @sbourdeauducq With the caveat that I'm not aware of the precise details of any of the relevant contracts, and with apologies if this is treading on peoples' toes here, but...... https://github.com/m-labs/artiq/issues/967#issuecomment-378239721
<whitequark>
bb-m-labs: force build --props=package=llvmlite-artiq conda-win64
<bb-m-labs>
build forced [ETA 1h34m44s]
<bb-m-labs>
I'll give a shout when the build finishes