IRC log for #qi-hardware on 20150303

00:22.33*** join/#qi-hardware fengling (~fengling@60.14.88.170)
01:37.41*** join/#qi-hardware infobot (ibot@rikers.org)
01:37.41*** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
01:37.41*** mode/#qi-hardware [+v infobot] by ChanServ
02:32.59*** join/#qi-hardware whitequark (whitequark@fehu.whitequark.org)
02:33.17*** join/#qi-hardware _whitelogger (whitelogge@fehu.whitequark.org)
02:33.30*** mode/#qi-hardware [+v _whitelogger] by ChanServ
03:22.28*** join/#qi-hardware infobot (ibot@rikers.org)
03:22.29*** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
03:22.29*** mode/#qi-hardware [+v infobot] by ChanServ
03:50.57*** join/#qi-hardware infobot_ (ibot@rikers.org)
03:50.57*** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
03:50.57*** mode/#qi-hardware [+v infobot_] by ChanServ
04:15.13*** join/#qi-hardware infobot (ibot@rikers.org)
04:15.14*** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
04:15.14*** mode/#qi-hardware [+v infobot] by ChanServ
04:17.22DocScrutinizer05((stop working after 4 years)) yes, when you overclock them
04:18.33DocScrutinizer05the chips have 100,000h at OP1 to 4, and only some15,000h at OP5. Going to OP5++ will *drastically* reduce chip lifetime
04:18.44DocScrutinizer05~omap-oc
04:18.44infoboti heard omap-oc is http://mg.pov.lt/maemo-irclog/%23maemo.2010-08-01.log.html#t2010-08-01T22:16:05  read that!, or and this http://mg.pov.lt/maemo-irclog/%23maemo.2011-03-11.log.html#t2011-03-11T03:04:11
04:25.25DocScrutinizer05also design flaws in thermal management can cause the chip to constantly operate beyond max temeprature rating, which also reduces lifespan extremely
04:26.27DocScrutinizer05and we're talking about 10^x here for factor of lifespan shortening
04:27.20DocScrutinizer05with x something maybe like (°C above linit) / 10
04:30.11DocScrutinizer05~wiki electromigration
04:36.01DocScrutinizer05feel free to work through the formulas in there, and correct my above guesstimation of 10^x
04:39.24DocScrutinizer05anyway when lifespan drops for 500MHz->600MHz by factor 5 from 100k to 22k hours. then it drops for 600->700 *at least* to 22kh/5 = 4.4kh, and for 700->800 to 4.4kh/5 = <1000 hours
04:40.02DocScrutinizer05and I expect the factor to increase rather than stay constant, like /5 /7 /10 ...
04:44.15DocScrutinizer05and yes, OMAP4 is flawed. At least that's what I heard when working for a customer who supported customers using those critters
04:45.02DocScrutinizer05there seem to be SiErr that are "WONT FIX in OMAP4. Fixed in OMAP5"
04:45.54DocScrutinizer05not related to lifespan though, but who knows what else is in there that I never heard about
04:47.55DocScrutinizer05(SiErr in tickets opened while testing on TI Blaze)
05:37.21*** join/#qi-hardware wolfspraul (~wolfsprau@x2f76bfe.dyn.telefonica.de)
07:33.37eintopfoh thanks
07:34.08eintopfi had this night the biggest stomach pains forever. that wasnt funny
07:40.02eintopfso i think neo900 is prepared for long time lifing
07:44.56wpwraknice quote from xkcd: "the self-driving car project we launched by accident [...]"
07:50.34eintopfhi wpwrak
07:59.50*** join/#qi-hardware porchao (~quassel@218.231.187.90.eo.eaccess.ne.jp)
08:30.56*** join/#qi-hardware AnxiousGarlic (~Spider@130.225.244.206)
08:31.20*** part/#qi-hardware AnxiousGarlic (~Spider@130.225.244.206)
09:03.05*** join/#qi-hardware pcercuei (~paul@p4FC46475.dip0.t-ipconnect.de)
09:30.56*** join/#qi-hardware pcercuei (~paul@p4FC46475.dip0.t-ipconnect.de)
09:37.20*** join/#qi-hardware pcercuei_ (~paul@137.71.226.54)
11:55.15*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
12:41.31*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
13:12.07*** join/#qi-hardware methril (~methril@200.49.35.42)
13:15.15*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
13:22.40*** join/#qi-hardware methril (~methril@200.49.35.42)
13:45.23*** join/#qi-hardware dandon_ (~dandon@88.151.75.214)
14:11.21*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
15:22.03*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
15:46.07*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
16:04.10*** join/#qi-hardware FrankBlues (~alex@c-24-2-97-70.hsd1.ut.comcast.net)
16:30.21*** join/#qi-hardware FrankBlues (~alex@c-24-2-97-70.hsd1.ut.comcast.net)
16:31.19*** join/#qi-hardware pcercuei (~paul@p4FC46475.dip0.t-ipconnect.de)
16:37.28*** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
16:49.15*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
17:00.34*** join/#qi-hardware pcercuei (~paul@137.71.226.54)
18:55.25*** join/#qi-hardware unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421)
19:11.33*** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::a)
20:05.38*** join/#qi-hardware FrankBlues (~alex@c-24-2-97-70.hsd1.ut.comcast.net)
20:47.55*** join/#qi-hardware idundidit (~idundidit@66-215-119-163.dhcp.atsc.ca.charter.com)
23:03.32*** join/#qi-hardware FDCX_ (~fdcx@188.26.174.120)

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