IRC log for #qi-hardware on 20120421

01:18.20*** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com)
01:52.47*** join/#qi-hardware wej (~j@95.211.10.3)
03:04.30*** join/#qi-hardware Openfree` (~Openfreer@116.228.88.131)
05:09.51*** join/#qi-hardware xwalk (~crosswalk@rrcs-98-102-156-195.central.biz.rr.com)
05:14.38*** join/#qi-hardware xwalk (~crosswalk@rrcs-98-102-156-195.central.biz.rr.com)
05:40.23*** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com)
06:16.09*** join/#qi-hardware panda|x201 (~hzhang@123.116.115.164)
06:18.01*** join/#qi-hardware xwalk (~crosswalk@rrcs-98-102-156-195.central.biz.rr.com)
06:41.52*** join/#qi-hardware Martix (~martix@vpn-konference.ms.mff.cuni.cz)
06:52.34*** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com)
07:04.07*** part/#qi-hardware emeb (~ericb@ip72-223-81-94.ph.ph.cox.net)
07:25.15viricmth: ok, thank you!
07:31.46*** join/#qi-hardware DocScrutinizer (~halley@openmoko/engineers/joerg)
07:33.07*** join/#qi-hardware jekhor (~jek@46.53.195.29)
08:47.54*** join/#qi-hardware Jay7 (jay@2.92.36.233)
09:35.08*** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com)
10:28.20*** join/#qi-hardware Textmode_ (~boneidle@adsl-syd-4-20.ozonline.com.au)
10:36.49*** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net)
10:48.08*** join/#qi-hardware Textmode_ (~boneidle@adsl-syd-4-20.ozonline.com.au)
11:18.36*** join/#qi-hardware GNUtoo-desktop (~GNUtoo@host137-129-dynamic.45-79-r.retail.telecomitalia.it)
11:28.38*** join/#qi-hardware losinggeneration (~quassel@75-170-158-9.desm.qwest.net)
11:28.38*** join/#qi-hardware wpwrak (~werner@234-171-231-201.fibertel.com.ar)
11:35.04*** join/#qi-hardware Aylax (~Aylax@90.84.146.235)
11:38.33*** join/#qi-hardware Textmode_ (~boneidle@adsl-syd-4-20.ozonline.com.au)
12:11.36*** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net)
12:22.09*** join/#qi-hardware amirhb (bc9e9646@gateway/web/freenode/ip.188.158.150.70)
12:45.02*** join/#qi-hardware jekhor (~jek@46.53.195.29)
12:47.02qi-bot[commit] Adam Wang: fixed LP38511TJ-ADJ's GND to power input (master) http://qi-hw.com/p/kicad-libs/f36ddbf
12:54.55*** join/#qi-hardware jekhor (~jek@46.53.195.29)
13:01.05qi-bot[commit] Adam Wang: changed JS28F256J3F105's BYTE as Input (master) http://qi-hw.com/p/kicad-libs/261b470
13:04.39*** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com)
13:09.09qi-bot[commit] Adam Wang: changed MIC2550AYTS's VTRM to Power input (master) http://qi-hw.com/p/kicad-libs/2c9b9b4
13:14.39qi-bot[commit] Adam Wang: changed testpin to Passive (master) http://qi-hw.com/p/kicad-libs/966affe
13:22.43qi-bot[commit] Adam Wang: changed MT46V32M16P's VREF to input. (master) http://qi-hw.com/p/kicad-libs/9cd6b11
13:24.26*** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net)
13:28.19*** join/#qi-hardware Ayla (~paul@171.215.73.86.rev.sfr.net)
14:23.26*** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net)
14:24.32LunaVoraxHello everyone!
14:24.56wolfspraulhi :-)
14:25.02wolfspraulI'm almost calling it a day though...
15:24.14*** join/#qi-hardware Textmode_ (~boneidle@adsl-syd-4-20.ozonline.com.au)
15:28.32*** join/#qi-hardware emeb (~ericb@ip72-223-81-94.ph.ph.cox.net)
15:57.02*** join/#qi-hardware Textmode_ (~boneidle@adsl-syd-4-20.ozonline.com.au)
16:47.39*** join/#qi-hardware orson_zhai (~orson@111.193.0.197)
16:49.46*** part/#qi-hardware orson_zhai (~orson@111.193.0.197)
17:20.27*** join/#qi-hardware qwebirc31750 (4766dbad@gateway/web/freenode/ip.71.102.219.173)
17:22.25rjeffriesreading backlog. someone asked if I pimp qi-hardware in Raspberry Pi channel. A: NO. I was not promoting Raspberry Pi here, merely mentioning the release of board schematics (a Good Thing, IMO).
17:24.29rjeffriesNot sure I understand the latent hostimity to a $35 computer that will run Linux. While not perfectly open, they have released datasheet on the SoC and now we see schematics. As best I can tell, they are not forcing people to purchase the board.
17:25.49rjeffriesWhy not let 1,000 flowers bloom? Raspberry Pi may well fail, if so, then it failed. It is not a threat to Ben Nanonote, rather it has very different target market.
17:27.51rjeffriesBen NN has been an interesting (ongoing experiment). I am not sure Raspberry Pi can not achive a similar level of open-ness as Ben NN. Both have published SoC datasheets.
17:29.42rjeffriesThe life forces of qi hardware have already shifted to Milkymist, which has promise, although it will never be a $35 system. Will Milkylist someday be converted to an ASIC? It could happen.
17:30.33rjeffriess/hostimity/hostility/
18:17.07DocScrutinizerwhat damn latent hostility?
18:22.50DocScrutinizerwpwrak: (precharge) hah, well you want some proper current limiters in a number of places
18:32.29DocScrutinizerwpwrak: and I don't think you could place "the capacitor to the right side of switch" here
18:33.12DocScrutinizeranyway we had sth similar with Vsys on GTA02, no? ;-D
18:38.44DocScrutinizer(current limiter) a LDO with /ENA input is probably the better alternative to a switch with current limiter
18:39.09DocScrutinizerthis way you got a decent decoupling from system VDD by design
18:39.42DocScrutinizerand a LDO probably is even cheaper than a switch with current limiter
18:40.44DocScrutinizerof course this requires some power rail providing Uout + Udrop_LDO
18:42.24DocScrutinizerrunning a commerical device without any on-board power stabilization is ... a bit unusual. As are good stabilized 5V wallwart PSU
18:52.52*** join/#qi-hardware Ayla (~paul@186.189.26.93.rev.sfr.net)
19:25.14*** join/#qi-hardware GNUtoo (~gnutoo@host137-129-dynamic.45-79-r.retail.telecomitalia.it)
20:05.08*** join/#qi-hardware Martix (~martix@ip-89-176-31-78.net.upcbroadband.cz)
20:07.52wpwrakDocScrutinizer: in GTA02, we solved the Vsys problem just by placing a cap on the other side of the switch :)
20:09.51wpwrakan LDO may be a bit inefficient. but yes, it's a possiblity, too.
20:10.37wpwrakjust the absence of inrush current limiting is generally a bad idea, as we keep seeing :)
20:10.55*** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net)
20:11.01*** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul)
20:15.20DocScrutinizeryup
20:15.53DocScrutinizerunless you have no separate power domains and a proper power-up sequence
20:16.43DocScrutinizerone of the main reasons for power-up sequences is to avoid such effects
20:18.12DocScrutinizerbasically you can take a boader approach than "limiting inrush": always consider both ends of the rope
20:57.29wpwrakDocScrutinizer: power-up sequences don't help in this case - it's all hot-plugged
20:58.35wpwrakor at least can be hot-plugged. same worst case :)
21:49.25DocScrutinizersure
21:56.51*** join/#qi-hardware wej (~j@95.211.10.3)
22:34.29*** join/#qi-hardware xwalk (~crosswalk@d47-69-35-236.try.wideopenwest.com)
23:00.34*** join/#qi-hardware xwalk (~crosswalk@d47-69-35-236.try.wideopenwest.com)
23:10.23*** join/#qi-hardware Jay7 (jay@2.92.189.210)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.