| 00:44.46 | *** join/#qi-hardware cladamw (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 00:54.42 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 01:08.35 | *** join/#qi-hardware Jay7 (jay@78-106-209-252.broadband.corbina.ru) |
| 01:09.00 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 01:11.14 | qi-bot | The build has FAILED: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/openwrt-xburst.full_system-20120325-2303 |
| 01:13.03 | xiangfu | hmm... |
| 01:13.57 | wolfspraul | xiangfu: hey good morning :-) |
| 01:14.06 | xiangfu | good morning. |
| 01:14.16 | wolfspraul | good morning dear troubles |
| 01:14.18 | wolfspraul | :-) |
| 01:14.23 | wolfspraul | (reference to the failing build) |
| 01:17.24 | xiangfu | I work on the build host yesterday. update the config file. include package that fixed. |
| 01:17.52 | xiangfu | let's wait next build. |
| 01:18.39 | xiangfu | I have added those 2 usb device to http://en.qi-hardware.com/wiki/Milkymist_One_accessories#USB. |
| 01:19.26 | xiangfu | no picture yet. too late yesterday. I will upload 2 pictures and put more information in that page. |
| 01:19.31 | wolfspraul | ah yes, nice |
| 01:19.40 | wolfspraul | we should document a number of usb devices and why they do not work |
| 01:19.48 | wolfspraul | as inspiration and todo list, if an interested hacker comes along |
| 01:19.54 | wolfspraul | what do we have? |
| 01:19.57 | wolfspraul | usb speakers |
| 01:20.06 | wolfspraul | usb audio cards/mic |
| 01:20.22 | wolfspraul | usb video capture and tv as you have there |
| 01:20.34 | wolfspraul | usb-midi, already working to a degree |
| 01:20.40 | wolfspraul | usb storage |
| 01:20.46 | wolfspraul | usb webcam |
| 01:21.32 | wolfspraul | what else? |
| 01:21.57 | wolfspraul | usb-ethernet maybe for completeness, although m1 has a built-in ethernet of course |
| 01:22.09 | wolfspraul | of course usb mice & kbd, we have those already |
| 01:22.21 | wolfspraul | usb-wifi |
| 01:23.01 | wolfspraul | there's some nice and cheap tablets like the wacom tablets (but cheap no-name) |
| 01:23.23 | wolfspraul | yeah |
| 01:23.30 | wolfspraul | enough :-) |
| 01:23.37 | wolfspraul | for most of those we just document that and why they don't work :-) |
| 01:48.46 | 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:51.49 | wolfspraul | Wikipedia |
| 01:52.03 | wolfspraul | (without looking at either one) |
| 01:52.24 | wolfspraul | when in doubt, reuse and make references to stuff on wikipedia |
| 01:52.40 | wolfspraul | if we do something different and follow a vendor, we must be really sure about that, then it's ok |
| 01:52.44 | *** join/#qi-hardware wej (~j@m2.mullvad.net) |
| 01:52.57 | wolfspraul | let's see what werner says about the specific symbol :-) |
| 01:53.33 | wpwrak | hmm, what would be the wikipedia symbol ? i don't see any on http://en.wikipedia.org/wiki/Varistor |
| 01:54.24 | 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.58 | 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:55.11 | wpwrak | ;-)) |
| 01:56.26 | wpwrak | compare this with http://en.wikipedia.org/wiki/Thermistor |
| 01:56.48 | cladamw | Wikipedia is the same symbol as Littlefuse, but still not the same as KiCad part "VR" component in library: /library/device.lib |
| 01:57.41 | cladamw | man ! i think that Chinese Wikipedia is unreliable. :-) |
| 01:57.46 | wpwrak | hmm, varistor = overvoltage protection. thermistor = overcurrent protection. don't confuse the two :) |
| 01:58.35 | wpwrak | "VR" may be just the symbol for a general variable resistor of unspecified nature. lemme check ... |
| 01:58.46 | 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:59.46 | cladamw | KiCad calls "VARISTANCE" in its "Description" |
| 02:00.56 | 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:02.16 | cladamw | eg. : http://dpaste.com/721899/ |
| 02:03.02 | cladamw | eg. : http://dpaste.com/721901/ |
| 02:04.16 | 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:05.03 | cladamw | then load that component into KiCad Library Editor, it shows directly into GUI. |
| 02:05.31 | wpwrak | IEC has S00558 for voltage-dependent resistors. but note the "U" |
| 02:05.42 | cladamw | (i.e.) your boom should directly generate datasheet link to find parts in Digikey from *.dcm file |
| 02:06.00 | wpwrak | i wouldn't maintain such information in .dcm. they're too messy to edit |
| 02:06.25 | wpwrak | better have a separate file with human-friendly text. like the BOOKSHELF files |
| 02:06.54 | wpwrak | then populate .dcm with a script if necessary. note that you'll probably lose local caching this way, though |
| 02:07.08 | 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.47 | wpwrak | yes, but good luck finding _the_ data sheet for, say, varistors ;-) |
| 02:08.42 | cladamw | so how do you think that i directly to use vendor's symbol ? |
| 02:10.09 | wpwrak | cool. IEC have no thermistor, no PTC, no NTC. no surprise there's such a chaos |
| 02:11.54 | 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:12.24 | cladamw | i lilke to do this way if you still against ? |
| 02:12.27 | cladamw | :-) |
| 02:14.44 | 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:15.52 | wpwrak | i think the two symbols represent different technologies and different physical principles to arrive at the same result |
| 02:16.36 | wpwrak | since we often don't care what technology is inside the chip, we have a 50% chance of getting the symbol right :) |
| 02:17.38 | cladamw | yes, so they may be just suffering from patent conflicts. |
| 02:19.06 | wpwrak | no, not that. it's just different physics |
| 02:19.12 | cladamw | i think the library for chip varistors, maybe i just call it "chipvaristors.lib', is that okay to you ? |
| 02:19.43 | 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:20.06 | cladamw | whatever their physics, they are the varistors. :-) |
| 02:22.03 | cladamw | i am thinking the qi's libraries(components/modules). How we gather/collect those parts we're using now. :-) |
| 02:22.56 | wpwrak | here we have all the technologies: http://www.learnemc.com/tutorials/Transient_Protection/t-protect.html |
| 02:23.05 | wpwrak | see, there's more than one way to do this :) |
| 02:24.46 | cladamw | he, nice link. |
| 02:25.18 | 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.27 | wpwrak | i've never seen this used in practice |
| 02:27.50 | wpwrak | http://www.talkingelectronics.com/CctSymbols/Circuit_Symbols.html |
| 02:27.55 | wpwrak | uses the kicad symbol |
| 02:28.10 | wpwrak | and even shows the Zener equivalence |
| 02:29.46 | cladamw | mmm...left one is the same as TDK's symbol. |
| 02:29.47 | wpwrak | seems to be the best compromise |
| 02:31.51 | wpwrak | they have a total of three variants ;-) also the one from the chinese wikipedia. and weird Z(orro?)-shaped one |
| 02:32.13 | wpwrak | well, that's the same as TDK's |
| 02:32.32 | wpwrak | never saw that anywhere else either |
| 02:32.57 | wpwrak | by the way, there's about half a dozen IEC symbols for spark gaps ;-))) |
| 02:35.00 | cladamw | yeah...great link, so we can take this url for example to create/naming libraries, okay ? |
| 02:40.20 | wpwrak | okay. it's a start :) |
| 02:41.30 | cladamw | great, thanks for your great surf skills in google. ;-) |
| 02:43.14 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 02:43.54 | cladamw | so for (V24), i should use a name for Voltage Dependent Resistor, i.e. vdr.lib |
| 02:46.14 | wpwrak | everybody seems to use varistor ... |
| 02:47.56 | cladamw | phew~ alright, name it as 'varistor.lib' ;-) |
| 02:49.00 | wolfspraul | surf skills :-) |
| 02:52.02 | wpwrak | and now, dinner-eating skills :) |
| 04:30.49 | *** join/#qi-hardware wolfspraul (~wolfsprau@114.241.246.140) |
| 05:07.06 | *** join/#qi-hardware orsonzhai (~zhai@1.202.15.210) |
| 05:46.47 | *** join/#qi-hardware cladamw (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 05:49.48 | *** join/#qi-hardware wolfspraul (~wolfsprau@114.241.246.140) |
| 05:50.21 | *** join/#qi-hardware jekhor (~jek@77.215.97.60) |
| 05:56.41 | xiangfu | A New Milkymist Firmware Release: http://en.qi-hardware.com/wiki/Milkymist_One_Firmware#2012-03-27 |
| 05:56.46 | xiangfu | I am still testing... |
| 05:56.53 | xiangfu | so far so good :-) |
| 05:57.26 | xiangfu | the MIC boost make Mic works much better then before. |
| 06:06.04 | 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.29 | xiangfu | kyak, already disabled. :) |
| 06:06.38 | kyak | great :) |
| 06:06.53 | kyak | now we just wait till we hit the qt4 compilation issue... |
| 06:07.30 | kyak | ah, mirko has fixed it.. great |
| 06:08.16 | 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.32 | xiangfu | kyak, ok |
| 06:08.54 | xiangfu | kyak, just send them to me |
| 06:11.55 | xiangfu | cladamw, here. I just upload a new release. that I am testing... |
| 06:12.15 | xiangfu | cladamw, if this M1 is for ship out. please reflash again. |
| 06:12.33 | xiangfu | I just fixed the 'latest' symlink. |
| 06:12.50 | cladamw | xiangfu, oah..okay, i tried it again. :-) |
| 06:12.56 | xiangfu | reflash again with 'reflash_m1.sh --qi --data', if if for ship out don't forget reflash the mac address. |
| 06:13.13 | cladamw | sure. ;-) |
| 06:14.01 | xiangfu | there is a MIC improve. :-) |
| 06:14.08 | xiangfu | in next release. |
| 06:14.25 | cladamw | xiangfu, aha...okay.. btw, i recorded my steps here: https://github.com/adamwang/script/blob/master/m1_reflash_steps |
| 06:15.13 | cladamw | since sometimes if steps of reflash for ship out has been changed, i have to record myself though. :-) |
| 06:15.35 | xiangfu | cool :) |
| 06:16.07 | xiangfu | watched. :) |
| 06:17.52 | 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:19.09 | cladamw | I'll just ping you when i get stuck. :) |
| 06:21.08 | xiangfu | ok |
| 06:58.58 | qi-bot | [commit] Xiangfu: nanonote-files: config.full_system use DirectFB as drawing-backend (master) http://qi-hw.com/p/openwrt-packages/37a4be2 |
| 07:01.04 | *** join/#qi-hardware jurting (~jommpa90_@ip-234-208-230-46.dialup.ice.net) |
| 07:05.13 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 07:23.38 | 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:24.31 | 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:36.57 | *** join/#qi-hardware tonghuix (~tonghuix@221.219.124.242) |
| 07:47.45 | xiangfu | kyak, https://dev.openwrt.org/ticket/11188 <--- reported. |
| 07:47.48 | xiangfu | thanks again |
| 08:02.46 | *** join/#qi-hardware uwe_ (~uwe_@p57AE952E.dip0.t-ipconnect.de) |
| 08:27.41 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 09:08.54 | *** join/#qi-hardware Ayla (~paul@53.121.101.84.rev.sfr.net) |
| 09:49.02 | *** join/#qi-hardware pabs3 (~pabs@d122-109-116-184.per801.wa.optusnet.com.au) |
| 09:51.34 | *** join/#qi-hardware antoniodariush (~antonioda@nat-sta-slph1.tvu.ac.uk) |
| 10:04.22 | *** join/#qi-hardware jivs (~jivs@nat-sta-slph1.tvu.ac.uk) |
| 10:18.37 | *** join/#qi-hardware wolfspraul (~wolfsprau@114.241.246.140) |
| 10:51.22 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 10:52.22 | *** join/#qi-hardware DocScrutinizer (~halley@openmoko/engineers/joerg) |
| 11:11.26 | *** join/#qi-hardware uwe___ (~uwe_@p57AE9683.dip0.t-ipconnect.de) |
| 11:55.48 | *** join/#qi-hardware tonghuix (~tonghuix@123.115.187.201) |
| 12:01.30 | *** join/#qi-hardware cladamw (~adamwang@host-222.80-43-115.dynamic.totalbb.net.tw) |
| 12:49.57 | qi-bot | [commit] Adam Wang: added few symbols (master) http://qi-hw.com/p/kicad-libs/c903a7a |
| 13:03.04 | *** join/#qi-hardware rektide (~rektide@deneb.eldergods.com) |
| 13:16.10 | jluis | top |
| 13:30.35 | *** join/#qi-hardware tonghuix (~tonghuix@123.115.187.201) |
| 13:54.32 | *** join/#qi-hardware urandom__ (~user@ip-88-152-192-240.unitymediagroup.de) |
| 14:19.15 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-41-219.w109-223.abo.wanadoo.fr) |
| 14:26.17 | *** join/#qi-hardware pabs3 (~pabs@d122-109-116-184.per801.wa.optusnet.com.au) |
| 14:31.57 | mirko | is somebody using python on the nanonote? |
| 14:34.15 | 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 |
| 15:19.53 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 15:44.32 | *** join/#qi-hardware emeb (~ericb@ip72-223-81-94.ph.ph.cox.net) |
| 16:46.00 | mirko | wolfspraul: ping |
| 16:46.04 | mirko | larsc: ping |
| 17:37.08 | *** join/#qi-hardware viric_ (~viric@unaffiliated/viric) |
| 18:01.25 | *** join/#qi-hardware viric_ (~viric@unaffiliated/viric) |
| 18:05.23 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-41-219.w109-223.abo.wanadoo.fr) |
| 18:19.25 | *** join/#qi-hardware zenlunatic (~justin@c-68-48-40-231.hsd1.md.comcast.net) |
| 18:53.39 | *** join/#qi-hardware Ayla (~paul@186.132.123.78.rev.sfr.net) |
| 18:54.27 | *** join/#qi-hardware GNUtoo (~gnutoo@host149-73-dynamic.56-82-r.retail.telecomitalia.it) |
| 19:47.49 | larsc | mirko: pong |
| 19:49.06 | whitequark | 121 minute rtt |
| 19:58.10 | larsc | well, he hasn't received the response yet |
| 20:18.45 | *** join/#qi-hardware jekhor (~jek@c-83-233-149-204.cust.bredband2.com) |
| 20:45.49 | *** join/#qi-hardware jekhor (~jek@c-83-233-149-204.cust.bredband2.com) |
| 21:31.00 | Ayla | larsc: maybe he's UDP |
| 21:36.53 | whitequark | larsc: I have been measuring rtt to you using irc as a zero point |
| 22:58.44 | wolfspraul | mirko: pong |
| 22:59.23 | wolfspraul | didn't he say something about drinking last night? :-) |
| 23:03.01 | *** join/#qi-hardware wolfspraul (~wolfsprau@114.241.246.140) |
| 23:10.33 | wpwrak | if he's been drinking for the last 6 hours, he may slowly begin to show some effects :) |
| 23:12.30 | whitequark | Ayla: LOL |
| 23:12.33 | whitequark | http://www.wired.com/wiredenterprise/2012/03/ms-patent/?intcid=story_ribbon |
| 23:14.16 | whitequark | well I advise everybody here to read that |
| 23:14.19 | whitequark | very on topic :D |
| 23:16.05 | Ayla | yeah |
| 23:51.38 | *** join/#qi-hardware zrafa_ (~rafa@190.14.174.29) |
| 23:57.43 | *** join/#qi-hardware dvdk (~dvdkhlng@g225038140.adsl.alicedsl.de) |