00:59.45 | *** join/#neo900 dos1 (~dos@unaffiliated/dos1) |
00:59.59 | DocScrutinizer05 | moin dos1 |
01:00.22 | DocScrutinizer05 | sleepless in $??? |
01:01.06 | DocScrutinizer05 | frowns at https://s3.amazonaws.com/LogicPDDMX/file_20130804_180851_1015574A_OMAP36x_MDP_Brief_XiHyf.pdf?AWSAccessKeyId=AKIAIZHS7222VBZA4LJQ&Expires=1384995709&response-content-disposition=attachment%3B%20filename%3D1015574A_OMAP36x_MDP_Brief.pdf&response-content-type=application/pdf&Signature=GiU6h2Prt6nv6hRCNfH9pu5Oq3o%3D |
01:01.40 | dos1 | nah, actually going to sleep soon |
01:02.17 | DocScrutinizer05 | + 1 GB(!!!) low-power DDR SDRAM PoPmemory / discrete 512 MB NANDflash memory |
01:02.19 | dos1 | just opened the window to refresh the air and woke up the laptop to check few things before going to bed ;) |
01:02.40 | DocScrutinizer05 | there's hope |
01:02.56 | dos1 | link doesn't work (AccessDenied - Request has expired), but - wow! |
01:03.12 | DocScrutinizer05 | if only thhose TI suckers would disclose which PoP chip they used in their Zoom2 |
01:03.57 | DocScrutinizer05 | dman |
01:04.03 | DocScrutinizer05 | (expired) |
01:05.52 | DocScrutinizer05 | http://wstaw.org/m/2013/11/21/plasma-desktopjw3743.png |
01:10.36 | DocScrutinizer05 | maybe the answer hides in there somewhere: https://gforge.ti.com/gf/project/omapzoom/frs/?action=index |
01:11.22 | DocScrutinizer05 | also a nice read: http://en.wikipedia.org/wiki/OMAP |
01:16.21 | dos1 | http://processors.wiki.ti.com/index.php/OMAP35x_To_AM37x_Software_Migration_Guide |
01:17.11 | dos1 | maybe interesting for kernel development? |
01:17.24 | DocScrutinizer05 | definitely |
01:17.37 | DocScrutinizer05 | #maemo-ssu |
01:18.19 | mashina_ | what if someone comes up with a kernel 3.x out of left field? do we build temples to our new god? |
01:20.39 | dos1 | I can't find any generic information about AM/DM37x family like that OMAP wiki article |
01:21.21 | dos1 | it appears only in references |
01:21.51 | dos1 | how does DM relate to OMAP? |
01:23.43 | dos1 | N900 uses OMAP3430 - and I found that 34xx and 36xx are meant for wireless usage, while 35xx is available in low volumes and is meant for devices like beagleboard |
01:24.01 | dos1 | and that migration guide is from 35xx to am/dm37xx |
01:24.28 | dos1 | I wonder how all of them relate to each other |
01:27.55 | dos1 | OMAP3630 on that Zoom is same as in N9/N950 |
01:29.22 | DocScrutinizer05 | yep |
01:30.25 | DocScrutinizer05 | dos1: basically DM == OMAP for mere mortals |
01:31.17 | dos1 | so why it's named differently? |
01:31.23 | DocScrutinizer05 | only TI knows |
01:31.38 | dos1 | that 34xx/36xx vs. 35xx/37xx differentation is bugging me |
01:31.51 | DocScrutinizer05 | yeah, it's idiotic |
01:32.14 | dos1 | "Please keep in mind that the Zoom platforms use the OMAP34xx and not the OMAP35xx as found on various other boards like the Beagle Board or Mistral EVM. The devices themselves are similar (i.e. CortexA8, C64x+ DSP, and SGX Graphics) however the OMAP34xx is targeted at wireless customers, so you may find limited support for the OMAP34xx unless you are working on a wireless phone design. " |
01:32.44 | DocScrutinizer05 | *cough* |
01:33.38 | DocScrutinizer05 | particularly funny when you learn that TI failed / forgot to bother about RoHS for their Zoom2 modem module |
01:33.50 | DocScrutinizer05 | so Zomm2 is in fact NO wireless device |
01:34.49 | DocScrutinizer05 | failwale |
01:34.49 | dos1 | well, the first concern that came into my uneducated mind was power consumption |
01:35.00 | DocScrutinizer05 | nope |
01:35.18 | DocScrutinizer05 | it's merely about supply chain channels and support |
01:35.32 | dos1 | ok then :) |
01:35.38 | DocScrutinizer05 | no mere mortal can bux the 4/6 |
01:35.43 | DocScrutinizer05 | buy |
01:36.10 | dos1 | no other notable differences? |
01:36.14 | DocScrutinizer05 | and you can't find datasheets for that stuff either |
01:36.18 | DocScrutinizer05 | nope |
01:36.27 | dos1 | funny |
01:36.32 | DocScrutinizer05 | well, they are quite differently binned at fab |
01:36.36 | DocScrutinizer05 | to order |
01:37.27 | DocScrutinizer05 | that's why Nokia is right per definitionem when they say stuff like "do not lock to 600MHz! Do not OC! Do not use SR!" |
01:38.01 | DocScrutinizer05 | after all they know what they ordered and got delivered, from TI |
01:38.37 | dos1 | hmm |
01:38.38 | DocScrutinizer05 | ~omap-oc |
01:38.38 | infobot | somebody said omap-oc was 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 |
01:38.50 | DocScrutinizer05 | applies only to the 5/7 |
01:38.57 | DocScrutinizer05 | not to the 4/6 |
01:39.03 | dos1 | so all seen 1GB RAM occurences were OMAP36xx? |
01:39.10 | DocScrutinizer05 | 4/6 may be same, worse, or even better |
01:39.23 | DocScrutinizer05 | that's unrelated, but yes |
01:40.11 | DocScrutinizer05 | it's just "no mere mortal can buy those chips" again |
01:40.29 | DocScrutinizer05 | or maybe not |
01:40.38 | DocScrutinizer05 | for N9 definitely the case |
01:40.55 | dos1 | unrelated, as in there's no problem with using dm37xx instead if some obtainable pop is identified? |
01:41.19 | DocScrutinizer05 | there IS NO such chip like 110J1H0K |
01:41.35 | DocScrutinizer05 | exactly |
01:41.56 | DocScrutinizer05 | any PoP working on OMAP3630 shall also work on DM3730 |
01:42.49 | dos1 | ok, it's all clear to me now :) |
01:42.53 | DocScrutinizer05 | :-D |
01:43.13 | DocScrutinizer05 | only thing still unclear: which damn PoP are they using in Zoom2? |
01:43.55 | DocScrutinizer05 | I'm not inclined to *buy* one just to find out what's written on the PoP chip |
01:44.30 | DocScrutinizer05 | I asked oin #linux-omap |
01:44.34 | DocScrutinizer05 | in* |
01:45.08 | DocScrutinizer05 | maybe somebody there has a zoom2 with 3630 and 1GB of RAM, and is willing to read that printing and forward it to me |
03:32.17 | *** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
03:39.27 | *** join/#neo900 Funklord (~cow@84-55-99-121.customers.ownit.se) |
04:55.09 | *** join/#neo900 Herbstb3rt (~Herbstber@drms-590c5e43.pool.mediaWays.net) |
09:03.29 | *** join/#neo900 zammy (~sammy@ppp-24-86.98-62.inwind.it) |
09:34.43 | *** join/#neo900 kolp (~quassel@212.255.236.254) |
09:48.59 | *** join/#neo900 Neros (~quassel@2001:660:2402:14:a11:96ff:fe78:3144) |
10:01.30 | *** join/#neo900 Neros (~quassel@2001:660:2402:14:a11:96ff:fe78:3144) |
10:07.03 | *** join/#neo900 dos1 (~dos@unaffiliated/dos1) |
11:14.44 | *** join/#neo900 Neros (~quassel@2001:660:2402:14:a11:96ff:fe78:3144) |
11:32.49 | *** join/#neo900 stevenm (~stevenm@stevenm.keele.netcentral.co.uk) |
11:33.47 | *** join/#neo900 zammy (~sammy@ppp-24-86.98-62.inwind.it) |
11:42.55 | *** join/#neo900 Neros_ (~quassel@wifi-osiris-sec-181-175.u-strasbg.fr) |
11:47.33 | *** join/#neo900 kolp (~quassel@212.255.250.47) |
13:54.38 | *** join/#neo900 Neros (~quassel@24-55-190-109.dsl.ovh.fr) |
14:07.22 | *** join/#neo900 SAiF (73f9ca82@gateway/web/freenode/ip.115.249.202.130) |
14:59.17 | SAiF | No action |
15:33.12 | SAiF | what |
15:39.09 | *** join/#neo900 hbib (~wurmel@pD9E0E814.dip0.t-ipconnect.de) |
15:46.04 | *** join/#neo900 deafboy (deafboy@46.229.238.172) |
16:06.17 | SAiF | so |
16:13.30 | *** join/#neo900 deafboy (deafboy@cicolina.org) |
16:24.45 | *** join/#neo900 NIN101 (~NIN@p5DD28474.dip0.t-ipconnect.de) |
16:58.35 | SAiF | ever |
17:02.39 | sono | action!!lll |
17:02.52 | sono | note the l. not a 1 |
17:27.05 | SAiF | I wonder how |
17:27.14 | *** part/#neo900 SAiF (73f9ca82@gateway/web/freenode/ip.115.249.202.130) |
17:35.35 | DocScrutinizer05 | we're not entertainers, we work hard to get some hardware out to you, guys |
17:36.14 | DocScrutinizer05 | display connector still a problem |
17:37.48 | *** join/#neo900 dos1 (~dos@unaffiliated/dos1) |
17:37.49 | DocScrutinizer05 | of course again 50 suppliers claim "MOQ:100, available, capacity:500000/week" and when you ask for quotation, they answer "that component is EOL, obsolete, and hardly ever asked for. Hard to find and *very* expensive*" |
17:38.02 | DocScrutinizer05 | moin dos1 |
17:39.01 | dos1 | moin |
17:51.13 | *** join/#neo900 Neros (~quassel@24-55-190-109.dsl.ovh.fr) |
18:30.05 | DocScrutinizer05 | how about a link on progressbar-click? to https://shop.goldelico.com/campaign/9603.php |
18:30.45 | DocScrutinizer05 | otherwise users ahve little means to learn about our 6 pledges 1500+ |
18:30.48 | DocScrutinizer05 | :-D |
19:22.59 | *** join/#neo900 Mistah_Darcy (~MistahDar@71-9-57-207.dhcp.gvrb.ca.charter.com) |
19:58.58 | *** join/#neo900 zammy (~sammy@ppp-232-194.98-62.inwind.it) |
20:04.09 | DocScrutinizer05 | on the bright side, it seems there *IS* a 1GByte LPDDR PoP chip (though without NAND) |
20:23.45 | DocScrutinizer05 | excellent day: 9 donations, 2 love, 1 1.5k+ |
21:04.02 | *** join/#neo900 hbib (~wurmel@pD9E0DB6C.dip0.t-ipconnect.de) |
21:11.52 | *** join/#neo900 wentknweqt_ (~wentknweq@unaffiliated/notten) |
21:42.35 | DocScrutinizer05 | err 11 |
21:43.09 | DocScrutinizer05 | scratching the 40k |
21:43.40 | DocScrutinizer05 | which doesn't mean much since all that are preorders |
21:44.05 | DocScrutinizer05 | but 162 preorders are pretty nice |
21:44.20 | DocScrutinizer05 | only 38 more to go for our minimum |
22:02.01 | *** part/#neo900 hbib (~wurmel@pD9E0DB6C.dip0.t-ipconnect.de) |
22:24.40 | *** join/#neo900 mashina (calvin@unaffiliated/prizm) |
22:49.49 | *** join/#neo900 xes (~xes@unaffiliated/xes) |
23:34.22 | *** join/#neo900 Hakki (~hakki@ip212-226-155-81.adsl.kpnqwest.fi) |