| kristianpaul | xiangfu: morning | 01:25 |
|---|---|---|
| xiangfu | kristianpaul: good morning | 01:26 |
| kristianpaul | wich mupdf version are you using for flickernoise btw? | 01:26 |
| xiangfu | I am using 0.8 | 01:26 |
| kristianpaul | okk | 01:27 |
| aw_ | morning | 01:34 |
| aw_ | anyone know how to capture that video from GUI tool? | 01:35 |
| kristianpaul | hi adam :-) | 01:35 |
| kristianpaul | I think video sample to a file is not implemented, just screenshot of a vide preview | 01:36 |
| kristianpaul | arg | 01:43 |
| kristianpaul | gg | 01:43 |
| kristianpaul | hmm http://paste.debian.net/113963/ | 01:44 |
| xiangfu | kristianpaul: update your mtk. | 01:47 |
| kristianpaul | shit, yes | 01:48 |
| kristianpaul | i toucht i did it.. | 01:48 |
| aw_ | kristianpaul xiangfu , how to use screenshot on M1 gui? | 01:48 |
| kristianpaul | tought* | 01:48 |
| aw_ | plugging keyboard? | 01:49 |
| kristianpaul | control + f12 i remenber | 01:49 |
| kristianpaul | xiangfu: ? | 01:49 |
| Action: kristianpaul still updating about last hw/sw changes on m1 | 01:50 | |
| aw_ | what's *.per file when using save? | 01:55 |
| xiangfu | multi patch performance is soooooo cool. | 02:03 |
| xiangfu | wow. with "multi patch performance" I can be a VJ :D | 02:12 |
| kristianpaul | :o | 02:13 |
| larsc | hehe | 02:15 |
| xiangfu | (I may need a BIG projector :) | 02:16 |
| kristianpaul | xiangfu: multi patch is in last msd? | 02:19 |
| xiangfu | kristianpaul: switch the 'patch performance' with keyboard shortcut. | 02:21 |
| xiangfu | kristianpaul: open the 'keyboard' bind the 'key' to 'patch' | 02:22 |
| kristianpaul | oh | 02:22 |
| kristianpaul | cool, i tought it just was posible with midi | 02:22 |
| kristianpaul | okay, now i need a portable keyboard ;) | 02:23 |
| xiangfu | kristianpaul: http://en.qi-hardware.com/wiki/Milkymist_One_accessories | 02:26 |
| kristianpaul | how do you created data partition? | 02:27 |
| kristianpaul | nice ! | 02:31 |
| kristianpaul | i can take screenshot finally :-) | 02:31 |
| kristianpaul | and ftp transfer was not bad | 02:31 |
| xiangfu | kristianpaul: data partition is mount by default. | 02:34 |
| xiangfu | 1. you can copy file to /flash/ | 02:34 |
| kristianpaul | no, i mean m1.flash5.bin | 02:34 |
| xiangfu | 2. or reflash it :) | 02:34 |
| xiangfu | kristianpaul: http://downloads.qi-hardware.com/people/xiangfu/milkymist-one/2011-04-06/flash.data | 02:36 |
| kristianpaul | yeah, but how i do create the m1.flash5.bin file? | 02:36 |
| xiangfu | kristianpaul: https://github.com/milkymist/scripts/blob/master/build#L74 | 02:42 |
| kristianpaul | Minimac RX FIFO overflow! | 02:42 |
| kristianpaul | Warning: out of RX buffers to refill slot E0008008! | 02:42 |
| kristianpaul | Warning: out of RX buffers to refill slot E0008014! | 02:42 |
| kristianpaul | Warning: out of RX buffers to refill slot E0008020! | 02:42 |
| kristianpaul | Warning: out of RX buffers to refill slot E000802C! | 02:42 |
| xiangfu | kristianpaul: you should update all milkymist git repo. then rebuild all image. | 02:43 |
| xiangfu | kristianpaul: I rare meet this error after update. | 02:43 |
| xiangfu | kristianpaul: or you can try : http://downloads.qi-hardware.com/software/images/Milkymist_One/latest/ :) | 02:44 |
| kristianpaul | ok | 02:44 |
| kristianpaul | well actually sintesis just finished :-D | 02:44 |
| kristianpaul | i wonder if build_bitstream.sh is usable or i should always go to /home/paul/milkymist/boards/milkymist-one/flash | 02:54 |
| aw_ | xiangfu, http://downloads.qi-hardware.com/people/adam/m1/pic/M1_Screenshot_casio_ex-z200.png | 03:09 |
| kristianpaul | xiangfu: wich scripts are you using for making that last images? | 03:10 |
| kristianpaul | script order too.. | 03:10 |
| xiangfu | kristianpaul: all images? | 03:11 |
| kristianpaul | xiangfu: yes | 03:11 |
| xiangfu | kristianpaul: I using mine: https://github.com/milkymist/scripts/blob/master/build | 03:11 |
| kristianpaul | hmm okay | 03:12 |
| kristianpaul | nice | 03:12 |
| kristianpaul | i need that, i was crazy compiling all this from scratch some hrs ago | 03:12 |
| kristianpaul | i dont get why i need a MMU beyond the fact running linux is good, but yeah, talk on ML looks interesting | 03:28 |
| kristianpaul | aw_: you are genious !!! | 03:30 |
| kristianpaul | ALL this time i had a canon cemra with A/V out, and now i realized i can plug it on the MM1 :( | 03:31 |
| kristianpaul | as you can see on irc i always had the video out with my camera.. :( | 03:32 |
| aw_ | kristianpaul, all i did was xiangfu taught me! :-) | 03:35 |
| aw_ | kristianpaul, since i have to recognize how MM1's goes before/after i add parts on video circuit path. so I asked xiangfu that how i can capture video snap on gui. :-) | 03:40 |
| xiangfu | just create an empty page: http://www.milkymist.org/wiki/index.php?title=Flickernoise_user_manual | 03:42 |
| xiangfu | we should add the 'multi patch performance' to this page :) | 03:43 |
| wolfspraul | xiangfu: I had another idea :-) after booting, m1 should automatically start with a patch, or even randomly picking one and then randomly continuing with others | 03:46 |
| wolfspraul | or if it's possible, after booting it should continue with whatever it did before the last power off | 03:46 |
| xiangfu | I was thinking auto select one. not auto start :) then when you click "start!" no needs to select. | 03:48 |
| aw_ | xiangfu, http://downloads.qi-hardware.com/people/adam/m1/pic/M1_Screenshot_360x288_casio_ex-z200.png | 03:48 |
| wolfspraul | xiangfu: I think the best would be if m1 continued with whatever it was doing before the last power-off | 03:49 |
| wolfspraul | maybe with some way to escape from the loop, so people cannot get stuck in a crash | 03:49 |
| kristianpaul | xiangfu: i did | 03:49 |
| kristianpaul | eraseflash 0xD20000 151 | 03:49 |
| kristianpaul | flashmem 0xD20000 data.flash5.bin noverify | 03:49 |
| kristianpaul | but got /flash empty | 03:49 |
| wolfspraul | but other than that I think that would be good. if it was in the GUI - back to gui. if it was running some patch X, back to patch X. if it was running multiple patches, back to the same set. etc. | 03:49 |
| xiangfu | kristianpaul: how you create the data.flash5.bin . there is one parameter "convert" like | 03:50 |
| xiangfu | kristianpaul: mm-mkyaffs2image /PATH data.flash5.bin convert <---- | 03:51 |
| xiangfu | kristianpaul: I should make the 'convert' as default. since we don't have a LE m1 | 03:51 |
| kristianpaul | ah, you mean http://downloads.qi-hardware.com/software/images/Milkymist_One/latest/reflash_m1.sh was not already converted? | 03:53 |
| xiangfu | kristianpaul: it's already converted. I though you are create by yourself. sorry. | 03:54 |
| kristianpaul | not, i just get it from that url.. | 03:54 |
| wolfspraul | kristianpaul: so you found out now that you can connect your Canon camera to the m1? | 03:56 |
| kristianpaul | my first screenshot :D http://downloads.qi-hardware.com/people/kristianpaul/Screenshot-00.png | 03:56 |
| wolfspraul | how much better is the Canon cam, in an actual video-in patch, as compared to the best ccd mini camera you got? | 03:57 |
| kristianpaul | hmm , wait i need upload a video patch first ;) | 03:57 |
| kristianpaul | xiangfu: how i can make a the vide-in preview? | 04:00 |
| kristianpaul | i was swiching to low resolution, but that not make sense.. | 04:00 |
| xiangfu | kristianpaul: sorry. what you mean? | 04:00 |
| kristianpaul | oh sorry, | 04:01 |
| kristianpaul | is it posible to make video-in preview bigger? | 04:01 |
| xiangfu | kristianpaul: (flash data) compare the md5sum. try again. so far it works fine here. | 04:01 |
| xiangfu | kristianpaul: yes. http://downloads.qi-hardware.com/people/xiangfu/tmp/video-in-switch-resolution.tar.gz | 04:02 |
| xiangfu | kristianpaul: you can switch 360x288 -- 180x144 with this bin. but there is a bug. only can switch 32 times | 04:02 |
| xiangfu | kristianpaul: http://downloads.qi-hardware.com/people/xiangfu/tmp/big-video-in.tar.gz this one is hardcode only big video-in 360x288 | 04:03 |
| wolfspraul | xiangfu: ahh! :-) so the video-in-switch-resolution is the newer one? | 04:03 |
| xiangfu | wolfspraul: yes. but a bug :) | 04:04 |
| xiangfu | switch 32 times :( | 04:04 |
| wolfspraul | does video-in-switch-resolution replace the older one? | 04:07 |
| wolfspraul | if so, just delete the older one | 04:07 |
| wolfspraul | even if someone runs into it (unlikely), it is better to delete known bad stuff than to let people fall into a trap | 04:07 |
| wolfspraul | these are just temporary/personal builds anyway... | 04:08 |
| xiangfu | I add that one for back the source code patch. | 04:12 |
| xiangfu | wolfspraul: when I move the big video-in preview. I can feel that is slow then the small one. | 04:13 |
| wolfspraul | ok sure. I don't feel very strongly that a larger preview-in needs to be the default, I just need it for some camera comparison screenshots. | 04:15 |
| wolfspraul | not worth further discussions... | 04:15 |
| wolfspraul | (for me at least :-)) | 04:16 |
| wolfspraul | I'm curious what Sebastien thinks about the m1 after booting going back to what it did before last power off. | 04:16 |
| wolfspraul | I think that would be a cool feature with real end user value. | 04:16 |
| wolfspraul | we find out later :-) | 04:17 |
| xiangfu | yes. | 04:23 |
| xiangfu | for now. too bad. after reboot. all keyboard bindings are lose :( | 04:23 |
| wolfspraul | it should remember 'the whole' state over power cycle | 04:24 |
| xiangfu | 'DMX desk' setting lose too. | 04:25 |
| wolfspraul | I think we first define the goal. I think it should remember the full state and go back to do exactly what it did before. | 04:42 |
| wolfspraul | if Sebastien agrees, then we can start with the most important settings/states first, and then the more advanced ones | 04:42 |
| kristianpaul | btw i noticed i have to reboot with the video camera connected in order to the patches to work well | 04:54 |
| kristianpaul | this is when changing resolution | 04:54 |
| wolfspraul | yes I also noticed some strangeness in the video-in signal not being detected unless I reboot | 04:55 |
| wolfspraul | but I didn't have the time yet to track it down into a proper reproducible procedure... | 04:56 |
| wolfspraul | or maybe what I saw was that plugging the camera in hung the entire m1, when I was in the preview dialog already I think. I need to make it properly reproducible first. All small bugs I think. | 04:56 |
| lekernel | for large video in preview just use a patch | 06:59 |
| lekernel | video_a=1 | 06:59 |
| lekernel | decay=0 | 07:00 |
| lekernel | this will put the video in fullscreen with no effect | 07:00 |
| lekernel | and with hardware acceleration so this will get a good framerate - not like the preview dialog | 07:00 |
| aw_ | good, but modify video_a=1, decay=0 to which file? | 07:01 |
| lekernel | xiangfu: "flickernoise user manual" goes here: https://github.com/milkymist/flickernoise/tree/master/doc | 07:02 |
| lekernel | aw_: in the patch editor | 07:02 |
| xiangfu | lekernel: yes. try to compile that file. meet some errors.http://pastebin.com/vziTG6cy | 07:04 |
| aw_ | after added V9MLA0402LNH, http://downloads.qi-hardware.com/people/adam/m1/pic/M1_Screenshot_360x288_V9MLA0402LNH_casio_ex-z200.png | 07:10 |
| aw_ | if using fullscreen is good to compare. :-) | 07:11 |
| xiangfu | aw_: full screen is much better. | 07:12 |
| aw_ | hmm...but i haven't learned that how to use patch editor. :( | 07:13 |
| xiangfu | lekernel: if you don't mind . I would like to commit one file like: | 07:13 |
| xiangfu | more LeKernel\ -\ FullScreen\ Video-in\ Preview.fnp | 07:13 |
| xiangfu | video_a=1 | 07:13 |
| xiangfu | decay=0 | 07:13 |
| xiangfu | to the .../patches/Simple | 07:14 |
| aw_ | xiangfu lekernel thanks, i got my fullscreen snapshot http://downloads.qi-hardware.com/people/adam/m1/pic/M1_Screenshot_fullscreen_V9MLA0402LNH_casio_ex-z200.png | 08:08 |
| aw_ | i am wondering that how i can get a video source with http://en.wikipedia.org/wiki/File:SMPTE_Color_Bars.svg | 08:10 |
| aw_ | to test our video-in circuit. man! i need to think about this. | 08:10 |
| xiangfu | aw_: how about same that picture to your camera :) | 08:12 |
| aw_ | xiangfu, yup..just need to 'feed' SMPTE color bar into our connector J18's 'green' one. i.e. we needs a camera source it can generates a standard color bar pattern. | 08:14 |
| aw_ | i can download color bar sources from web somewhere. but this likes you surveys a VGA >> S-video & composite video RCA out, then connects it into our M1. :-) | 08:16 |
| aw_ | well...this conversion kit won't be a pure color bar source. | 08:17 |
| xiangfu | ok | 08:20 |
| aw_ | xiangfu, what's this possible err? http://pastebin.com/BYqgak2r | 09:24 |
| aw_ | xiangfu, my flash chip is likely dead? | 09:25 |
| xiangfu | aw_: I am not sure. I advice just reboot and try again | 09:27 |
| lekernel | xiangfu: yes you can add in /patches/simple | 10:12 |
| CIA-48 | flickernoise: Xiangfu Liu master * r0291ca6 / patches/Simple/Lekernel - FullScreen Video-in Preview.fnp : add one patch file for FullScreen Video-in Preview - http://bit.ly/gu8VMT | 10:13 |
| xiangfu | :) | 10:13 |
| lekernel | xiangfu: you're probably missing some latex packages... but I don't know which one. tbh I'm also struggling with latex at times | 10:53 |
| lekernel | xiangfu: try that http://packages.debian.org/search?searchon=contents&keywords=pplr7t&mode=filename&suite=stable&arch=any | 10:54 |
| xiangfu | lekernel: yes. I am google a lot. install about 200M package. seems still miss some font package. | 10:54 |
| lekernel | the first error you get is "! I can't find file `pplr7t'." which should be solved with that package... | 10:55 |
| xiangfu | lekernel: thanks, installing | 10:55 |
| xiangfu | another 30MB :) | 10:55 |
| xiangfu | lekernel: thanks. works fine now. I can get the correct pdf file. | 10:57 |
| xiangfu | after install those three package: | 10:57 |
| xiangfu | sudo apt-get install texlive-latex-recommended | 10:57 |
| xiangfu | sudo apt-get install texlive-latex-base | 10:58 |
| xiangfu | sudo apt-get install texlive-fonts-recommended | 10:58 |
| xiangfu | Output written on handbook.pdf (31 pages, 165293 bytes). | 10:59 |
| wolfspraul | lekernel: I was curious what you think about my idea that after power cycling, the m1 should go back doing whatever it did last, remembering all state info if possible | 11:02 |
| wolfspraul | if you agree with that general goal, xiangfu can slowly implement missing features in that direction | 11:02 |
| lekernel | there's already a performance autostart mode | 11:02 |
| wolfspraul | how is it invoked? | 11:03 |
| xiangfu | lekernel: there is a autostart in system settings don't know how to use that. | 11:03 |
| lekernel | should be enough for most real life purposes imo... or do you have something specific in mind? | 11:03 |
| lekernel | just select a .per multi-patch-performance file | 11:03 |
| lekernel | and it will start at boot (before displaying anything on the screen so it can be used in live contexts) | 11:03 |
| wolfspraul | ok I will try that. | 11:04 |
| wolfspraul | I was more thinking as a general idea - m1 goes back to what it did last after power cycles. | 11:04 |
| lekernel | that's a lot more complex to do with little benefits imo | 11:04 |
| xiangfu | lekernel: what is the .per file format? | 11:04 |
| lekernel | what feature would that enable? | 11:04 |
| wolfspraul | I'm not asking you to do it, I am just curious how you feel about it from a product design perspective. | 11:04 |
| lekernel | well, no matter who does it, this requires adding hooks all over the code and making it a bit messy | 11:05 |
| wolfspraul | you probably think too radical. | 11:05 |
| wolfspraul | I am just curious about how you think the user would like that behavior. | 11:05 |
| wolfspraul | or not like it | 11:05 |
| wolfspraul | always going to the same starting point also may be desirable | 11:06 |
| wolfspraul | people may get stuck in something they don't want | 11:06 |
| wolfspraul | where others may feel the product is much more robust/easy to use, if it always goes back to what it did last | 11:06 |
| lekernel | yeah, or in case of a bug, to an unrecoverable state | 11:06 |
| wolfspraul | yes but I am asking about what is desirable | 11:07 |
| wolfspraul | not for you to think through technical details | 11:07 |
| lekernel | xiangfu: when you make a multi patch perf, click "save" on the control panel and it makes such a .per file | 11:07 |
| wolfspraul | I will play with the existing gui a bit more first, there are more features I don't know well yet. | 11:07 |
| wolfspraul | like 'performance autostart mode' | 11:07 |
| wolfspraul | as a product design goal, I somehow like "go back to what it did last" | 11:08 |
| lekernel | well, don't reboot it then :) | 11:08 |
| lekernel | i'd prefer the product to be rock stable so it never has to be rebooted rather than messy "session save" code so the bugs are bearable | 11:09 |
| wolfspraul | that's why I think it's a valuable feature, because I think in real life settings, there will be a lot of unplugging, moving the box, changing power strips, etc. | 11:09 |
| wolfspraul | ah I did in no way suggest to do this to cover up crashes | 11:09 |
| wolfspraul | I am talking about product design goals | 11:09 |
| wolfspraul | in fact as you pointed out (getting into an unrecoverable state), this 'go back' thing would require a rock solid foundation to be fun to use | 11:10 |
| wolfspraul | but I am not asking you about technicalities, I'm asking about what is desirable for our users | 11:10 |
| wolfspraul | of course over time we will hear, if we ask and listen carefully | 11:10 |
| wolfspraul | but we can also have some thoughts in advance :-) | 11:11 |
| lekernel | imo the next thing that should go away in the GUI is the control panel | 11:11 |
| lekernel | it looks ugly, makes people afraid and isn't intuitive | 11:11 |
| lekernel | I'm thinking about replacing that with good looking icons describing the complete system (with lights, screen, dmx desk, camera ...) which pop up the appropriate window when you click on them | 11:12 |
| lekernel | I think this is much more important than a small detail like the session system | 11:13 |
| lekernel | people will see that instantly | 11:13 |
| wolfspraul | ok, understood | 11:13 |
| lekernel | #[~~{[#é!! what's worse than GNU/Autocrap? a customized GNU/Autocrap. | 14:20 |
| lekernel | s/ppcbe/lm32 on all autocrap scripts ftw =] | 14:24 |
| lekernel | portability layer FAIL | 14:24 |
| xiangfu | how the OSC configure in M1. it's receive data from which port? | 14:31 |
| xiangfu | 7777 :) | 14:33 |
| lekernel | yes | 14:34 |
| lekernel | on udp | 14:35 |
| lekernel | hmm... why does libgd require pthreads? | 14:49 |
| xiangfu | is there a demo/sample show how "/variable" in OSC control works under M1 ? | 15:26 |
| lekernel | not yet | 15:32 |
| lekernel | but you can e.g. take one of the DMX patches and replace "idmx" with "iosc" | 15:32 |
| kristianpaul | oh | 15:35 |
| kristianpaul | i can use osc also to transfer raw data right? | 15:35 |
| xiangfu | four kinds of data (if I am correct, from the source code) | 15:36 |
| kristianpaul | nice | 15:36 |
| xiangfu | lekernel: there are idmx1/2/3/4 , so I just replace them to iosc1/2/3/4? | 15:36 |
| xiangfu | testing | 15:37 |
| lekernel | iosc or osc... I don't remember | 15:39 |
| lekernel | then they take a float, you can try with oscsend | 15:40 |
| lekernel | you can also use the variable monitor | 15:40 |
| xiangfu | yes. I am using oscsend | 15:40 |
| kristianpaul | osc in flickernoise is a server or cliente mode? | 15:41 |
| kristianpaul | client* | 15:41 |
| xiangfu | server | 15:41 |
| kristianpaul | nice doc http://olivier.heinry.fr/public/heure-locale/heure-locale-en-public-April2011-1.pdf | 15:42 |
| xiangfu | just install the "touchOSC" in my android phone. | 15:49 |
| xiangfu | the touchOSC output format is like : http://pastebin.com/QyAjarkP | 15:49 |
| xiangfu | it is osc | 15:51 |
| xiangfu | http://en.qi-hardware.com/wiki/File:TouchOSC-control-m1-performence.ogv | 16:41 |
| xiangfu | (have to sleep. see you) | 16:41 |
| lekernel | cool vid | 16:55 |
| kristianpaul | indeed (video) | 17:20 |
| kristianpaul | xiangfu is ready for a party ;-) | 17:21 |
| lekernel | http://www.milkymist.org/mmone/milkyglow_large.png (7.8MB) | 17:22 |
| kristianpaul | nice pic, but kinda blur | 17:24 |
| kristianpaul | well, not so blur, may be tricky zoom :-) | 17:26 |
| methril_work | lekernel, any news/work with gcc 4.6? | 17:30 |
| methril_work | who is a gcc master? | 17:30 |
| lekernel | i'm not | 17:30 |
| lekernel | and tbh, don't really want to be one | 17:31 |
| methril_work | i would like to debug | 17:31 |
| methril_work | and get them compiled | 17:31 |
| methril_work | i don`t want to, but i would like to see gcc with full support :) | 17:31 |
| lekernel | otoh, if you send me a patch I can commit it to the GCC repository in less than 24 hours, which is already a progress compared to the previous LM32 situation | 17:31 |
| methril_work | nice picture, this acrylic looks better | 17:32 |
| methril_work | ok | 17:32 |
| methril_work | i see some rtems people dealing with all the newlib,gcc, binutils.... | 17:32 |
| methril_work | do you think they could help? | 17:32 |
| lekernel | you can try asking around, but keep your hopes low | 17:33 |
| lekernel | if I were you i'd rather help with the LLVM port | 17:33 |
| Action: kristianpaul likes pcc | 17:36 | |
| methril_work | i don't know anything about LLVM (neither GCC) | 17:36 |
| methril_work | but i have to deal with GCC | 17:36 |
| methril_work | we need GCC for Linux | 17:37 |
| lekernel | ok, then LLVM is clearly advantageous for you since it has documented internals | 17:37 |
| lekernel | GCC does not by FSF policy :=] | 17:37 |
| kristianpaul | oh really? what about comunity support? | 17:38 |
| lekernel | they get trolled by FSF people... hahaha | 17:38 |
| kristianpaul | :p | 17:38 |
| kristianpaul | lekernel: whats the max trougput you achived with the uart core? | 17:39 |
| kristianpaul | what was* | 17:39 |
| lekernel | about 230k | 17:39 |
| lekernel | this uart design isn't meant to be fast | 17:40 |
| lekernel | maybe you can use ethernet instead | 17:40 |
| kristianpaul | hmm i dint tested the last minimac2 revision yet | 17:40 |
| kristianpaul | but seems i should do some ttcp tests.. | 17:41 |
| methril_work | well, lekernel thak you | 17:41 |
| lekernel | haven't had any ethernet bug other than the PHY reset problem since I introduced minimac2 | 17:41 |
| methril_work | i'll do some more tests | 17:41 |
| kristianpaul | nice :-) | 17:41 |
| methril_work | and if i get tired of not finding anything, i'll try LLVM | 17:41 |
| kristianpaul | brave guy :-) | 17:45 |
| methril_work | :) | 17:46 |
| larsc | mwalle: why do we want deprecated syscalls? | 19:36 |
| larsc | or is this just for the moment so uClibc works? | 19:36 |
| mwalle | larsc: mh? which ones? | 20:21 |
| mwalle | you mean the defines? | 20:22 |
| larsc | yes | 20:24 |
| larsc | #define __ARCH_WANT_SYSCALL_DEPRECATED | 20:24 |
| mwalle | iirc uclibc needs one of those | 20:25 |
| larsc | ok | 20:26 |
| larsc | the old syscall deprecated syscall be implemented by the means of of newer ones, but i guess uClibc has support for it yet. i'll take a look | 20:27 |
| mwalle | larsc: if it can be removed, i'll happy with that ;) | 20:36 |
| lekernel | http://www.milkymist.org/desktop/out.png (to replace flickernoise control panel) | 23:10 |
| kristianpaul | what is that? i mean still tmk? | 23:16 |
| kristianpaul | not that bad... but hmm.. i dont get the m1 logo mean in the center of the screen | 23:17 |
| kristianpaul | and the lined X | 23:17 |
| kristianpaul | but still nice :-) | 23:18 |
| --- Fri Apr 15 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!
