<Fallenou>
I think it's one third political, one third "marketing is good if it makes people talk about it", one third Carla is a very good friend of the boss's wife
__del__ has quit [Quit: Leaving.]
<lekernel>
"there's no such thing as bad publicity"? :-)
<Fallenou>
I guess that's what marketing department think =)
<Fallenou>
but I really have no clue about marketing
<Fallenou>
I can say that the headphone works quite well :)
<Fallenou>
a lot of nice gadget features (detection of whether it's on your head or around your neck, touch sensitive commands for pause/resume/next/previous/volume-up/volume-down) etc
<Fallenou>
lekernel: why going back to gcc?
<Fallenou>
problems with clang?
<lekernel>
yeh
<lekernel>
it's actually quite a mess too...
<lekernel>
two build systems (autocrap + cmake), bugs that appear only with one of them
<lekernel>
sometimes horrible c++ code
<lekernel>
look at the clang driver for example :) thousands of lines of C++ mess that ought to be replaced with 200 lines of python
<Fallenou>
oh :( I had faith in a good almighty replacement for gcc
<Fallenou>
too bad
<lekernel>
and finally, the lm32 backend has its share of bugs too, and generates suboptimal code (even more so for lm32 than for other platforms, _of course_)
<lekernel>
I'll just give up and stick with an old gcc...
<Fallenou>
anyway, I kind of start understanding your resentment for autocrap as I am studying netbsd build system and trying to understand how to make a lm32 port
<Fallenou>
netbsd build system itself seems really clean
<Fallenou>
but to build gcc/binutils it calls autotools of those packages and the hell starts there
<Fallenou>
what's great is that netbsd uses gcc 4.5.3 :)
<lekernel>
btw - do you remember if SDRAM worked with milkymist-ng during the workshop?
<Fallenou>
so far I only ran the BIOS during the workshop
<Fallenou>
it uses SDRAM, right ?
<lekernel>
it will initialize and test it
<lekernel>
did it try to boot from the network?
<Fallenou>
I don't remember :/
<Fallenou>
Do you know the difference between lm32--rtems , lm32--elf, and lm32--uclinux toolchains?
<Fallenou>
it seems gcc defines those three as possible lm32 toolchains
<Fallenou>
I don't really understand the meaning of the latest word in toolchains
<Fallenou>
like what would it mean to have a lm32--netbsd toolchain or a lm32--netbsdelf one
<Fallenou>
what kind of job needs to be done etc
<lekernel>
it defines what libraries and linker scripts are used by default
<Fallenou>
it seems there is no such documentation about that
<lekernel>
include path too
<lekernel>
do you have the -ng or old bios flashed on your board?
<Fallenou>
I have -ng BIOS
<Fallenou>
I'm not at home though, so I don't have the board nearby
<lekernel>
can I send you a test bitstream?
<lekernel>
I'm tracking down an annoying sdram bug atm...
<Fallenou>
but I can try something on monday afternoon (after 19h)
<Fallenou>
yes of course :)
<lekernel>
thx
<lekernel>
just let me know if the init passes in the bios
<Fallenou>
ok
<Fallenou>
(about netbsd) so far I succeeded in making netbsd build system understanding the existence of lm32 arch, and generating a lm32--elf toolchain before trying to build (and fail) the rest of the Operating System
<Fallenou>
it's like buildroot build system, it builds the toolchain before building the OS :)
<Fallenou>
very nicely done
<Fallenou>
it even works on Mac OS X
<Fallenou>
is there any "gcc" hacker/developper in the Milkymist community?
xiangfu has quit [Quit: leaving]
<lekernel>
hmm, I'd rather start with just the kernel... do you need the whole build system for it?
<Fallenou>
it seems so
<Fallenou>
I don't even know yet how to only build the kernel
<Fallenou>
I only found so far this command : ./build.sh -U -m lm32 build
<Fallenou>
which builds toolchain + kernel + basic operating system (shell/unix basic tools/basic netbsd tools)
<Fallenou>
brb
<wpwrak>
Fallenou: welcome to the autocrap haters club :)