¤Ä¤Ã¤Æ¤â¡¢Èó¸ø³«¤Î¤òÊ̤ˤĤ±¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¡£
Copyright 1999- Jun Makino
2011/11 2011/10 2011/09 2011/08 2011/07 2011/06 2011/05 2011/04 2011/03 2011/02 2011/01ÅöÌ̤ÎͽÄê
[ 26.168] (II) config/udev: Adding input device FSPPS/2 Sentelic FingerSensingPad (/dev/input/event1) [ 26.168] (**) FSPPS/2 Sentelic FingerSensingPad: Applying InputClass "evdev pointer catchall" [ 26.168] (II) Using input driver 'evdev' for 'FSPPS/2 Sentelic FingerSensingPad' [ 26.168] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so [ 26.168] (**) FSPPS/2 Sentelic FingerSensingPad: always reports core events [ 26.168] (**) FSPPS/2 Sentelic FingerSensingPad: Device: "/dev/input/event1" [ 26.176] (--) FSPPS/2 Sentelic FingerSensingPad: Found 11 mouse buttons [ 26.176] (--) FSPPS/2 Sentelic FingerSensingPad: Found scroll wheel(s) [ 26.176] (--) FSPPS/2 Sentelic FingerSensingPad: Found relative axes [ 26.176] (--) FSPPS/2 Sentelic FingerSensingPad: Found x and y relative axes [ 26.176] (II) FSPPS/2 Sentelic FingerSensingPad: Configuring as mouse [ 26.176] (II) FSPPS/2 Sentelic FingerSensingPad: Adding scrollwheel support [ 26.176] (**) FSPPS/2 Sentelic FingerSensingPad: YAxisMapping: buttons 4 and 5 [ 26.176] (**) FSPPS/2 Sentelic FingerSensingPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 26.176] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input1/event1" [ 26.176] (II) XINPUT: Adding extended input device "FSPPS/2 Sentelic FingerSensingPad" (type: MOUSE) [ 26.176] (II) FSPPS/2 Sentelic FingerSensingPad: initialized for relative axes. [ 26.176] (**) FSPPS/2 Sentelic FingerSensingPad: (accel) keeping acceleration scheme 1 [ 26.176] (**) FSPPS/2 Sentelic FingerSensingPad: (accel) acceleration profile 0 [ 26.177] (**) FSPPS/2 Sentelic FingerSensingPad: (accel) acceleration factor: 2.000 [ 26.177] (**) FSPPS/2 Sentelic FingerSensingPad: (accel) acceleration threshold: 4 [ 26.177] (II) config/udev: Adding input device FSPPS/2 Sentelic FingerSensingPad (/dev/input/mouse0) [ 26.177] (II) No input driver/identifier specified (ignoring)
01610067ms Absolute packet: 58, b3, 46, 09 01610079ms Absolute packet: 58, b2, 4a, 0c 01610091ms Absolute packet: 58, b2, 4d, 07 01610103ms Absolute packet: 58, b1, 51, 09 01610115ms Absolute packet: 58, b1, 54, 02 01610127ms Absolute packet: 58, b0, 58, 08 01610139ms Absolute packet: 58, af, 5b, 0d 01610151ms Absolute packet: 58, af, 5e, 06 01610164ms Absolute packet: 58, ae, 62, 0d 01610176ms Absolute packet: 58, ae, 66, 09 01610188ms Absolute packet: 58, ae, 69, 07
01689369ms Absolute packet: 7c, 8a, 58, 0d 01689376ms Absolute packet: 78, d8, 8f, 09 01689381ms Absolute packet: 7c, 8a, 58, 01 01689388ms Absolute packet: 78, d8, 8f, 0a 01689393ms Absolute packet: 7c, 89, 58, 05 01689400ms Absolute packet: 78, d8, 8f, 07 01689405ms Absolute packet: 7c, 88, 58, 0d 01689413ms Absolute packet: 78, d8, 90, 00 01689417ms Absolute packet: 7c, 88, 58, 06
ÇÛʬ Í×µá µþ¤ÎÀ°È÷¡¦±¿ÍÑ 150 161 ¥·¥¹¥Æ¥à³«È¯ 45 45 ±¿ÍÑÅù·ÐÈñ 97 109 ÍøÍÑÂ¥¿Ê 9 9 HPCI¤ÎÀ°È÷±¿ÍÑ 19 15 HPCI¹âÅÙ²½ ? 9 Àïά¥×¥í¥°¥é¥à 31 31
Back to GK112, and more importantly, GK102, or lack thereof. It looks like Nvidia could not pull off GK102, and that part was canceled. The important and difficult variant, GK112 is now about a year after GK102 should have come out before it was canceled. This explains why the smaller GK10x chips launch first, but also indicates exactly how screwed up Kepler is. Launching the small chips first will bring another host of problems, but we have covered that in previous articles.
The culprit is once again the interconnect, something even Jen-Hsun backhandedly admitted last year. Sources tell SemiAccurate that the same interconnect issues are casting doubt on the viability of Denver/T50/Tegra 6 (Note: This was Tegra 5 until the recent slips and roadmap readjustments) and the roadmaps show Kepler in GK1x2 guise is currently suffering a lot too, one of two variants has already failed. The main effect here is runaway power use, clock drops, and the attendant downward performance spiral. Then again, Nvidia wisely delayed Kepler a year to fix that, but as we have repeatedly stated, the architecture is fundamentally wrong, and that is not really fixable. We will see what the company is able to do when GK112 comes out, if it does.
One last thing to think about is performance. Nvidia was claiming ~2.5x the DP performance of Fermi for Kepler. According to 4Gamers, that is now down to 1.5-2x. This once again points to yield and/or performance per watt issues with the chip, both of which are very possible. Then again, Fermi was delivered with <50% of the promised performance per watt, so a mere, to be charitable, 20% backpedaling on Kepler can be considered great progress, right?
ÆüËÜ¡¡¡¡¡¡¡¡¡¡£±£°¡¦£µ£³±ß¡¿£Ë£×£È ¥ª¥¯¥é¥Û¥Þ½£¡¡£´¡¦£µ£µ±ß¡¿£Ë£×£È ¥ï¥·¥ó¥È¥ó½£¡¡£´¡¦£¶£µ±ß¡¿£Ë£×£È ¥ª¥ì¥´¥ó½£¡¡¡¡£´¡¦£·£¶±ß¡¿£Ë£×£È ¥¢¥¤¥ª¥ï½£¡¡¡¡£´¡¦£¸£±±ß¡¿£Ë£×£È
I-131 3.16E-11uCi/mL I-132 6.22E-11uCi/mL Cs-134 1.56E-11uCi/mL Cs-137 1.56E-11uCi/mL Sr-89 1.65E-05uCi Sr-Total 8.03E-06uCi Cs-136 2.90E-12uCi/mL Te-132 6.22E-11uCi/mL Ce-144 0uCi/mL Zr-95 0uCi/mL Sr-90 1.88E-06uCi Sb-127 0uCi/mL Te-129m 7.82E-12uCi/mL Nb-95 1.12E-13uCi/mL Ba-140 4.65E-13uCi/mL Np-239 0uCi/mL Sr-89gamma 0uCi/mL Xe-133 0uCi/mL Ag-110m 5.64E-14uCi/mL
°ÞÅÙ¡¢·ÐÅÙ¡¢»þ¹ï: 37.35¡¢140.32¡¢3/21 4:54:57 PM Ag-110m 1.65E-05 uCi/mL Am-241 8.19E-07 uCi/mL¤È¸«¤¨¤ë¤ó¤À¤±¤É¤¤¤¯¤é¤Ê¤ó¤Ç¤âÂ礲᤮¤Ê¤¤¤³¤ì¡©
°ÞÅÙ ·ÐÅÙ »þ¹ï: 35.67 139.74 3/18/2011 2:05:28 PM Sr-90 1.88E-06uCi Sr-Total 8.03E-06uCi Sr-89 1.65E-05uCi¤¬¥Ç¡¼¥¿