<kristianpaul> phew... long day no internet link near
<kristianpaul> oops wrong chan :)
<xiangfu> the milkydrop have so many patches. :D
<kristianpaul> from winamp timess? :)
<wolfspraul> xiangfu: just be careful about licenses
<wolfspraul> if you plan to milkymistify some of them
<xiangfu> yes.
<wolfspraul> check that it is properly licensed as open source or free software, and make sure we carry attributions of the original authors along properly
<xiangfu> I am try some of them on milkymist now.
<wolfspraul> when in doubt, don't use it. try to contact the author first. once you get an email permission you are always good to go.
<xiangfu> some of them works totally different. :)
<wolfspraul> (repeating)
<xiangfu> yes. sure
<wolfspraul> anything that looks different is good :-)
<wolfspraul> just like I said, please let's do high quality work on the license and attribution side too
<wolfspraul> sometimes creative people don't care much, they just 'release' their stuff on the web
<wolfspraul> without any license information, even without contact links or author information
<wolfspraul> we should not incorporate such works into Milkymist One, if the licensing status is unknown/unclear, don't use it
<wolfspraul> in such cases, try to contact the author in some efficient way. if you hear back great, otherwise we won't use it.
<wolfspraul> all of this is easier said than done :-)
<wolfspraul> nice, seems all gpl!
<wolfspraul> let's get anything that works and looks nice to m1 :-)
<wolfspraul> also email those guys (or other ways of contact), see whether anybody is still active, tell them about m1, and let's see how we can work together
<wolfspraul> most updates seem to be from 4 years ago, but some are just a few weeks old
<wpwrak> wolfspraul: (tell them about m1) perhaps the best approach for that would be to make a quick video, then mail them thanking them for their "patch" and showing them how well it renders on the M1. then let them draw their own conclusions ;-)
<wolfspraul> well, it's all work, but yes
<wolfspraul> one by one
<wpwrak> now that making good videos is within easy reach ... ;-)
<Thihi> Hiya.
<Thihi> You do some seriously whack shit.
<Thihi> Carry on.
<xiangfu> Thihi, welcome
<Thihi> Yeah, I did, you showed me on the Other Channel. ;P Pretty cool.
<lekernel> hi
<lekernel> is back from scandinavia
<wolfspraul> lekernel: how was it?
<wolfspraul> lekernel: xiangfu found a cheap 15 USD vga->cvbs converter thanks to Joerg's advice, it's fun
<lekernel> it was great... small, underground, a lot of fun
<lekernel> yeah, there are cheap converters like that
<lekernel> but with some fpga design work it can be done with a $1 converter as well *g*
<Thihi> lekernel, what were you doing in scandinavia?
<lekernel> I used one already
<wolfspraul> lekernel: yes but this may allow us to make higher quality videos now
<lekernel> Thihi, going to hacknight.se and visiting friends
<xiangfu> Thihi, we are try to build the hardware for people like you :D
<wolfspraul> also xiangfu just noticed it can switch between pal and ntsc and shows some bugs with ntsc :-) (or probably bugs)
<Thihi> Nice.
<lekernel> wolfspraul, higher quality? CVBS _reduces_ quality compared to VGA
<wolfspraul> lekernel: quick update on the production side. roh's first box with cases has arrived in Taipei, but not through customs yet
<wolfspraul> well
<Thihi> xiangfu, well, I really just use straight projector / camera feedback, and nothing else. So not really for me, although I do see the appeal in what you do.
<wolfspraul> the best videos we had so far were taking with a camera on a tripod :-)
<wolfspraul> of course with a vga grabber would be better but neither me nor xiangfu have one or plan to buy one
<lekernel> I have tried NTSC once, and it worked for me... without bugs
<wolfspraul> so compared to a camera on a tripod filming an LCM, it might be better :-)
<lekernel> but of course it seems I never get the bugs here *g*
<lekernel> they kick in later and waste tons of time
<Thihi> xiangfu, I might get interested later on, though, but I have this big project I'm going to do with the stuff I've gathered so far, that'll prolly take me a long time to finish. I might get it out next summer or so, and before that I won't prolly have any time for anything besides work and the wife. :)
<lekernel> wolfspraul, so how do you record the video then? VGA -> CVBS converter -> digital camera with a CVBS input?
<wolfspraul> the shipment of boxes and lots of print material should go out to Taipei any day now, it's a big box and needs a little planning to be economic
<wolfspraul> adam got the boards from minbo back (schmitt-trigger rework), just 2 hours ago, and very soon we know the results from that detour
<wolfspraul> no vga -> cvbs -> back to usb :-)
<wolfspraul> it's a test
<wolfspraul> but the 2 converters cost only 15-20 usd each, which is nice
<lekernel> back to USB? so you have a USB frame grabber with CVBS in?
<wolfspraul> yes
<lekernel> ah, ok
<wolfspraul> the difference is that that frame grabber costs 15 usd
<lekernel> yeah, that would work better than filming a screen :)
<lekernel> ok, i see
<wolfspraul> we will find out the downsides soon
<wolfspraul> yes we need better videos, working on it
<lekernel> the only obvious downside is the video quality is lower than a VGA frame grabber
<lekernel> but if the whole thing costs 40-30 usd and also provides cvbs out, it's still good value for money
<lekernel> 40-30
<lekernel> has been doing to much *hdl
<kristianpaul> (hdl) related with radars? :-D
<wolfspraul> Milkymist One HS code is 8471.41 http://en.qi-hardware.com/wiki/Milkymist_One_accessories#HS_code
<wolfspraul> I feel good about that, let's see what customs are saying over time :-)
<wolfspraul> notebooks are normally 8471.30, I'm wondering what a desktop PC would be...
<Alarm> hi  !  This cable is the right thing for paltest?
<Alarm> This cable is the right thing?
<Alarm> http://www.google.fr/imgres?imgurl=http://imagecz.cz/media/0/produkty-kabely/Kramer_VGA_CINCH.jpg&imgrefurl=http://imagecz.cz/item/kramer-vga-cinch-rgb-yuv-delka-0-3-metru&h=374&w=500&sz=28&tbnid=QiqHW4kUGJFV9M:&tbnh=82&tbnw=110&prev=/search%3Fq%3Dvga%2Bcinch%26tbm%3Disch%26tbo%3Du&zoom=1&q=vga+cinch&docid=BVerFKYkHo0X6M&hl=fr&sa=X&ei=aCVBTtfeBIvs-gbzvsjWCQ&sqi=2&ved=0CGEQ9QEwBQ&dur=478
<lekernel> it looks good, but you can't be sure
<Alarm> lekernel: Have you the wiring of the cable?
<Fallenou> the pinout ?
<lekernel> all that is needed is VGA red channel -> CVBS RCA plug
<lekernel> you can brew your own cable if you wish
<lekernel> check pinouts.ru (for example)
<Alarm> 1 RED --> Red Video (75 ohm, 0.7 V p-p) ?
<Alarm> ok
<lekernel> anyone got a working kernel (including framebuffer) + openwrt initrd binaries for demo at the ccc camp?
<Alarm> lekernel: I have a beautiful checkerboard :)
<Alarm> black anh white
<lekernel> yup :)
<lekernel> that's what it's supposed to do
<lekernel> now you can play with the verilog source if you wish
<Alarm> thank you :)
<Alarm> I have a problem to compile flickernoise: http://pastebin.com/6s4nzkbx
<lekernel> larsc, are you going to the ccc camp?
<lekernel> who else? mwalle?
<Alarm> Nobody Inpiration by my failure of "make flickernoise"?
<GitHub80> [clang-demos] jpbonn created master (+1 new commit): https://github.com/milkymist/clang-demos/compare/cf264b8^...cf264b8
<GitHub80> [clang-demos/master] Added clang "hello world" sample. - JP Bonn
<jpbonn> did you follow the "Automatic Build" directions at http://www.milkymist.org/wiki/index.php?title=Flickernoise_build_instructions
<Alarm> I have created the environment variables. I executed 'make-C compile-flickernoise flickernoise.fbi'
<jpbonn> were you in the scripts directory?
<lekernel> of course, distros are ignoring lm32 ... http://packages.debian.org/experimental/i386/qemu-system/filelist
<lekernel> phew
<Alarm> I copied the contents of the scripts in rtems-4.11
<jpbonn> That's not in the directions.  Follow the directions - they should work. See http://www.milkymist.org/wiki/index.php?title=Flickernoise_build_instructions to get the scripts and then follow the README.html file that was checked out from git.
<larsc> lekernel: i won't be at the camp
<lekernel> i mailed the fedora and debian maintainers
<lekernel> what a mess...
<Alarm> jpbonn: Sorry but I do not know where to script the directory must be copied to the recommendations of the README.html? At the root /?
<jpbonn> Alarm: Do not copy anything. Did you do the "automatic build" steps at http://www.milkymist.org/wiki/index.php?title=Flickernoise_build_instructions ?
<Alarm> jpbonn: If you're in your home, 'git clone git: / / github.com / Milkymist / scripts.git installs scripts in home so I ask again the scripts must be installed where?
<jpbonn> Alarm: the home directory is fine.  There's no need to copy it.
<Alarm> jpbonn: If I am in my home directory, and I run 'git clone git: / / github.com / Milkymist / scripts.git' Script directory is installed in my home directory. In this case, I'm having a problem to run scripts to install in / opt/rtems-41.11?
<jpbonn> Alarm: README.html: 2. Make sure you have write access to `/opt/rtems-4.11'
<jpbonn> Alarm: README.html:The scripts checkout the milkymist git repository to "../" so you need write access to the parent directory from where you issue the following commands
<Alarm> jpbonn: read this recommendation but it is not clear to me?
<jpbonn> Alarm: ignore it for now.  I'm actually not sure if it's referring to the parent of the scripts directory or not. If you run into permissions problems you can fix it later.
<Alarm> Well I'm going to sleep the body Tomorrow is another day
<mwalle> lekernel: im on vaction by the end of the week :)