| 01:37.36 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d35:0:2cff:617d:d469:7d7a) |
| 01:46.51 | *** join/#qi-hardware uwe_ (~uwe_@ipservice-092-217-107-168.092.217.pools.vodafone-ip.de) |
| 02:08.42 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 02:15.33 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 02:27.36 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 03:01.23 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 03:33.06 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.53) |
| 03:41.25 | *** join/#qi-hardware archang (~archang@111.198.29.53) |
| 04:10.02 | *** join/#qi-hardware fengling (~fengling@2002:6fc6:1d35:0:2cff:617d:d469:7d7a) |
| 06:24.44 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 06:26.24 | eintopf | good morning |
| 06:26.40 | eintopf | everyone is hacking - fine |
| 06:58.54 | *** join/#qi-hardware fmeerkoetter (~fmee@pd95c658f.dip0.t-ipconnect.de) |
| 07:10.45 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 07:18.39 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 07:55.42 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 08:35.31 | *** join/#qi-hardware archang (~archang@111.198.29.53) |
| 08:38.29 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 08:50.34 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 09:01.21 | *** join/#qi-hardware wolfspraul (~wolfsprau@xd9bad564.dyn.telefonica.de) |
| 09:28.47 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 09:47.53 | rjeffries_ | so it seems like, (not quite sure how...) a bot somehow sends me an alert if I am mentioned by name on this channel? |
| 09:56.37 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 10:14.36 | rjeffries_ | my previous statement was posted in wrong (this) irc channel sorry. |
| 10:28.44 | rjeffries_ | this is a decent design as attractive price (when it ships) https://www.cnx-software.com/2015/04/21/udoo-neo-combines-arduino-raspberry-pi-wi-fi-bluetooth-and-sensors-into-a-single-49-board-crowdfunding/ |
| 10:37.06 | whitequark | (if) |
| 10:37.14 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 10:57.48 | roh | nasty connectors |
| 10:58.37 | roh | and i do not believe the price with a imx6 (all other boards are more expensive.. those cores cost some euros) |
| 10:59.23 | wpwrak | maybe Mark Tuson does the sourcing for them. then the price is no problem ;-) |
| 11:27.20 | rjeffries_ | one thing is absolute total 100 percent guarantee in #qi-hardware <smile> |
| 11:32.15 | rjeffries_ | no matter what, commercial small, cheap, relatively open computers of any flavor are assumed dead on arrival |
| 11:33.04 | whitequark | pick two |
| 12:03.00 | wpwrak | that too :) but it's unfortunately rather common for projects to underestimate what things cost |
| 12:04.04 | whitequark | also the thing where prototyping and mass production take completely disjoint skill sets |
| 12:04.17 | whitequark | the former is fairly well covered by makerspaces and such |
| 12:04.36 | whitequark | the latter is thoroughly lacking |
| 12:30.35 | valhalla | didn't the udoo already release a board? |
| 12:30.58 | valhalla | I expect that the second one is more likely to be successfull, if the first one was |
| 12:33.05 | valhalla | http://www.udoo.org/ ----> it seems that they did |
| 13:04.57 | *** join/#qi-hardware jwhitmore (~jwhitmore@88.151.80.134) |
| 13:09.23 | DocScrutinizer05 | http://maemo.cloud-7.de/share-service/20150420_002.jpg *ANY* hints how to find out about the properties of those chips and particularly what "TN0" means are extremely appreciated |
| 13:10.34 | DocScrutinizer05 | also pointers to companies who would to chip electrical QA testing on order, for a few hundred or maybe 1000 chips, highly appreciated |
| 13:11.13 | DocScrutinizer05 | thanks in advance |
| 13:13.27 | DocScrutinizer05 | http://maemo.cloud-7.de/share-service/20150421_002.jpg |
| 13:14.03 | DocScrutinizer05 | http://maemo.cloud-7.de/share-service/20150421_004.jpg |
| 13:14.17 | DocScrutinizer05 | http://maemo.cloud-7.de/share-service/20150421_008.jpg |
| 13:16.07 | DocScrutinizer05 | I's *supposed* to be (and sort of verified to be) a 8Gb-LPDDR/4Gb-OneNAND PoP chip for OMAP3 |
| 13:17.10 | DocScrutinizer05 | so the question is "what means -A506" and particularly "what means TN0" (sometimes quoted as "TNO") |
| 13:18.00 | DocScrutinizer05 | and generally "would it be possible to ask $somebody about more details about this particular chip/serialnumber" |
| 13:19.07 | whitequark | ask the people who sell it? |
| 13:28.05 | DocScrutinizer05 | did |
| 13:28.09 | DocScrutinizer05 | no dice |
| 13:29.52 | DocScrutinizer05 | brokers, have no idea really about what they actually are pushing through |
| 13:30.35 | DocScrutinizer05 | we asked for meaning of "TNO" and about "datasheets, pleeeease". No luck |
| 13:31.22 | DocScrutinizer05 | the answer is basically "we have a chip with this label and this footprint for you. Take it or leave it" |
| 13:37.17 | DocScrutinizer05 | I wonder if Samsung (and who there, they're a huge set of unlinked companies) would know and be willing to tell us some more about that particular chip/waver |
| 13:39.12 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 13:39.33 | *** join/#qi-hardware luke-jr_ (~luke-jr@unaffiliated/luke-jr) |
| 13:41.59 | whitequark | try asking on reddit.com/r/askengineers |
| 13:42.12 | whitequark | people from many big companies lurk there and samsung is enormous |
| 13:46.01 | DocScrutinizer05 | thanks! :-) |
| 13:47.39 | whitequark | /r/ECE also worth a try (those intersect but not much) |
| 13:50.10 | whitequark | the others are too novice oriented |
| 14:11.58 | DocScrutinizer05 | if only it wasn't reddit ;-) |
| 14:12.19 | DocScrutinizer05 | dos1: did you have an account there? |
| 14:36.04 | whitequark | DocScrutinizer05: you don't even need to provide *email* to register |
| 14:36.05 | whitequark | what is the issue |
| 15:25.47 | DocScrutinizer05 | whitequark: oh wow, didn't realize |
| 15:27.29 | *** join/#qi-hardware pcercuei (~paul@p4FDE6277.dip0.t-ipconnect.de) |
| 15:38.41 | whitequark | reddit hasn't sent me a single email ever |
| 15:38.50 | whitequark | actually annoying because I want it to notify me of replies |
| 15:57.36 | *** join/#qi-hardware wolfspraul (~wolfsprau@xd9bad564.dyn.telefonica.de) |
| 16:12.35 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 17:46.47 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::2) |
| 19:18.28 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 19:25.05 | *** join/#qi-hardware FDCX_ (~fdcx@86.121.175.251) |
| 20:27.44 | *** join/#qi-hardware arhuaco (~arhuaco__@186.80.243.165) |
| 20:44.19 | *** join/#qi-hardware rjeffries_ (~rjeffries@97-86-138-47.dhcp.stls.mo.charter.com) |
| 21:10.54 | *** join/#qi-hardware dos1 (~dos1@unaffiliated/dos1) |
| 21:27.07 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 22:06.00 | *** join/#qi-hardware rjeffries_ (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 22:09.02 | *** join/#qi-hardware Haswell (~broaderba@unaffiliated/haswell) |
