| qi-bot | The build has FAILED: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/openwrt-xburst.full_system-20120325-2303 | 01:11 |
|---|---|---|
| xiangfu | hmm... | 01:13 |
| wolfspraul | xiangfu: hey good morning :-) | 01:13 |
| xiangfu | good morning. | 01:14 |
| wolfspraul | good morning dear troubles | 01:14 |
| wolfspraul | :-) | 01:14 |
| wolfspraul | (reference to the failing build) | 01:14 |
| xiangfu | I work on the build host yesterday. update the config file. include package that fixed. | 01:17 |
| xiangfu | let's wait next build. | 01:17 |
| xiangfu | I have added those 2 usb device to http://en.qi-hardware.com/wiki/Milkymist_One_accessories#USB. | 01:18 |
| xiangfu | no picture yet. too late yesterday. I will upload 2 pictures and put more information in that page. | 01:19 |
| wolfspraul | ah yes, nice | 01:19 |
| wolfspraul | we should document a number of usb devices and why they do not work | 01:19 |
| wolfspraul | as inspiration and todo list, if an interested hacker comes along | 01:19 |
| wolfspraul | what do we have? | 01:19 |
| wolfspraul | usb speakers | 01:19 |
| wolfspraul | usb audio cards/mic | 01:20 |
| wolfspraul | usb video capture and tv as you have there | 01:20 |
| wolfspraul | usb-midi, already working to a degree | 01:20 |
| wolfspraul | usb storage | 01:20 |
| wolfspraul | usb webcam | 01:20 |
| wolfspraul | what else? | 01:21 |
| wolfspraul | usb-ethernet maybe for completeness, although m1 has a built-in ethernet of course | 01:21 |
| wolfspraul | of course usb mice & kbd, we have those already | 01:22 |
| wolfspraul | usb-wifi | 01:22 |
| wolfspraul | there's some nice and cheap tablets like the wacom tablets (but cheap no-name) | 01:23 |
| wolfspraul | yeah | 01:23 |
| wolfspraul | enough :-) | 01:23 |
| wolfspraul | for most of those we just document that and why they don't work :-) | 01:23 |
| cladamw | wpwrak, i think that the symbol of Varistor i didn't use common one in AD m1r4 sch, in KiCad, its varistor is the same as Wikipedia, but TDK uses a different one from its datasheet. so what would you suggest ? | 01:48 |
| wolfspraul | Wikipedia | 01:51 |
| wolfspraul | (without looking at either one) | 01:52 |
| wolfspraul | when in doubt, reuse and make references to stuff on wikipedia | 01:52 |
| wolfspraul | if we do something different and follow a vendor, we must be really sure about that, then it's ok | 01:52 |
| wolfspraul | let's see what werner says about the specific symbol :-) | 01:52 |
| wpwrak | hmm, what would be the wikipedia symbol ? i don't see any on http://en.wikipedia.org/wiki/Varistor | 01:53 |
| cladamw | wpwrak, page 3 of http://www.tdk.co.jp/tefe02/e9c11_avr.pdf , page 22 of http://www.littelfuse.com/data/en/Product_Catalogs/Littelfuse_Varistors_Catalog.pdf | 01:54 |
| cladamw | if you clicked in Chinese version wikipedia, see http://zh.wikipedia.org/wiki/%E5%A3%93%E6%95%8F%E9%9B%BB%E9%98%BB | 01:54 |
| wpwrak | ;-)) | 01:55 |
| wpwrak | compare this with http://en.wikipedia.org/wiki/Thermistor | 01:56 |
| cladamw | Wikipedia is the same symbol as Littlefuse, but still not the same as KiCad part "VR" component in library: /library/device.lib | 01:56 |
| cladamw | man ! i think that Chinese Wikipedia is unreliable. :-) | 01:57 |
| wpwrak | hmm, varistor = overvoltage protection. thermistor = overcurrent protection. don't confuse the two :) | 01:57 |
| wpwrak | "VR" may be just the symbol for a general variable resistor of unspecified nature. lemme check ... | 01:58 |
| cladamw | yeah....but they are easy to confuse. so I think when I create new symbol that I should follow vendor's symbol, how do you think ? | 01:58 |
| cladamw | KiCad calls "VARISTANCE" in its "Description" | 01:59 |
| cladamw | now i think those *.dcm file, we should always to fill p/n, description, datasheet link, then in Library Editor it will show up very good information. | 02:00 |
| cladamw | eg. : http://dpaste.com/721899/ | 02:02 |
| cladamw | eg. : http://dpaste.com/721901/ | 02:03 |
| cladamw | said that we could have different projects with different vendor p/n, the *.dcm file is good to fill up specific datasheet link, description, p/n. | 02:04 |
| cladamw | then load that component into KiCad Library Editor, it shows directly into GUI. | 02:05 |
| wpwrak | IEC has S00558 for voltage-dependent resistors. but note the "U" | 02:05 |
| cladamw | (i.e.) your boom should directly generate datasheet link to find parts in Digikey from *.dcm file | 02:05 |
| wpwrak | i wouldn't maintain such information in .dcm. they're too messy to edit | 02:06 |
| wpwrak | better have a separate file with human-friendly text. like the BOOKSHELF files | 02:06 |
| wpwrak | then populate .dcm with a script if necessary. note that you'll probably lose local caching this way, though | 02:06 |
| cladamw | well...since I am editing those new components for m1r4, I can still fill them into *.dcm file, since KiCad uses it(fields) for part information to fill up. | 02:07 |
| wpwrak | yes, but good luck finding _the_ data sheet for, say, varistors ;-) | 02:07 |
| cladamw | so how do you think that i directly to use vendor's symbol ? | 02:08 |
| wpwrak | cool. IEC have no thermistor, no PTC, no NTC. no surprise there's such a chaos | 02:10 |
| cladamw | hmm....i think that I follow the vendor datasheets to create 'varistors.lib' to include different vendor varistors, they will be added into varistors.dcm & varistors.lib :-) | 02:11 |
| cladamw | i lilke to do this way if you still against ? | 02:12 |
| cladamw | :-) | 02:12 |
| cladamw | we're not a super team on parts management in naming whole libraries systems. ;-) I would speed up to append. then we sometimes or later to clean up ? | 02:14 |
| wpwrak | i think the two symbols represent different technologies and different physical principles to arrive at the same result | 02:15 |
| wpwrak | since we often don't care what technology is inside the chip, we have a 50% chance of getting the symbol right :) | 02:16 |
| cladamw | yes, so they may be just suffering from patent conflicts. | 02:17 |
| wpwrak | no, not that. it's just different physics | 02:19 |
| cladamw | i think the library for chip varistors, maybe i just call it "chipvaristors.lib', is that okay to you ? | 02:19 |
| wpwrak | some use the Zener effect, others use some other effect. there are many ways to get something to conduct when there's overvoltage. spark gaps, anyone ? ;-) | 02:19 |
| cladamw | whatever their physics, they are the varistors. :-) | 02:20 |
| cladamw | i am thinking the qi's libraries(components/modules). How we gather/collect those parts we're using now. :-) | 02:22 |
| wpwrak | here we have all the technologies: http://www.learnemc.com/tutorials/Transient_Protection/t-protect.html | 02:22 |
| wpwrak | see, there's more than one way to do this :) | 02:23 |
| cladamw | he, nice link. | 02:24 |
| wpwrak | the IEC symbol would be like the kicad symbol or maybe even the thermistor symbol (it's very poorly drawn), but with an U letter on the side | 02:25 |
| wpwrak | i've never seen this used in practice | 02:25 |
| wpwrak | http://www.talkingelectronics.com/CctSymbols/Circuit_Symbols.html | 02:27 |
| wpwrak | uses the kicad symbol | 02:27 |
| wpwrak | and even shows the Zener equivalence | 02:28 |
| cladamw | mmm...left one is the same as TDK's symbol. | 02:29 |
| wpwrak | seems to be the best compromise | 02:29 |
| wpwrak | they have a total of three variants ;-) also the one from the chinese wikipedia. and weird Z(orro?)-shaped one | 02:31 |
| wpwrak | well, that's the same as TDK's | 02:32 |
| wpwrak | never saw that anywhere else either | 02:32 |
| wpwrak | by the way, there's about half a dozen IEC symbols for spark gaps ;-))) | 02:32 |
| cladamw | yeah...great link, so we can take this url for example to create/naming libraries, okay ? | 02:35 |
| wpwrak | okay. it's a start :) | 02:40 |
| cladamw | great, thanks for your great surf skills in google. ;-) | 02:41 |
| cladamw | so for (V24), i should use a name for Voltage Dependent Resistor, i.e. vdr.lib | 02:43 |
| wpwrak | everybody seems to use varistor ... | 02:46 |
| cladamw | phew~ alright, name it as 'varistor.lib' ;-) | 02:47 |
| wolfspraul | surf skills :-) | 02:49 |
| wpwrak | and now, dinner-eating skills :) | 02:52 |
| xiangfu | A New Milkymist Firmware Release: http://en.qi-hardware.com/wiki/Milkymist_One_Firmware#2012-03-27 | 05:56 |
| xiangfu | I am still testing... | 05:56 |
| xiangfu | so far so good :-) | 05:56 |
| xiangfu | the MIC boost make Mic works much better then before. | 05:57 |
| kyak | xiangfu: hi! i think we need to disable xfce repo in feeds.conf for good. Only need to have qi-packages, packages, desktop and xorg. What do you think? | 06:06 |
| xiangfu | kyak, already disabled. :) | 06:06 |
| kyak | great :) | 06:06 |
| kyak | now we just wait till we hit the qt4 compilation issue... | 06:06 |
| kyak | ah, mirko has fixed it.. great | 06:07 |
| kyak | xiangfu: i tried to have a look an ncursesw problem.. This is magic.. Do you mind i paste you something in pm in order not to clutter the channel? | 06:08 |
| xiangfu | kyak, ok | 06:08 |
| xiangfu | kyak, just send them to me | 06:08 |
| xiangfu | cladamw, here. I just upload a new release. that I am testing... | 06:11 |
| xiangfu | cladamw, if this M1 is for ship out. please reflash again. | 06:12 |
| xiangfu | I just fixed the 'latest' symlink. | 06:12 |
| cladamw | xiangfu, oah..okay, i tried it again. :-) | 06:12 |
| xiangfu | reflash again with 'reflash_m1.sh --qi --data', if if for ship out don't forget reflash the mac address. | 06:12 |
| cladamw | sure. ;-) | 06:13 |
| xiangfu | there is a MIC improve. :-) | 06:14 |
| xiangfu | in next release. | 06:14 |
| cladamw | xiangfu, aha...okay.. btw, i recorded my steps here: https://github.com/adamwang/script/blob/master/m1_reflash_steps | 06:14 |
| cladamw | since sometimes if steps of reflash for ship out has been changed, i have to record myself though. :-) | 06:15 |
| xiangfu | cool :) | 06:15 |
| xiangfu | watched. :) | 06:16 |
| cladamw | no need to watch that. it's my own tool. :-) well...since my steps will always comes from you. you know that i still can't interpret/understand script. :-O | 06:17 |
| cladamw | I'll just ping you when i get stuck. :) | 06:19 |
| xiangfu | ok | 06:21 |
| qi-bot | [commit] Xiangfu: nanonote-files: config.full_system use DirectFB as drawing-backend (master) http://qi-hw.com/p/openwrt-packages/37a4be2 | 06:58 |
| qi-bot | [commit] Xiangfu: package: ncurses: fix the libncursesw disappears when select some package thanks to kyak (release_2012-03-18) http://qi-hw.com/p/openwrt-xburst/657d4c7 | 07:23 |
| qi-bot | [commit] Xiangfu: package: ncurses: fix the libncursesw disappears when select some package thanks to kyak (master) http://qi-hw.com/p/openwrt-xburst/c475dd5 | 07:24 |
| xiangfu | kyak, https://dev.openwrt.org/ticket/11188 <--- reported. | 07:47 |
| xiangfu | thanks again | 07:47 |
| qi-bot | [commit] Adam Wang: added few symbols (master) http://qi-hw.com/p/kicad-libs/c903a7a | 12:49 |
| jluis | top | 13:16 |
| mirko | is somebody using python on the nanonote? | 14:31 |
| mirko | if so, are you willing to test the following python-upgrade with the apps you use? - https://dev.openwrt.org/raw-attachment/ticket/11157/python-2.7.3rc2.diff | 14:34 |
| mirko | wolfspraul: ping | 16:46 |
| mirko | larsc: ping | 16:46 |
| larsc | mirko: pong | 19:47 |
| whitequark | 121 minute rtt | 19:49 |
| larsc | well, he hasn't received the response yet | 19:57 |
| Ayla | larsc: maybe he's UDP | 21:31 |
| whitequark | larsc: I have been measuring rtt to you using irc as a zero point | 21:36 |
| wolfspraul | mirko: pong | 22:58 |
| wolfspraul | didn't he say something about drinking last night? :-) | 22:59 |
| wpwrak | if he's been drinking for the last 6 hours, he may slowly begin to show some effects :) | 23:10 |
| whitequark | Ayla: LOL | 23:12 |
| whitequark | http://www.wired.com/wiredenterprise/2012/03/ms-patent/?intcid=story_ribbon | 23:12 |
| whitequark | well I advise everybody here to read that | 23:14 |
| whitequark | very on topic :D | 23:14 |
| Ayla | yeah | 23:16 |
| --- Wed Mar 28 2012 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!