Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
Freemor joined #qi-hardware
rzk joined #qi-hardware
wolfspraul joined #qi-hardware
skynet-2000 joined #qi-hardware
wolfspraul joined #qi-hardware
<PiLeS> More seriously but in the same vein, I reckon that releasing a ready-made minimal toolchain that would allow compilation FOR the Ben FROM the Ben would be a Good Thing (TM). I know of some people (including me) who would spend more time working on ports if it didn't take up >2 GB and -more importantly- precious CPU cycles from my^H^Htheir money-generating workstation.
<PiLeS> just sayin'
<wolfspraul> PiLeS: totally hear you
<wolfspraul> one reason we had to kick out gcc from the standard image once was that the 512mb rootfs was full
<wolfspraul> it's hovering around 480mb now, basically whenever we add something nice we have to think what else to remove
<wolfspraul> sure things are installable with opkg, but that requires work to setup and is generally more inconvenient than if things are preinstalled
<wolfspraul> thanks to work from David and Lars the nand and ubifs are so fast now that we could easily mount the entire 2gb
<wolfspraul> but how to switch from 512mb to 2gb without breaking compatibility for a lot of people, that's tough
<wolfspraul> once at the beginning we switched from 256mb to 512mb, and it took more than a year until finally people didn't run into bugs related to that switch anymore
<PiLeS> Maybe what is needed is some form of classification in the packages; a bit like what the Debian guys did, but better ;)
<PiLeS> Anyway, that wasn't my point.
<wolfspraul> PiLeS: huh? what was your point then?
<PiLeS> opkg is easy enough as it is
<wolfspraul> ok
<PiLeS> I was dreaming
<wolfspraul> which tools are you missing?
<wolfspraul> that's good
<wolfspraul> my dream Ben has gigaherz-anything and can do everything
<PiLeS> erm
<wolfspraul> :-)
<PiLeS> the tools that I'm missing right now (and that I'm too lazy/busy/important/stupid/pick-any to develop by myself is a full xburst toolchain image for the Ben
<PiLeS> Or maybe it is around and I missed it?
<wolfspraul> xburst-toolchain, what do you mean exactly?
<wolfspraul> we have gcc, we are probably weak on headers and libraries
<PiLeS> These are building blocks. They are fine. I was thinking more along the lines of that: http://en.qi-hardware.com/wiki/Building_OpenWRT_on_Debian_6
<PiLeS> but for the Ben.
<PiLeS> That's some work
<PiLeS> but it will draw the geeks like honey does for flies.
<PiLeS> Free labour!
<wolfspraul> you mean you want to build the entire image on the Ben?
<wolfspraul> run openwrt on ben? :-)
<PiLeS> And by For the Ben I really mean FROM the Ben
<PiLeS> Yup
<PiLeS> Maybe not the full image, that's where classification kicks in
<wolfspraul> I think openwrt has some pretty cool online image generators now
<wolfspraul> unfortunately I forgot the url, lemme see whether I can find it somewhere
<wolfspraul> it's different from your idea but it also offloads building from your notebook/desktop
<wolfspraul> just not onto the Ben, but in the other direction (cloud :-))
aw joined #qi-hardware
aw_ joined #qi-hardware
<PiLeS> Nice.
wolfspraul joined #qi-hardware
<PiLeS> But that's still not what I meant.
<PiLeS> Anyway, just throwing ideas in the air, looking at how they fly ;-)
xiangfu joined #qi-hardware
<PiLeS> The self-contained idea would appeal to geeks and devs with time to spare; no?
freakazoid0223 joined #qi-hardware
<PiLeS> I would most certainly devote my spare Ben to that! ;-)
<wolfspraul> don't know
<wolfspraul> we are talking about smart and imaginative people, they see something in the future
<wolfspraul> which excites them
<wolfspraul> but the excitements may differ a lot, because the future is so unclear and so full of possibilities :-)
<wolfspraul> so yes I can definitely *imagine* that some people get excited about this idea
<wolfspraul> not me though, at least not today. I have no problem with the idea of moving the building into the cloud, to powerful servers.
<wolfspraul> I rather have a great buildhost with gui, like the openwrt link I posted.
<PiLeS> well, I do
<wolfspraul> oh sure, please do
<wolfspraul> you asked me, so I answer :-)
<wolfspraul> for myself
<wolfspraul> think about the Milkymist One case
<wolfspraul> build the bitstream on the M1? the synthesis tools?
<wolfspraul> those are nice *ideas*, but not more than that. It will not happen for x years.
<PiLeS> Not the same thing
<wolfspraul> I can be motivated about something I can reach in 1 week, 1 month, maybe 3 months.
<PiLeS> Hey! You're a human being! ;-)
<wolfspraul> there are many things in-motion. embedded devices become more powerful, making them better targets for full distros, or be able to build all software on them
<wolfspraul> on the other side there are always yet more embedded devices appearing, with more integration, or specialized tools that need a powerful host computer, for now
<wolfspraul> so you need to think about the time horizon that motivates you
<wolfspraul> and I think you do :-)
<wolfspraul> otherwise you wouldn't be chatting with me here, you would be hacking on your idea
<wolfspraul> but your idea is impractical in the short run, so you kinda don't want to start :-)
<wolfspraul> if your goal is to make the Ben be able to build an entire Ben image on itself - GO FOR IT!
<wolfspraul> I am not stopping you
<wolfspraul> but you will be on this for a few months, maybe years?
<wolfspraul> so maybe you are not so excited about it, after all
<wolfspraul> we see :-)
<PiLeS> powerful host computer my shiny ass. This mighty old workstation was built by Michael Dell's tiny helper-hands 12 years ago.
<PiLeS> Also, Chatting while said workstation builds stuff...
<PiLeS> :-*
<wolfspraul> ok, but you want to run it on the Ben or not?
<PiLeS> I told you, I am a dreamer
wolfspra1l joined #qi-hardware
wolfspraul joined #qi-hardware
<PiLeS> maybe I am not so excited. Maybe I am not worth. Maybe I should step down. Maybe Seppuku is in order.
<PiLeS> Maybe I should go to bed now, and be thankful for having a GF.
<PiLeS> Or maybe I should try and be more helpful, fuck girls, who needs them?
rejon_ joined #qi-hardware
<PiLeS> Kuessen. Guten nacht.
<kyak> wpwrak: there is such script, but is it too hard to replace in mind? :)
DocScrutinizer joined #qi-hardware
kristianpaul joined #qi-hardware
wolfspraul joined #qi-hardware
skynet-2000 joined #qi-hardware
stefan_schmidt joined #qi-hardware
kristianpaul joined #qi-hardware
jekhor joined #qi-hardware
dvdk joined #qi-hardware
<dvdk> wolfspraul: reading through the IRC logs;
<dvdk> wolfspraul: about the problem with limited space in 512 mb UBIFS partition:
<wpwrak> kyak: not too hard. but it's kinda cute if the machine does it for you ;-)
<dvdk> why don't we release multiple differently sized images, like one 512 mb "medium" image, and another 1GB "large" image with more packages included?
<dvdk> shouldn't be too difficult from the toolchain point of view. all these packages are built anyway, so throwing them into another, larger image shouldn't break anything
<dvdk> hmm, but size of the mtd partitions is fixed in the kernel? would need two corresponding versions for the kernel?
mstevens joined #qi-hardware
skynet-2000 joined #qi-hardware
skynet-2000 joined #qi-hardware
<wolfspraul> dvdk: yes, fixed partition sizes
wolfspraul joined #qi-hardware
<kyak> not this partition discussion again :)
jivs joined #qi-hardware
<dvdk> wolfspraul: can't this be passed in from the boot loader? On PPC there is usually a device-tree file passed to the kernel that configures mtd partitioning
<dvdk> kyak: :)
antoniodariush joined #qi-hardware
jivs joined #qi-hardware
<roh> dvdk: there is no device tree on mips afaik
<roh> blogic was working on something there.. for a different mips device. maybe we should wait for his work and then followup
<dvdk> i didn't call for a full device tree for mips. just for some config to pass from boot loader to kernel...
<dvdk> maybe cmdline would do?
<roh> well.. wouldnt be the worst idea to do proper devicetree and wait till then. lets wait what blogic has to say
<mth> there is already a config option to parse mtd partitioning from the kernel command line, afaik
<dvdk> well, then problem solved? For a "big" installation we'd only have to change uboot env. vars and install the larger root ubifs, no?
wolfspraul joined #qi-hardware
<mth> probably; I haven't used the feature yet, but I saw it when browsing menuconfig
Ayla joined #qi-hardware
wolfspraul joined #qi-hardware
jekhor joined #qi-hardware
wolfspraul joined #qi-hardware
wolfspraul joined #qi-hardware
wolfspraul joined #qi-hardware
antoniodariush joined #qi-hardware
kristoffer joined #qi-hardware
<kyak> how do oy ulike it, wpwraks?
<kyak> s/oy/you/s/ulike/like/s/wpwraks/wpwrak
<qi-bot> kyak meant: "how do you like it, wpwrak?"
<kyak> now, it must do the same, but automatically :)
<kyak> drunk speech translator
jivs joined #qi-hardware
woakas joined #qi-hardware
<wpwrak> kyak: ah, nice...
<wpwrak> s/ah/wheee/s/nice/EXCELLENT/s/.../!!11!/
<qi-bot> wpwrak meant: "!!11!!!11!!!11!!!11!!!11!!!11!!!11!!!11!."
<wpwrak> hmm :)
<wpwrak> close ;-)
antoniodariush joined #qi-hardware
<blogic> roh: yes
<blogic> i have experimental patches for DT on MIPS
<blogic> lmo will switch all devices to DT and not accept new target unless they are DT conformant
Textmode joined #qi-hardware
urandom__ joined #qi-hardware
rzk joined #qi-hardware
paroneayea joined #qi-hardware
emeb joined #qi-hardware
vladkorotnev joined #qi-hardware
paroneayea joined #qi-hardware
vladkorotnev left #qi-hardware
erikkugel joined #qi-hardware
<erikkugel> Hi guys, just a quick question about building the software image. When I run make, config still asks something around 20 question about various modules, including Ethernet Gadget, ALSA and LCD. I'm curious if anyone else had seen this? I'm building the latest Novermber image...
dptech joined #qi-hardware
<dvdk> erikkugel: I guess the kernel config is just not up to date with the kernel version used. slightly unclean. the proper fix is usually to run 'yes "" | make config' or something to update the config for the newer kernel (applying defaults)
freakazoid0223 joined #qi-hardware
<erikkugel> That sounds great, I'll try it out, the main reason I'm asking is for the Debian script we have on the wiki. Thanks for the lead dvdk!
Ayla joined #qi-hardware
jekhor joined #qi-hardware
erikkugel left #qi-hardware
<qi-bot> [commit] Werner Almesberger: m1/patches/rtems: added milkymist-midi-opt.patch (master) http://qi-hw.com/p/wernermisc/f331607
<qi-bot> [commit] Werner Almesberger: midigen/: MIDI traffic generator (master) http://qi-hw.com/p/wernermisc/395458b
arti joined #qi-hardware
arti left #qi-hardware
zedstar joined #qi-hardware
rzk joined #qi-hardware
wej joined #qi-hardware
wejp joined #qi-hardware
freakazoid0223 joined #qi-hardware
<kristianpaul> wpwrak: you sent M1 related patches to qi list and not copy to mm dev list for some sepacial reason?
<wpwrak> argh
<wpwrak> they were meant to go to the other list, of course
<kristianpaul> sure :-)
<kristianpaul> s/sepacial/special
<wpwrak> thanks for the heads up ! :)