#milkymist IRC log for Thursday, 2011-08-25

wolfspraulwpwrak: did you get your m1?00:29
wpwraktomorrow. fedex didn't feel like leaving the warmth of their station today, it seems00:40
wpwrakif i'm lucky, it'll arrive together with something i've ordered from digi-key. one day less of twiddling my thumbs.00:41
wolfsprauloh I see00:41
wolfspraulAdam finished 20 boards fix2 -> fix2b00:41
wolfspraulplus the one that caused a problem (0x4D)00:42
wolfspraulanother 26 fix2 -> fix2b to go00:42
wolfspraulso there was a total of 204 render cycles, one failed00:43
wpwrakso the plan is to finish the fix2b rework first ? then go though the fallout ?00:43
wolfspraulI leave it to Adam, I don't want to kick him around all the time.00:44
wolfspraulI think he feels better first finishing that batch, yes.00:44
wpwrakokay. just want to know for my own planning.00:44
wolfspraulyes. so if he does that, all of today will be fix2->fix2b.00:45
wolfsprauland part of tomorrow. he calculates with a rate of 15 / day.00:45
wolfspraulxiangfu: you there? should we get the new flterm with logging to Adam?00:45
wolfspraulit could save him a little effort00:45
wolfspraulwhat does he have to do? build flterm from source? how did he get the flterm binary he is using right now?00:46
xiangfuwolfspraul, yes.  we should get new flterm to Adam.00:47
xiangfuhe build th flterm from source.00:47
xiangfuall he do is 'git pull' and make again.00:47
wolfspraulok that's easy00:50
wolfspraullet's see whether we can sneak it in :-)00:50
wolfsprauland then he needs a new command line?00:51
xiangfuyes.00:51
xiangfunow he is manually input 'flterm --port /dev/ttyUSB0 --kernel boot.bin', needs to add '--log m1.log'00:52
xiangfuI guess00:52
xiangfuwolfspraul, by the way I am uploading the Xilinx folder and license files to buildhost. it's myabe needs 2 days to finish upload. then let's see it it work out of tar ball :)00:54
xiangfus/it it/if it00:55
wolfspraulok good [xilinx]00:55
wolfsprauldoes the --log option append to the log file? or overwrite it?00:55
xiangfuappend00:55
wolfspraulah yes, just saw a+00:56
wolfspraulok, then he will probably do "--log m1rc3_0x57.log" or so00:56
wolfspraulvery good00:57
wolfspraulI think it will help him a little00:57
xiangfuyes01:00
wolfspraulaw: hi good morning! :-)01:13
awwolfspraul, good morning.01:13
wolfspraulxiangfu: let's help Adam get the new flterm...01:13
awxiangfu not here01:13
xiangfuhere :)01:14
Action: xiangfu is jumping :)01:14
wolfspraulaw: do you remember where the flterm sources are? (in your folder structure)01:14
wolfspraulyou need to 'cd' to that folder, then 'git pull' then 'make' (I think)01:14
xiangfuaw you can run 'which flterm'01:15
awxiangfu, /usr/bin/flterm01:15
xiangfudelete it first by 'sudo rm /usr/bin/flterm'01:16
awxiangfu, done01:16
xiangfuaw, then as wolfgang said find the milkymist.git folder. and goto the 'tools' folder01:17
xiangfurun 'git pull' and 'make'01:17
awflterm is new now01:19
awso next, what the command i should type? to record ?01:20
xiangfutry ./flterm see if '--log' in the help message01:20
wolfspraulaw: if you see the --log command in the help message, that means you can now use the new --log option, for example01:22
wolfspraulflterm --port /dev/ttyUSB0 --kernel boot.bin --log m1rc3_0x63.log01:22
wolfspraul--log will _append_ to the log file, so it will not overwrite it01:22
wolfspraulxiangfu: doesn't adam also have to run make install?01:24
xiangfuno, have to manually copy it to /usr/bin/01:24
awyes, i saw '--log' under /milkymist/tools, but how i can use it under different folder?01:25
xiangfuaw, just 'sudo cp flterm /usr/bin/' :)01:25
awxiangfu, i need to copy it into /usr/bin?01:25
awgood it can be typed under different folder. second...take one board to log01:27
awxiangfu, the log file can't be opened by 'gedit' after I used 'ctrl+C' to stop flterm, doesn't flterm accept 'ctrl +C'?01:35
xiangfuwhat is the error when you use 'gedit' ?01:36
awedit has not been able to detect the character encoding.01:38
awPlease check that you are not trying to open a binary file.01:38
awSelect a character encoding from the menu and try again.01:38
awxiangfu, but log can be opened by GNU Emacs 23 and GVim that I am not used them.01:39
xiangfuhmm... gedit have a 'tools' --> 'set languages'  try that.01:43
xiangfuaw, I can open the log file without any problem. just 'gedit a.log'01:43
awxiangfu, set to which? 'English'?01:46
awxiangfu, http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/m1rc3_0x52.log01:49
xiangfuyes set to English and try again.01:49
awbtw, if Emacs & GVim can open it, i think now i am ok01:50
awstill can't open after set English01:50
wolfspraulaw: email that log file to xiangfu, cc me. We'll find the reason.01:51
awbtw, I am writing a small script for flterm, moment, you can help01:51
wolfspraulbut yes, it seems you can use flterm --log now01:51
wolfsprauloh, I see you uploaded the log file already :-)01:53
wolfspraulinstalling gedit right now...01:54
xiangfuaw, there are some garbage characters, "telnetd started with stacksize = 81920 and priority = 901:54
xiangfu¿·6& "01:54
xiangfubut I don't have those characters in my log file.01:55
xiangfustrange01:55
wolfspraulxiangfu: I see two 0x00 bytes at the end of the file.01:55
wolfspraulthat's probably triggering the gedit problem. also I'm not sure what happens if you append. some text editors may choke on the 0x0001:56
awxiangfu, the garbage was done by usb-jtag board which once I powered off, it was that01:57
xiangfuaw, ok. then you can try exit the flterm before you you poweroff the usb-jtag :)01:58
awi have to power-cycle 10 times without "ctrl+C" in 'flterm'01:58
awxiangfu, NO01:58
xiangfuok.01:58
awthat was ineffciency01:58
wolfspraulno no, of course not. the software has to be fixed, the workaround is not on the human side :-)01:59
wolfspraulaw: you are right01:59
awwell..if gedit can't read it well...let still do it. since Emacs and GVim can read it01:59
wolfspraulyes01:59
wolfspraulmaybe xiangfu can avoid logging 0x00 in flterm?01:59
wolfspraul0x00 should not really be in a text file and serves no purpose02:00
kristianpaulxiangfu: why uploading xilinx stuff?02:00
wolfspraulI think once we take the two 0x00 at the end out gedit will not complain anymore.02:00
kristianpaulI installed mine from server and download from xilinx serves too02:00
kristianpauljust a ssh -Y and run ./xsetup02:01
xiangfuaw, you can try 'xedit' :)02:01
awxiangfu, please help me this first. ;-) http://downloads.qi-hardware.com/people/adam/m1/scripts/flterm_adam.sh02:01
wolfspraulxiangfu: wow, it seems you are writing each character separately and call fflush after each character? :-)02:02
wolfspraulat least that makes it easy to skip 0x0002:02
xiangfukristianpaul, you install it in fidelio.qi-hardware.com?02:02
awxiangfu, yes, 'xedit' can read it02:02
kristianpaulxiangfu: oh yeah, time ago02:03
wolfspraulxiangfu: I think just don't log 0x00: if (c) {fwrite/fflush}02:03
xiangfukristianpaul, update xilinx, then we can setup dailybuild soc :)02:04
wolfspraulflushing after each character is a bit extreme too I think, but I'm not sure about all buffers and whether they are flushed at ctrl-c etc.02:04
kristianpaulxiangfu: just tell where you want it isntalled02:04
xiangfukristianpaul, /opt/Xilinx02:04
kristianpaulxiangfu: i installed on my personal folder to not disturb system, but builhost looks more generic02:04
kristianpaulxiangfu: okay on my way..02:05
xiangfukristianpaul, ssh -Y extreme slow here :(02:06
kristianpauli cant image uploading then... :)02:06
xiangfukristianpaul, well, it's not hurry. so I just uploading from my server to buildhost. :) (since my server stand there only for my blog service)02:07
kristianpaulno problem i can do it right now or neber ;)02:07
kristianpaulnever*02:07
wolfspraulxiangfu: can you not log 0x00 ?02:08
wolfspraulthat should solve the problem02:08
wolfspraulyou should also think about the flush after each character02:08
awxiangfu, help me on my flterm_adam.sh since my previous file named already "52-results", so i just want flterm --log can append directly on those 'existed files'. ;-)02:09
wolfspraulyou can leave it in for now but I think it's too extreme02:09
xiangfuwolfspraul,  yes.02:09
xiangfuwolfspraul, (fflush) maybe every line.02:09
xiangfuif(c = '\n') fflush02:09
xiangfuwolfspraul, I just write those code follow 'flerm.c' , needs improve.02:11
wolfspraulyes sure but if you fix the 0x00 now then Adam can use gedit again (I hope)02:14
kristianpaulxiangfu: configure.ac:5: error: Autoconf version 2.68 or higher is required02:14
kristianpaulis it know?02:14
kristianpaulknown*02:14
kristianpaulI'm rebuilding my toolchain as seems last disk failure truncated my /opt partition :(02:15
kristianpaulrtems toolchain02:15
wolfspraulaw: what do you want to know about flterm_adam.sh ?02:15
wolfspraullooks good02:15
awxiangfu, i keep testing...just ping me if you have new one02:15
awwolfspraul, No, must be path to be correctly, well.. i don't know02:16
wolfspraulwait02:16
wolfspraultry this line02:16
xiangfuaw, http://downloads.qi-hardware.com/people/xiangfu/tmp/flterm_adam.sh02:17
xiangfuoh02:17
xiangfukristianpaul, it's known. :)02:17
xiangfukristianpaul, there is one line in my .bashrc : PATH=/home/xiangfu/workspace/PanGu/openwrt-xburst/staging_dir/host/bin:$PATH02:18
wolfspraulsudo flterm --port /dev/ttyUSB0 --kernel ~/m1_adam/snapshots/2011-07-13/for-rc3/boot.4e53273.bin --log ~/m1_adam/snapshots/2011-07-13/results/$1-results02:18
wolfspraulyou have to run flterm with sudo, no?02:18
xiangfukristianpaul, which have autoconf 2.68 :)02:18
awxiangfu, thanks a lot! ;-) try it later, i am reflashing another board02:18
kristianpaulxiangfu: 2.67-2 debian squeeze02:18
kristianpauldamn debian old stuf.. :/02:18
kristianpauloh well :)02:19
xiangfukristianpaul, upload to 2.68 is conflict with pkc-config02:19
wolfspraulah yes, xiangfu's is nicer02:19
awwolfspraul, yes, seems same as xingfu's one. thanks!02:19
wolfspraulaw: xiangfu will fix the gedit problem too02:19
kristianpaulxiangfu: so stay with 2.67-2 and try your PATH right?02:19
awwolfspraul, alright, i go for other boards firstly, i think xiangfu will ping me later, thank you all.02:20
xiangfukristianpaul, yes.02:21
kristianpaulxiangfu: oh wait, that line from your batch is about openwrt-xburst..02:21
kristianpaulbashrc*02:21
xiangfukristianpaul, yes :)02:21
kristianpaulhum??02:21
kristianpauland it solves my boostraping problem around rtems?02:22
kristianpaulhe, i shall be more precise02:22
xiangfukristianpaul, not sure. maybe. I only have zlib problem when compile rtems now.02:22
kristianpaulhum.. i think i'll try manually better02:23
kristianpaulbtw you run buildhost scripts as root?02:23
xiangfuaw, you can avoid 'sudo' by add this file [http://downloads.qi-hardware.com/people/xiangfu/tmp/72-qi-hardware.rules] to folder '/etc/udev/rules.d'02:23
kristianpaulokay i'll install ise as root too02:24
xiangfuaw, and change the GROUP to [GROUP="adam"]02:24
xiangfukristianpaul, no. I am not use 'root', I scare 'root' user always.02:25
xiangfukristianpaul, I change the '/opt' to mine :) for compile milkymist one stuff02:25
kristianpaulah02:25
kristianpaulok so..02:25
kristianpauli'll install as root you can rever permission later then02:26
kristianpaulrevert*02:26
kristianpaulhum no space left..02:27
kristianpaulon /opt02:27
xiangfukristianpaul, you installing ISE on buildhost now? if you install. I dont' think I needs do that again.02:28
xiangfuonly one ISE is enough.02:28
xiangfukristianpaul, what version you using? 13.2?02:28
kristianpaulsure, of corse 13.202:28
kristianpaulyes installing on buildhost now02:28
kristianpaulso..02:28
kristianpauli install on /home/xilinx..02:29
kristianpaul;-)02:29
kristianpaulokay installing now02:30
xiangfukristianpaul, thanks. I will use that one /home/xilinx02:30
kristianpaulbtw i'm lost, should i use rtems from the unoffial git repo in milkymist organizational page or rtems-old?02:31
xiangfunot rtems-old.02:32
xiangfukristianpaul, use rtems.git and 'mmstaging' branch02:36
kristianpaulI'm using your script :)02:38
kristianpaulhum wheezy have autoconf 1.68-102:40
kristianpaul2.68-1*02:40
kristianpaularghhh i should had stay on fedora....02:41
kristianpaulxiangfu: http://pastebin.com/wYpaddG302:42
xiangfu?02:44
kristianpaulafter make -C compile-flickernoise flickernoise.fbi02:45
kristianpaulsteps 1 to 6 went okay it seems..02:45
kristianpauljust telling :)02:45
kristianpauli decide to clone that scripts folder today02:46
awxiangfu, when used a normal command, i got err: adam@adam-laptop:~/m1_adam/snapshots/2011-07-13/for-rc3$ flterm --port /dev/ttyUSB0 --kernel boot.4e53273.bin02:46
aw[FLTERM] Starting...02:46
awSegmentation fault02:46
stekernkristianpaul: that pastebin paste seems to be incomplete02:47
kristianpaulhum..02:47
kristianpauldamn02:47
wolfspraulxiangfu: calling fwrite with a 0 file descriptor is not a good idea02:51
xiangfuwolfspraul, my fault. :(02:51
wolfspraulmaybe you fix that too then Adam can do a git pull and make/install02:51
xiangfusending new patch now02:51
kristianpaulfulllog http://pastebin.com/bhkgMyTy02:56
stekernkristianpaul: I think something is still missing02:57
awxiangfu, so i can do git pull and make now?02:59
xiangfuaw, no. I don't have write access to milkymist.git. have to wait Sebastien apply the patch02:59
awoah... i can use neither normal flterm command nor --log now..too bad. :(03:01
kristianpauldone, ISE 13.2 installed at /home/Xilinx/13.2 @ fidelio03:01
xiangfuaw, but you can manually apply it for temp.03:01
kristianpaulalready licensed and smalltalk disabled03:01
wolfspraulhow about --log /dev/null ?03:02
wolfspraulaw: try --log /dev/null03:02
awxiangfu, yes, just no gedit support now03:02
kristianpaulxiangfu: i'll start over again rtems toolchain process03:02
xiangfuaw, under milkmist.git folder run:03:03
xiangfuwget http://downloads.qi-hardware.com/people/xiangfu/tmp/0001-tools-flterm-check-logfd-not-log-0x00-flush-each-lin.patch03:03
kristianpaulhum the end-of-line in flterm is just fun :)03:03
xiangfugit am 0001-tools-flterm-check-logfd-not-log-0x00-flush-each-lin.patch03:03
xiangfuaw, and make again.03:03
wolfspraulxiangfu: how about he just uses --log /dev/null for now03:04
wolfspraulxiangfu: can you test whether that works?03:04
xiangfuwolfspraul, yes. /dev/null works fine03:04
wolfspraulso no git am/make etc. waste of time. get a working software into the repository, until then Adam can use a workaround such as --log /dev/null to fix the latest crash03:05
xiangfushould not write any C code before sleep03:12
xiangfukristianpaul, the error I have is like: http://pastebin.com/aaE6PTGM03:18
awxiangfu, just applied, now normal 'flterm' cmd can work, and the new log appended it but gedit still can't open it: http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/56-results03:20
stekernxiangfu: yeah, that's what I get too03:20
awxiangfu, so I keep using this new 'flterm' patch...later you fix that which can use gedit. just ping me, thanks.03:21
wpwrakxiangfu: solution: don't sleep after writing code ! ;-)03:22
xiangfuaw, about 'gedit' just select one code and click 'retry'03:23
xiangfuencode like ISO or whateven and click 'retry'03:23
awxiangfu, oah..yes, after select "Western" and clicked 'retry', then 'gedit' can read it then. thanks you! ;-)03:25
xiangfustekern, we should try this: [Fallenoulekernel: I copied CVS HEAD cpukit/zlib/zconf.h.in to a fresh git clone of milkymist rtems, it builds properly, do I commit & push ?]03:26
stekernxiangfu: CVS HEAD of rtems mainline I presume?03:27
kristianpaulyes03:32
wolfspraulxiangfu: I can reproduce the gedit problem. the warning goes away when I delete two 0xf7 characters in the log.03:34
wolfspraulsome garbage from the serial console somewhere03:34
xiangfuwolfspraul, yes. when poweron/off the milkymist one03:34
wolfspraulso what are the solutions03:34
stekernwhat's up with the rtems people not using a sane vcs03:34
wolfspraulwe could not log anything 0x80 or higher03:35
xiangfuwolfspraul, I think just leave them. garbage from serial is very normal03:35
stekernI mean, svn is bad enough, but cvs... common03:35
wolfspraulyes true03:35
wolfspraulbut then maybe a marker at the beginning? should we write proper utf-8?03:35
xiangfukristianpaul,  stekern, I will add the patch to my script.git until it fixed. :)03:35
wpwrakstekern: hey, it surely beat the stone tablets they used before ! ;-)03:35
stekernwpwrak: :)03:36
kristianpaulxiangfu: i dont think my current issue is related to zlib,,03:36
wolfspraulmaybe convert any character above 0x80 to a utf-8 sequence?03:36
xiangfukristianpaul, I don't see the error from your pastebin03:36
kristianpaulme either..03:36
kristianpaulis just that auto¨03:37
kristianpaul***03:37
kristianpaulagh03:37
kristianpaulwpwrak: nah, stone no, may be type writer?03:37
wolfspraulwe assume the 8-bit incoming characters to be iso-8859-1 and write utf-8? that could make the warning go away03:37
wolfspraulxiangfu: can you reproduce the gedit warning?03:42
xiangfuwolfspraul, yes. that will be one solution.03:42
xiangfuwolfspraul, yes. I can,03:42
wolfspraulhere's a snippet I found to go from 8859-1 to utf-8: if (*in<128) *out++=*in++; else *out++=0xc2+(*in>0xbf), *out++=(*in++&0x3f)+0x80;03:42
wolfspraulbasically a c >= 0x80 becomes two fwrite03:43
wolfspraulthen we write utf-8, and depending on Adam's locale settings and gedit assumptions/defaults, it may open without a warning03:43
wolfspraulMAY03:43
wolfspraul:-)03:44
wolfspraulbut utf-8 is a good start I think03:44
wolfspraulI guess the 0xf7 we write into the file now confuses gedit. if it assumes the file to be utf-8 (and there is no marker at the beginning), then it's a strange character. if it's not utf-8, then gedit won't know which 8-bit standard it is.03:45
xiangfustekern, I am apply the patch, compiling now. if everything fine , I will push my commit to scripts.git for keep the patch03:45
xiangfuwolfspraul, ok. will try that code03:48
stekernxiangfu: sounds good03:50
kristianpaulxiangfu: my problem is with boostraping, i always got configure.ac:5: error: Autoconf version 2.68 or higher is required03:56
xiangfukristianpaul, do you have autoconf 2.68 installed?03:58
kristianpaulno03:58
kristianpaulthink in me like same debian as buildhost03:59
kristianpaulmy autoconf is 2.67-203:59
xiangfukristianpaul, have to update to 2.68 since Sebastien sync the rtems.git with upstream.04:00
xiangfukristianpaul, then the buildhost will not compile either.04:00
kristianpaulhum...04:01
xiangfukristianpaul, the solutions is add openwrt staging host bin to your PATH,04:01
Action: kristianpaul *sigh*04:01
xiangfukristianpaul, if you in buildhost that will easy, there are openwrt-xburst.full_system under /home/xiangfu.04:01
xiangfu:)04:02
kristianpaulno no, more mixes of openwrt with this..04:02
xiangfuwolfspraul, the code [: if (*in<128) *out++=*in++; else *out++=0xc2+(*in>0xbf), *out++=(*in++&0x3f)+0x80;] not working :(04:05
wolfspraulwell04:05
wolfspraulof course that's just the numbers for the 0x80..0xFF to utf-8 conversion04:05
kristianpaulis not locales good for that convertion? (jsut a guess)04:06
GitHub59[scripts] xiangfu pushed 1 new commit to master: http://git.io/cIaHYw04:07
GitHub59[scripts/master] compile-flickernoise: fix zlib compile error - Xiangfu Liu04:07
wolfspraul0x80..0bf becomes 0xc2 + 0x80..0xbf04:07
xiangfustekern, ^04:07
wolfspraul0xc0 .. 0xff becomes 0xc3 + 0x80..0xbf04:07
wolfspraulif I read that snippet correctly...04:07
wolfspraulso 0xf7 would become 0xc3 0xb7. If I could find a binary editor I should try real quick whether the gedit warning goes away :-)04:09
wolfspraulwhich editor can give me a hex editing view?04:09
xiangfuvim :!xxd04:09
kristianpaulphew seems installing autoconf_2.68-1_all.deb solves this problem :)04:10
xiangfusorry04:10
kristianpaulhexedit i guess04:11
xiangfuwolfspraul, %!xxd04:11
kristianpauloh, nice xiangfu :)04:12
xiangfu:%!xxd to convert to hex, :%!xxd -r to convert back04:12
kristianpaulbut it actually is not updating ascii view after edit the hex equivalent is it?04:13
xiangfukristianpaul,  :%!xxd -r to convert back then save04:13
wolfspraulxiangfu: ok worked. and I can confirm that after I convert the two 0xf7 characters in there to 0xc3 0xb7 (the utf-8 equivalent), my gedit opens it without warning04:16
wolfspraulmy default console is utf-8 thought, so Adam may still get warnings depending which gedit version he has, his locale, etc.04:17
wolfspraulbut I think we should write utf-8, why not04:17
wolfspraulxiangfu: is that 0xc2/0xc3 stuff clear?04:17
wolfspraulthe line was meant to give you the numbers, not to copy/paste into your sources 1:104:18
xiangfuwolfspraul, ok.04:18
wolfspraulin your sources, it's something like if (c >= 0x80) { fwrite(0xc2+(c>0xbf)); fwrite(0x80+(c&0x3f)); }04:20
wolfspraulnot to be copied 1:1 :-)04:20
stekernxiangfu: nice one, I'll pull and test04:26
xiangfuwolfspraul, not copied 1:1 but I forget 0x00 again. now it works fine. thanks. (my serial console garbage is much more then Adam's :)04:34
wolfspraulcan your gedit open the resulting files without warnings now?04:36
xiangfuyes. without any  warnings now04:37
wolfspraulnice04:38
kristianpaulokay i need that zlib patch now :)04:40
xiangfumy fault the flterm patch goes to Version V3 :(04:45
stekernxiangfu: that worked for me04:48
kristianpaulhum..04:49
kristianpaulall04:49
kristianpaulok04:49
kristianpaulbye05:00
lekernelxiangfu, what is that "utf-8" patch doing?09:44
xiangfujust convert the > 0x80 ASCII to utf-8. for avoid the editor can not open it. (like gedit)09:44
lekernelif(c >= 0x80) ... isn't char signed?09:45
lekernelalso, is that really UTF8?09:46
lekernelwhy not simply drop those characters instead?09:46
xiangfulekernel, yes. that is a solution, simple and clean. :)09:47
lekernelok, please send a new patch09:51
lekerneland I guess you should check for c < 0 instead of c >= 0x80... no? (maybe I'm wrong)09:51
lekernelor use unsigned char ... I'm usually trying to avoid those corner cases :)09:52
xiangfulekernel, I use 'if(isascii(c))'09:57
lekernelok09:57
xiangfusent out10:03
wpwrakfwiw, "char" can default to signed or unsigned.10:53
kristianpaul"or" dint sounded as default..10:57
kristianpaulhow you force it?10:57
wpwrakwell, that depends on the compiler :)10:59
wpwrake.g., in gcc, you have -fsigned-char, -funsigned-char, and also the equivalent -fno-unsigned-char and -fno-signed-char11:00
wpwrakhmm, can't quite remember where I saw "char" default to "unsigned'. i thought it was sdcc, bit now i see that it has "--funsigned-char", which suggests the built-in default is signed11:02
kristianpaulhe, i was about to make a joke a bout sdcc xD11:05
kristianpauls/bout/about11:05
kristianpaulwow sdcc is version 3 now11:06
wpwrakstill buggy, though :-(11:33
wpwrakbut better than before11:33
lekernelwpwrak, most programs assume char is signed (and of course it was unsigned with some early versions of lm32-gcc, which meant more problems ...)11:54
FallenouI didn't know, usually I assume char is signed11:55
lekernelyeah, that's the right thing to do11:56
FallenouI thought by default all the types were signed by default unless you say (unsigned)11:56
lekernelthis mess with the C types is just stupid and wasting everyone's time11:56
Fallenouclearly11:56
FallenouI guess that's why people use uint8_t and such instead of primitif types11:56
lekernelthe standard should simply say things like int = 32 bits, short int = 16 bits, char = 8 bits, and all types are signed by default11:56
Fallenouchar = 8 bits is usually the case (don't know of any exception), but short int ... I think it depends, and that sucks11:57
stekernchar = 16 bit with TI C2000 compiler12:23
Fallenounice !12:23
wpwraklekernel: that's why we have int32_t, uint16_t, etc. they're good. use them ;-)12:25
lekernelbut they're not integrated in the compiler and sometimes result in a include file mess12:26
stekernI wonder how many programs written for x86 have got bitten by bugs when assuming unsigned long = 32 bits12:28
stekernor just plain long for that matter12:28
stekernisn't stdint.h part of C99 btw?12:36
wpwrakit's been well over a decade since I last saw problems with stdint.h, so i'd consider it rather safe. of course, maybe you visit tougher neighbourhoods than i do ;-)12:39
wpwrakM1 arrived ! :)16:40
kristianpaulGood !!16:46
kristianpaulDoes it boot? ;)16:51
wpwrakassembling the case ...16:55
wpwrakcase design feedback for the next version: the power input should also mention how much current it draws16:58
wpwraknow, find a power supply ...17:00
kristianpaulhum..17:04
kristianpauli still wondering why you dont pay taxes for it17:08
wpwrakoh, i had to. they somehow got that wrong. but it wasn't much, about USD 15. (declared value was USD 50)17:09
Action: wpwrak makes valiant attempt of locating one of the nice high-quality 5 V supplied remaining from the OQO days17:10
Action: wpwrak locates power supply :-)17:10
Action: wpwrak removes dust, spiders, ...17:11
Action: wpwrak checks idle output of power supply. 5.12 V, perfect17:16
Action: wpwrak hopes 2500 mA are enough17:16
wpwrakwikipedia says 5 W. excellent. that's plenty.17:17
wpwrakit gets as far as "press Esc for console"17:19
wpwraklocating keyboard ...17:20
wpwrakaah, effects ! :)17:20
wpwrakjust have to wait before it does somethign, it seems ;-)17:21
wpwrakmarvels at the coolness of the video effects17:23
wpwrak"esc for console", when exactly does this work ? when the Milkymist logo with that message is shown ? or also later ?17:26
kristianpaulclap clap !17:32
wpwrakstill haven't gotten it to talk to anything USB yet17:35
wpwrakeeh, kewl. of all devices, my little wireless remote keyboard works ;-)17:35
wpwrakat least with the console. no response under FN17:38
wpwrakthe handling of the screen when booting is rather confusing. first the welcome screen, then it's powered down (no signals), then blue screen, and finally some action17:41
wpwrakthe "stricken" aircrash looks cool17:44
wpwrakand the one following it has very nice colors17:44
wpwrak(the wiggling square) just the white line in the middle looks like a rendering error17:44
wpwrakcan USB hot-plug ? or do i have to power-cycle for new devices to be recognized ?17:48
lekernelusb hotplug works17:56
lekernelboth the console and FN use the same code for USB, so you have probably spotted one of those pesky intermittent bugs17:56
wpwrak;-))17:56
wpwrakor maybe i'm just not using it right17:57
lekernelyou shouldn't see the splash screen with "press esc for console", unless you are in rescue mode or pressed the power button for > ~1s17:57
wpwrakwhen i press the first button, i get a screen saying "Update" ... "Failed". mouse cursor is in the upper left corner. it there any keyboard input that should do something ?17:58
lekernelblue screen is probably missing camera input17:58
wpwrak(i don't get a mouse response, but that may be just a problem of my RF keyboard)17:58
lekerneluse ESC to leave render mode, not update ...17:58
lekernelor enter17:59
wpwrakaah, Esc also works in render mode. i see17:59
wpwrakbooting again17:59
lekernelyou can move the mouse cursor with the keyboard, see http://www.milkymist.org/leaflets/run3_leaflet.pdf17:59
wpwrakhmm, this keyboard doesn't have a meta key. and none of the "unusual" keys  (Fn+something) seem to work as the kind of modifier FN expects. but i also don't know what the keyboard really sends in this case. may be nonsense18:02
wpwrakah, i have better luck with some cheap crap keyboard18:03
wpwrakit doesn't like my kensington mouse, though18:04
wpwrakworks with a Microsoft mouse. you should watch the company your child keeps ! :)18:05
wpwrakokay, looking good so far. now i have to leave for a bit. more experimenting later.18:05
lekernelmeta key = windows key18:05
wpwrakwin = fn+ctrl on that kbd. and fn+cursor is also some magic. so maybe there's the conflict.18:06
GitHub92[milkymist] sbourdeauducq pushed 1 new commit to master: http://git.io/0NDl_w18:23
GitHub92[milkymist/master] tools: flterm: check logfd, check ascii, flush each line - Xiangfu Liu18:23
kristianpaulwin 1918:27
wpwrakwill M1s be sold as fully assembled kits or is there a plan to also sell a significant number of them as kits ? in the latter case, perhaps the case assembly instructions should mention that each acrylic parts has two protective sheets, a discreet transparent one and a white one to draw people's attention away from the former :)20:53
wpwrak(i only noticed the transparent one when i got to the sidewalls. before, i had thought the bottom plate simply had some scratches on what then must be the inside)20:54
wpwrakroh: should i expect any trouble when gluing the buttons with regular superglue ? (liquid, not the messy gel)20:55
rohwpwrak: its messy and tends to break if you put on mechanical stress21:08
roh;)21:08
rohwpwrak: but the buttons on the new parts i shipped in the last batch are already glued21:09
wpwrakthe ones i got are in parts. well, so maybe double-faced tape then21:34
lekernelif you go for the superglue, the most important thing is not to use too much21:41
lekernelotherwise it leaks from the sides and creates a mess21:41
lekernelthere won't be kits I think21:42
xiangfulekernel, Hi23:43
--- Fri Aug 26 201100:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!