| wolfspraul | wpwrak: did you get your m1? | 00:29 |
|---|---|---|
| wpwrak | tomorrow. fedex didn't feel like leaving the warmth of their station today, it seems | 00:40 |
| wpwrak | if i'm lucky, it'll arrive together with something i've ordered from digi-key. one day less of twiddling my thumbs. | 00:41 |
| wolfspraul | oh I see | 00:41 |
| wolfspraul | Adam finished 20 boards fix2 -> fix2b | 00:41 |
| wolfspraul | plus the one that caused a problem (0x4D) | 00:42 |
| wolfspraul | another 26 fix2 -> fix2b to go | 00:42 |
| wolfspraul | so there was a total of 204 render cycles, one failed | 00:43 |
| wpwrak | so the plan is to finish the fix2b rework first ? then go though the fallout ? | 00:43 |
| wolfspraul | I leave it to Adam, I don't want to kick him around all the time. | 00:44 |
| wolfspraul | I think he feels better first finishing that batch, yes. | 00:44 |
| wpwrak | okay. just want to know for my own planning. | 00:44 |
| wolfspraul | yes. so if he does that, all of today will be fix2->fix2b. | 00:45 |
| wolfspraul | and part of tomorrow. he calculates with a rate of 15 / day. | 00:45 |
| wolfspraul | xiangfu: you there? should we get the new flterm with logging to Adam? | 00:45 |
| wolfspraul | it could save him a little effort | 00:45 |
| wolfspraul | what does he have to do? build flterm from source? how did he get the flterm binary he is using right now? | 00:46 |
| xiangfu | wolfspraul, yes. we should get new flterm to Adam. | 00:47 |
| xiangfu | he build th flterm from source. | 00:47 |
| xiangfu | all he do is 'git pull' and make again. | 00:47 |
| wolfspraul | ok that's easy | 00:50 |
| wolfspraul | let's see whether we can sneak it in :-) | 00:50 |
| wolfspraul | and then he needs a new command line? | 00:51 |
| xiangfu | yes. | 00:51 |
| xiangfu | now he is manually input 'flterm --port /dev/ttyUSB0 --kernel boot.bin', needs to add '--log m1.log' | 00:52 |
| xiangfu | I guess | 00:52 |
| xiangfu | wolfspraul, 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 |
| xiangfu | s/it it/if it | 00:55 |
| wolfspraul | ok good [xilinx] | 00:55 |
| wolfspraul | does the --log option append to the log file? or overwrite it? | 00:55 |
| xiangfu | append | 00:55 |
| wolfspraul | ah yes, just saw a+ | 00:56 |
| wolfspraul | ok, then he will probably do "--log m1rc3_0x57.log" or so | 00:56 |
| wolfspraul | very good | 00:57 |
| wolfspraul | I think it will help him a little | 00:57 |
| xiangfu | yes | 01:00 |
| wolfspraul | aw: hi good morning! :-) | 01:13 |
| aw | wolfspraul, good morning. | 01:13 |
| wolfspraul | xiangfu: let's help Adam get the new flterm... | 01:13 |
| aw | xiangfu not here | 01:13 |
| xiangfu | here :) | 01:14 |
| Action: xiangfu is jumping :) | 01:14 | |
| wolfspraul | aw: do you remember where the flterm sources are? (in your folder structure) | 01:14 |
| wolfspraul | you need to 'cd' to that folder, then 'git pull' then 'make' (I think) | 01:14 |
| xiangfu | aw you can run 'which flterm' | 01:15 |
| aw | xiangfu, /usr/bin/flterm | 01:15 |
| xiangfu | delete it first by 'sudo rm /usr/bin/flterm' | 01:16 |
| aw | xiangfu, done | 01:16 |
| xiangfu | aw, then as wolfgang said find the milkymist.git folder. and goto the 'tools' folder | 01:17 |
| xiangfu | run 'git pull' and 'make' | 01:17 |
| aw | flterm is new now | 01:19 |
| aw | so next, what the command i should type? to record ? | 01:20 |
| xiangfu | try ./flterm see if '--log' in the help message | 01:20 |
| wolfspraul | aw: if you see the --log command in the help message, that means you can now use the new --log option, for example | 01:22 |
| wolfspraul | flterm --port /dev/ttyUSB0 --kernel boot.bin --log m1rc3_0x63.log | 01:22 |
| wolfspraul | --log will _append_ to the log file, so it will not overwrite it | 01:22 |
| wolfspraul | xiangfu: doesn't adam also have to run make install? | 01:24 |
| xiangfu | no, have to manually copy it to /usr/bin/ | 01:24 |
| aw | yes, i saw '--log' under /milkymist/tools, but how i can use it under different folder? | 01:25 |
| xiangfu | aw, just 'sudo cp flterm /usr/bin/' :) | 01:25 |
| aw | xiangfu, i need to copy it into /usr/bin? | 01:25 |
| aw | good it can be typed under different folder. second...take one board to log | 01:27 |
| aw | xiangfu, 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 |
| xiangfu | what is the error when you use 'gedit' ? | 01:36 |
| aw | edit has not been able to detect the character encoding. | 01:38 |
| aw | Please check that you are not trying to open a binary file. | 01:38 |
| aw | Select a character encoding from the menu and try again. | 01:38 |
| aw | xiangfu, but log can be opened by GNU Emacs 23 and GVim that I am not used them. | 01:39 |
| xiangfu | hmm... gedit have a 'tools' --> 'set languages' try that. | 01:43 |
| xiangfu | aw, I can open the log file without any problem. just 'gedit a.log' | 01:43 |
| aw | xiangfu, set to which? 'English'? | 01:46 |
| aw | xiangfu, http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc3/test_results/m1rc3_0x52.log | 01:49 |
| xiangfu | yes set to English and try again. | 01:49 |
| aw | btw, if Emacs & GVim can open it, i think now i am ok | 01:50 |
| aw | still can't open after set English | 01:50 |
| wolfspraul | aw: email that log file to xiangfu, cc me. We'll find the reason. | 01:51 |
| aw | btw, I am writing a small script for flterm, moment, you can help | 01:51 |
| wolfspraul | but yes, it seems you can use flterm --log now | 01:51 |
| wolfspraul | oh, I see you uploaded the log file already :-) | 01:53 |
| wolfspraul | installing gedit right now... | 01:54 |
| xiangfu | aw, there are some garbage characters, "telnetd started with stacksize = 81920 and priority = 9 | 01:54 |
| xiangfu | ¿·6& " | 01:54 |
| xiangfu | but I don't have those characters in my log file. | 01:55 |
| xiangfu | strange | 01:55 |
| wolfspraul | xiangfu: I see two 0x00 bytes at the end of the file. | 01:55 |
| wolfspraul | that's probably triggering the gedit problem. also I'm not sure what happens if you append. some text editors may choke on the 0x00 | 01:56 |
| aw | xiangfu, the garbage was done by usb-jtag board which once I powered off, it was that | 01:57 |
| xiangfu | aw, ok. then you can try exit the flterm before you you poweroff the usb-jtag :) | 01:58 |
| aw | i have to power-cycle 10 times without "ctrl+C" in 'flterm' | 01:58 |
| aw | xiangfu, NO | 01:58 |
| xiangfu | ok. | 01:58 |
| aw | that was ineffciency | 01:58 |
| wolfspraul | no no, of course not. the software has to be fixed, the workaround is not on the human side :-) | 01:59 |
| wolfspraul | aw: you are right | 01:59 |
| aw | well..if gedit can't read it well...let still do it. since Emacs and GVim can read it | 01:59 |
| wolfspraul | yes | 01:59 |
| wolfspraul | maybe xiangfu can avoid logging 0x00 in flterm? | 01:59 |
| wolfspraul | 0x00 should not really be in a text file and serves no purpose | 02:00 |
| kristianpaul | xiangfu: why uploading xilinx stuff? | 02:00 |
| wolfspraul | I think once we take the two 0x00 at the end out gedit will not complain anymore. | 02:00 |
| kristianpaul | I installed mine from server and download from xilinx serves too | 02:00 |
| kristianpaul | just a ssh -Y and run ./xsetup | 02:01 |
| xiangfu | aw, you can try 'xedit' :) | 02:01 |
| aw | xiangfu, please help me this first. ;-) http://downloads.qi-hardware.com/people/adam/m1/scripts/flterm_adam.sh | 02:01 |
| wolfspraul | xiangfu: wow, it seems you are writing each character separately and call fflush after each character? :-) | 02:02 |
| wolfspraul | at least that makes it easy to skip 0x00 | 02:02 |
| xiangfu | kristianpaul, you install it in fidelio.qi-hardware.com? | 02:02 |
| aw | xiangfu, yes, 'xedit' can read it | 02:02 |
| kristianpaul | xiangfu: oh yeah, time ago | 02:03 |
| wolfspraul | xiangfu: I think just don't log 0x00: if (c) {fwrite/fflush} | 02:03 |
| xiangfu | kristianpaul, update xilinx, then we can setup dailybuild soc :) | 02:04 |
| wolfspraul | flushing 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 |
| kristianpaul | xiangfu: just tell where you want it isntalled | 02:04 |
| xiangfu | kristianpaul, /opt/Xilinx | 02:04 |
| kristianpaul | xiangfu: i installed on my personal folder to not disturb system, but builhost looks more generic | 02:04 |
| kristianpaul | xiangfu: okay on my way.. | 02:05 |
| xiangfu | kristianpaul, ssh -Y extreme slow here :( | 02:06 |
| kristianpaul | i cant image uploading then... :) | 02:06 |
| xiangfu | kristianpaul, 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 |
| kristianpaul | no problem i can do it right now or neber ;) | 02:07 |
| kristianpaul | never* | 02:07 |
| wolfspraul | xiangfu: can you not log 0x00 ? | 02:08 |
| wolfspraul | that should solve the problem | 02:08 |
| wolfspraul | you should also think about the flush after each character | 02:08 |
| aw | xiangfu, 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 |
| wolfspraul | you can leave it in for now but I think it's too extreme | 02:09 |
| xiangfu | wolfspraul, yes. | 02:09 |
| xiangfu | wolfspraul, (fflush) maybe every line. | 02:09 |
| xiangfu | if(c = '\n') fflush | 02:09 |
| xiangfu | wolfspraul, I just write those code follow 'flerm.c' , needs improve. | 02:11 |
| wolfspraul | yes sure but if you fix the 0x00 now then Adam can use gedit again (I hope) | 02:14 |
| kristianpaul | xiangfu: configure.ac:5: error: Autoconf version 2.68 or higher is required | 02:14 |
| kristianpaul | is it know? | 02:14 |
| kristianpaul | known* | 02:14 |
| kristianpaul | I'm rebuilding my toolchain as seems last disk failure truncated my /opt partition :( | 02:15 |
| kristianpaul | rtems toolchain | 02:15 |
| wolfspraul | aw: what do you want to know about flterm_adam.sh ? | 02:15 |
| wolfspraul | looks good | 02:15 |
| aw | xiangfu, i keep testing...just ping me if you have new one | 02:15 |
| aw | wolfspraul, No, must be path to be correctly, well.. i don't know | 02:16 |
| wolfspraul | wait | 02:16 |
| wolfspraul | try this line | 02:16 |
| xiangfu | aw, http://downloads.qi-hardware.com/people/xiangfu/tmp/flterm_adam.sh | 02:17 |
| xiangfu | oh | 02:17 |
| xiangfu | kristianpaul, it's known. :) | 02:17 |
| xiangfu | kristianpaul, there is one line in my .bashrc : PATH=/home/xiangfu/workspace/PanGu/openwrt-xburst/staging_dir/host/bin:$PATH | 02:18 |
| wolfspraul | sudo 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-results | 02:18 |
| wolfspraul | you have to run flterm with sudo, no? | 02:18 |
| xiangfu | kristianpaul, which have autoconf 2.68 :) | 02:18 |
| aw | xiangfu, thanks a lot! ;-) try it later, i am reflashing another board | 02:18 |
| kristianpaul | xiangfu: 2.67-2 debian squeeze | 02:18 |
| kristianpaul | damn debian old stuf.. :/ | 02:18 |
| kristianpaul | oh well :) | 02:19 |
| xiangfu | kristianpaul, upload to 2.68 is conflict with pkc-config | 02:19 |
| wolfspraul | ah yes, xiangfu's is nicer | 02:19 |
| aw | wolfspraul, yes, seems same as xingfu's one. thanks! | 02:19 |
| wolfspraul | aw: xiangfu will fix the gedit problem too | 02:19 |
| kristianpaul | xiangfu: so stay with 2.67-2 and try your PATH right? | 02:19 |
| aw | wolfspraul, alright, i go for other boards firstly, i think xiangfu will ping me later, thank you all. | 02:20 |
| xiangfu | kristianpaul, yes. | 02:21 |
| kristianpaul | xiangfu: oh wait, that line from your batch is about openwrt-xburst.. | 02:21 |
| kristianpaul | bashrc* | 02:21 |
| xiangfu | kristianpaul, yes :) | 02:21 |
| kristianpaul | hum?? | 02:21 |
| kristianpaul | and it solves my boostraping problem around rtems? | 02:22 |
| kristianpaul | he, i shall be more precise | 02:22 |
| xiangfu | kristianpaul, not sure. maybe. I only have zlib problem when compile rtems now. | 02:22 |
| kristianpaul | hum.. i think i'll try manually better | 02:23 |
| kristianpaul | btw you run buildhost scripts as root? | 02:23 |
| xiangfu | aw, 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 |
| kristianpaul | okay i'll install ise as root too | 02:24 |
| xiangfu | aw, and change the GROUP to [GROUP="adam"] | 02:24 |
| xiangfu | kristianpaul, no. I am not use 'root', I scare 'root' user always. | 02:25 |
| xiangfu | kristianpaul, I change the '/opt' to mine :) for compile milkymist one stuff | 02:25 |
| kristianpaul | ah | 02:25 |
| kristianpaul | ok so.. | 02:25 |
| kristianpaul | i'll install as root you can rever permission later then | 02:26 |
| kristianpaul | revert* | 02:26 |
| kristianpaul | hum no space left.. | 02:27 |
| kristianpaul | on /opt | 02:27 |
| xiangfu | kristianpaul, you installing ISE on buildhost now? if you install. I dont' think I needs do that again. | 02:28 |
| xiangfu | only one ISE is enough. | 02:28 |
| xiangfu | kristianpaul, what version you using? 13.2? | 02:28 |
| kristianpaul | sure, of corse 13.2 | 02:28 |
| kristianpaul | yes installing on buildhost now | 02:28 |
| kristianpaul | so.. | 02:28 |
| kristianpaul | i install on /home/xilinx.. | 02:29 |
| kristianpaul | ;-) | 02:29 |
| kristianpaul | okay installing now | 02:30 |
| xiangfu | kristianpaul, thanks. I will use that one /home/xilinx | 02:30 |
| kristianpaul | btw i'm lost, should i use rtems from the unoffial git repo in milkymist organizational page or rtems-old? | 02:31 |
| xiangfu | not rtems-old. | 02:32 |
| xiangfu | kristianpaul, use rtems.git and 'mmstaging' branch | 02:36 |
| kristianpaul | I'm using your script :) | 02:38 |
| kristianpaul | hum wheezy have autoconf 1.68-1 | 02:40 |
| kristianpaul | 2.68-1* | 02:40 |
| kristianpaul | arghhh i should had stay on fedora.... | 02:41 |
| kristianpaul | xiangfu: http://pastebin.com/wYpaddG3 | 02:42 |
| xiangfu | ? | 02:44 |
| kristianpaul | after make -C compile-flickernoise flickernoise.fbi | 02:45 |
| kristianpaul | steps 1 to 6 went okay it seems.. | 02:45 |
| kristianpaul | just telling :) | 02:45 |
| kristianpaul | i decide to clone that scripts folder today | 02:46 |
| aw | xiangfu, 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.bin | 02:46 |
| aw | [FLTERM] Starting... | 02:46 |
| aw | Segmentation fault | 02:46 |
| stekern | kristianpaul: that pastebin paste seems to be incomplete | 02:47 |
| kristianpaul | hum.. | 02:47 |
| kristianpaul | damn | 02:47 |
| wolfspraul | xiangfu: calling fwrite with a 0 file descriptor is not a good idea | 02:51 |
| xiangfu | wolfspraul, my fault. :( | 02:51 |
| wolfspraul | maybe you fix that too then Adam can do a git pull and make/install | 02:51 |
| xiangfu | sending new patch now | 02:51 |
| kristianpaul | fulllog http://pastebin.com/bhkgMyTy | 02:56 |
| stekern | kristianpaul: I think something is still missing | 02:57 |
| aw | xiangfu, so i can do git pull and make now? | 02:59 |
| xiangfu | aw, no. I don't have write access to milkymist.git. have to wait Sebastien apply the patch | 02:59 |
| aw | oah... i can use neither normal flterm command nor --log now..too bad. :( | 03:01 |
| kristianpaul | done, ISE 13.2 installed at /home/Xilinx/13.2 @ fidelio | 03:01 |
| xiangfu | aw, but you can manually apply it for temp. | 03:01 |
| kristianpaul | already licensed and smalltalk disabled | 03:01 |
| wolfspraul | how about --log /dev/null ? | 03:02 |
| wolfspraul | aw: try --log /dev/null | 03:02 |
| aw | xiangfu, yes, just no gedit support now | 03:02 |
| kristianpaul | xiangfu: i'll start over again rtems toolchain process | 03:02 |
| xiangfu | aw, under milkmist.git folder run: | 03:03 |
| xiangfu | wget http://downloads.qi-hardware.com/people/xiangfu/tmp/0001-tools-flterm-check-logfd-not-log-0x00-flush-each-lin.patch | 03:03 |
| kristianpaul | hum the end-of-line in flterm is just fun :) | 03:03 |
| xiangfu | git am 0001-tools-flterm-check-logfd-not-log-0x00-flush-each-lin.patch | 03:03 |
| xiangfu | aw, and make again. | 03:03 |
| wolfspraul | xiangfu: how about he just uses --log /dev/null for now | 03:04 |
| wolfspraul | xiangfu: can you test whether that works? | 03:04 |
| xiangfu | wolfspraul, yes. /dev/null works fine | 03:04 |
| wolfspraul | so 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 crash | 03:05 |
| xiangfu | should not write any C code before sleep | 03:12 |
| xiangfu | kristianpaul, the error I have is like: http://pastebin.com/aaE6PTGM | 03:18 |
| aw | xiangfu, 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-results | 03:20 |
| stekern | xiangfu: yeah, that's what I get too | 03:20 |
| aw | xiangfu, so I keep using this new 'flterm' patch...later you fix that which can use gedit. just ping me, thanks. | 03:21 |
| wpwrak | xiangfu: solution: don't sleep after writing code ! ;-) | 03:22 |
| xiangfu | aw, about 'gedit' just select one code and click 'retry' | 03:23 |
| xiangfu | encode like ISO or whateven and click 'retry' | 03:23 |
| aw | xiangfu, oah..yes, after select "Western" and clicked 'retry', then 'gedit' can read it then. thanks you! ;-) | 03:25 |
| xiangfu | stekern, 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 |
| stekern | xiangfu: CVS HEAD of rtems mainline I presume? | 03:27 |
| kristianpaul | yes | 03:32 |
| wolfspraul | xiangfu: I can reproduce the gedit problem. the warning goes away when I delete two 0xf7 characters in the log. | 03:34 |
| wolfspraul | some garbage from the serial console somewhere | 03:34 |
| xiangfu | wolfspraul, yes. when poweron/off the milkymist one | 03:34 |
| wolfspraul | so what are the solutions | 03:34 |
| stekern | what's up with the rtems people not using a sane vcs | 03:34 |
| wolfspraul | we could not log anything 0x80 or higher | 03:35 |
| xiangfu | wolfspraul, I think just leave them. garbage from serial is very normal | 03:35 |
| stekern | I mean, svn is bad enough, but cvs... common | 03:35 |
| wolfspraul | yes true | 03:35 |
| wolfspraul | but then maybe a marker at the beginning? should we write proper utf-8? | 03:35 |
| xiangfu | kristianpaul, stekern, I will add the patch to my script.git until it fixed. :) | 03:35 |
| wpwrak | stekern: hey, it surely beat the stone tablets they used before ! ;-) | 03:35 |
| stekern | wpwrak: :) | 03:36 |
| kristianpaul | xiangfu: i dont think my current issue is related to zlib,, | 03:36 |
| wolfspraul | maybe convert any character above 0x80 to a utf-8 sequence? | 03:36 |
| xiangfu | kristianpaul, I don't see the error from your pastebin | 03:36 |
| kristianpaul | me either.. | 03:36 |
| kristianpaul | is just that auto¨ | 03:37 |
| kristianpaul | *** | 03:37 |
| kristianpaul | agh | 03:37 |
| kristianpaul | wpwrak: nah, stone no, may be type writer? | 03:37 |
| wolfspraul | we assume the 8-bit incoming characters to be iso-8859-1 and write utf-8? that could make the warning go away | 03:37 |
| wolfspraul | xiangfu: can you reproduce the gedit warning? | 03:42 |
| xiangfu | wolfspraul, yes. that will be one solution. | 03:42 |
| xiangfu | wolfspraul, yes. I can, | 03:42 |
| wolfspraul | here'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 |
| wolfspraul | basically a c >= 0x80 becomes two fwrite | 03:43 |
| wolfspraul | then we write utf-8, and depending on Adam's locale settings and gedit assumptions/defaults, it may open without a warning | 03:43 |
| wolfspraul | MAY | 03:43 |
| wolfspraul | :-) | 03:44 |
| wolfspraul | but utf-8 is a good start I think | 03:44 |
| wolfspraul | I 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 |
| xiangfu | stekern, I am apply the patch, compiling now. if everything fine , I will push my commit to scripts.git for keep the patch | 03:45 |
| xiangfu | wolfspraul, ok. will try that code | 03:48 |
| stekern | xiangfu: sounds good | 03:50 |
| kristianpaul | xiangfu: my problem is with boostraping, i always got configure.ac:5: error: Autoconf version 2.68 or higher is required | 03:56 |
| xiangfu | kristianpaul, do you have autoconf 2.68 installed? | 03:58 |
| kristianpaul | no | 03:58 |
| kristianpaul | think in me like same debian as buildhost | 03:59 |
| kristianpaul | my autoconf is 2.67-2 | 03:59 |
| xiangfu | kristianpaul, have to update to 2.68 since Sebastien sync the rtems.git with upstream. | 04:00 |
| xiangfu | kristianpaul, then the buildhost will not compile either. | 04:00 |
| kristianpaul | hum... | 04:01 |
| xiangfu | kristianpaul, the solutions is add openwrt staging host bin to your PATH, | 04:01 |
| Action: kristianpaul *sigh* | 04:01 | |
| xiangfu | kristianpaul, if you in buildhost that will easy, there are openwrt-xburst.full_system under /home/xiangfu. | 04:01 |
| xiangfu | :) | 04:02 |
| kristianpaul | no no, more mixes of openwrt with this.. | 04:02 |
| xiangfu | wolfspraul, the code [: if (*in<128) *out++=*in++; else *out++=0xc2+(*in>0xbf), *out++=(*in++&0x3f)+0x80;] not working :( | 04:05 |
| wolfspraul | well | 04:05 |
| wolfspraul | of course that's just the numbers for the 0x80..0xFF to utf-8 conversion | 04:05 |
| kristianpaul | is not locales good for that convertion? (jsut a guess) | 04:06 |
| GitHub59 | [scripts] xiangfu pushed 1 new commit to master: http://git.io/cIaHYw | 04:07 |
| GitHub59 | [scripts/master] compile-flickernoise: fix zlib compile error - Xiangfu Liu | 04:07 |
| wolfspraul | 0x80..0bf becomes 0xc2 + 0x80..0xbf | 04:07 |
| xiangfu | stekern, ^ | 04:07 |
| wolfspraul | 0xc0 .. 0xff becomes 0xc3 + 0x80..0xbf | 04:07 |
| wolfspraul | if I read that snippet correctly... | 04:07 |
| wolfspraul | so 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 |
| wolfspraul | which editor can give me a hex editing view? | 04:09 |
| xiangfu | vim :!xxd | 04:09 |
| kristianpaul | phew seems installing autoconf_2.68-1_all.deb solves this problem :) | 04:10 |
| xiangfu | sorry | 04:10 |
| kristianpaul | hexedit i guess | 04:11 |
| xiangfu | wolfspraul, %!xxd | 04:11 |
| kristianpaul | oh, nice xiangfu :) | 04:12 |
| xiangfu | :%!xxd to convert to hex, :%!xxd -r to convert back | 04:12 |
| kristianpaul | but it actually is not updating ascii view after edit the hex equivalent is it? | 04:13 |
| xiangfu | kristianpaul, :%!xxd -r to convert back then save | 04:13 |
| wolfspraul | xiangfu: 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 warning | 04:16 |
| wolfspraul | my default console is utf-8 thought, so Adam may still get warnings depending which gedit version he has, his locale, etc. | 04:17 |
| wolfspraul | but I think we should write utf-8, why not | 04:17 |
| wolfspraul | xiangfu: is that 0xc2/0xc3 stuff clear? | 04:17 |
| wolfspraul | the line was meant to give you the numbers, not to copy/paste into your sources 1:1 | 04:18 |
| xiangfu | wolfspraul, ok. | 04:18 |
| wolfspraul | in your sources, it's something like if (c >= 0x80) { fwrite(0xc2+(c>0xbf)); fwrite(0x80+(c&0x3f)); } | 04:20 |
| wolfspraul | not to be copied 1:1 :-) | 04:20 |
| stekern | xiangfu: nice one, I'll pull and test | 04:26 |
| xiangfu | wolfspraul, 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 |
| wolfspraul | can your gedit open the resulting files without warnings now? | 04:36 |
| xiangfu | yes. without any warnings now | 04:37 |
| wolfspraul | nice | 04:38 |
| kristianpaul | okay i need that zlib patch now :) | 04:40 |
| xiangfu | my fault the flterm patch goes to Version V3 :( | 04:45 |
| stekern | xiangfu: that worked for me | 04:48 |
| kristianpaul | hum.. | 04:49 |
| kristianpaul | all | 04:49 |
| kristianpaul | ok | 04:49 |
| kristianpaul | bye | 05:00 |
| lekernel | xiangfu, what is that "utf-8" patch doing? | 09:44 |
| xiangfu | just convert the > 0x80 ASCII to utf-8. for avoid the editor can not open it. (like gedit) | 09:44 |
| lekernel | if(c >= 0x80) ... isn't char signed? | 09:45 |
| lekernel | also, is that really UTF8? | 09:46 |
| lekernel | why not simply drop those characters instead? | 09:46 |
| xiangfu | lekernel, yes. that is a solution, simple and clean. :) | 09:47 |
| lekernel | ok, please send a new patch | 09:51 |
| lekernel | and I guess you should check for c < 0 instead of c >= 0x80... no? (maybe I'm wrong) | 09:51 |
| lekernel | or use unsigned char ... I'm usually trying to avoid those corner cases :) | 09:52 |
| xiangfu | lekernel, I use 'if(isascii(c))' | 09:57 |
| lekernel | ok | 09:57 |
| xiangfu | sent out | 10:03 |
| wpwrak | fwiw, "char" can default to signed or unsigned. | 10:53 |
| kristianpaul | "or" dint sounded as default.. | 10:57 |
| kristianpaul | how you force it? | 10:57 |
| wpwrak | well, that depends on the compiler :) | 10:59 |
| wpwrak | e.g., in gcc, you have -fsigned-char, -funsigned-char, and also the equivalent -fno-unsigned-char and -fno-signed-char | 11:00 |
| wpwrak | hmm, 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 signed | 11:02 |
| kristianpaul | he, i was about to make a joke a bout sdcc xD | 11:05 |
| kristianpaul | s/bout/about | 11:05 |
| kristianpaul | wow sdcc is version 3 now | 11:06 |
| wpwrak | still buggy, though :-( | 11:33 |
| wpwrak | but better than before | 11:33 |
| lekernel | wpwrak, 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 |
| Fallenou | I didn't know, usually I assume char is signed | 11:55 |
| lekernel | yeah, that's the right thing to do | 11:56 |
| Fallenou | I thought by default all the types were signed by default unless you say (unsigned) | 11:56 |
| lekernel | this mess with the C types is just stupid and wasting everyone's time | 11:56 |
| Fallenou | clearly | 11:56 |
| Fallenou | I guess that's why people use uint8_t and such instead of primitif types | 11:56 |
| lekernel | the standard should simply say things like int = 32 bits, short int = 16 bits, char = 8 bits, and all types are signed by default | 11:56 |
| Fallenou | char = 8 bits is usually the case (don't know of any exception), but short int ... I think it depends, and that sucks | 11:57 |
| stekern | char = 16 bit with TI C2000 compiler | 12:23 |
| Fallenou | nice ! | 12:23 |
| wpwrak | lekernel: that's why we have int32_t, uint16_t, etc. they're good. use them ;-) | 12:25 |
| lekernel | but they're not integrated in the compiler and sometimes result in a include file mess | 12:26 |
| stekern | I wonder how many programs written for x86 have got bitten by bugs when assuming unsigned long = 32 bits | 12:28 |
| stekern | or just plain long for that matter | 12:28 |
| stekern | isn't stdint.h part of C99 btw? | 12:36 |
| wpwrak | it'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 |
| wpwrak | M1 arrived ! :) | 16:40 |
| kristianpaul | Good !! | 16:46 |
| kristianpaul | Does it boot? ;) | 16:51 |
| wpwrak | assembling the case ... | 16:55 |
| wpwrak | case design feedback for the next version: the power input should also mention how much current it draws | 16:58 |
| wpwrak | now, find a power supply ... | 17:00 |
| kristianpaul | hum.. | 17:04 |
| kristianpaul | i still wondering why you dont pay taxes for it | 17:08 |
| wpwrak | oh, 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 days | 17: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, perfect | 17:16 | |
| Action: wpwrak hopes 2500 mA are enough | 17:16 | |
| wpwrak | wikipedia says 5 W. excellent. that's plenty. | 17:17 |
| wpwrak | it gets as far as "press Esc for console" | 17:19 |
| wpwrak | locating keyboard ... | 17:20 |
| wpwrak | aah, effects ! :) | 17:20 |
| wpwrak | just have to wait before it does somethign, it seems ;-) | 17:21 |
| wpwrak | marvels at the coolness of the video effects | 17:23 |
| wpwrak | "esc for console", when exactly does this work ? when the Milkymist logo with that message is shown ? or also later ? | 17:26 |
| kristianpaul | clap clap ! | 17:32 |
| wpwrak | still haven't gotten it to talk to anything USB yet | 17:35 |
| wpwrak | eeh, kewl. of all devices, my little wireless remote keyboard works ;-) | 17:35 |
| wpwrak | at least with the console. no response under FN | 17:38 |
| wpwrak | the 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 action | 17:41 |
| wpwrak | the "stricken" aircrash looks cool | 17:44 |
| wpwrak | and the one following it has very nice colors | 17:44 |
| wpwrak | (the wiggling square) just the white line in the middle looks like a rendering error | 17:44 |
| wpwrak | can USB hot-plug ? or do i have to power-cycle for new devices to be recognized ? | 17:48 |
| lekernel | usb hotplug works | 17:56 |
| lekernel | both the console and FN use the same code for USB, so you have probably spotted one of those pesky intermittent bugs | 17:56 |
| wpwrak | ;-)) | 17:56 |
| wpwrak | or maybe i'm just not using it right | 17:57 |
| lekernel | you shouldn't see the splash screen with "press esc for console", unless you are in rescue mode or pressed the power button for > ~1s | 17:57 |
| wpwrak | when 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 |
| lekernel | blue screen is probably missing camera input | 17:58 |
| wpwrak | (i don't get a mouse response, but that may be just a problem of my RF keyboard) | 17:58 |
| lekernel | use ESC to leave render mode, not update ... | 17:58 |
| lekernel | or enter | 17:59 |
| wpwrak | aah, Esc also works in render mode. i see | 17:59 |
| wpwrak | booting again | 17:59 |
| lekernel | you can move the mouse cursor with the keyboard, see http://www.milkymist.org/leaflets/run3_leaflet.pdf | 17:59 |
| wpwrak | hmm, 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 nonsense | 18:02 |
| wpwrak | ah, i have better luck with some cheap crap keyboard | 18:03 |
| wpwrak | it doesn't like my kensington mouse, though | 18:04 |
| wpwrak | works with a Microsoft mouse. you should watch the company your child keeps ! :) | 18:05 |
| wpwrak | okay, looking good so far. now i have to leave for a bit. more experimenting later. | 18:05 |
| lekernel | meta key = windows key | 18:05 |
| wpwrak | win = 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_w | 18:23 |
| GitHub92 | [milkymist/master] tools: flterm: check logfd, check ascii, flush each line - Xiangfu Liu | 18:23 |
| kristianpaul | win 19 | 18:27 |
| wpwrak | will 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 |
| wpwrak | roh: should i expect any trouble when gluing the buttons with regular superglue ? (liquid, not the messy gel) | 20:55 |
| roh | wpwrak: its messy and tends to break if you put on mechanical stress | 21:08 |
| roh | ;) | 21:08 |
| roh | wpwrak: but the buttons on the new parts i shipped in the last batch are already glued | 21:09 |
| wpwrak | the ones i got are in parts. well, so maybe double-faced tape then | 21:34 |
| lekernel | if you go for the superglue, the most important thing is not to use too much | 21:41 |
| lekernel | otherwise it leaks from the sides and creates a mess | 21:41 |
| lekernel | there won't be kits I think | 21:42 |
| xiangfu | lekernel, Hi | 23:43 |
| --- Fri Aug 26 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!