Performance Summary
*******************

Worst slack in design: 0.089

                                  Requested     Estimated     Requested     Estimated               Clock        Clock
Starting Clock                    Frequency     Frequency     Period        Period        Slack     Type         Group
------------------------------------------------------------------------------------------------------------------------------------
main_pll|CLKOP_inferred_clock     130.0 MHz     131.5 MHz     7.692         7.603         0.089     inferred     Inferred_clkgroup_0
System                            130.0 MHz     719.4 MHz     7.692         1.390         6.302     system       system_clkgroup
====================================================================================================================================

The Hardware

The Ups

First off it’s definitely speedier than the HTC Incredible and it should be!  It also seems to be faster than my netbook, a Dell Mini 9, and the display is certainly larger, clearer than the Mini 9′s.

The Xoom has 1G of memory, but part of that is lost to the display and other things, so the Linux Kernel ends up showing 742MB of RAM.

As to battery life I can’t make any reasonable comparisons WRT battery life against the phone since the Incredible has a bitty itty battery, and the Xoom has a pretty big cell inside of it.  1300 or 1450 mAh stock for the Incredible vs. 3250 mAh for the Xoom, however Seido has a monster 3500 mAh LiIon upgrade for the Incredible, but that requires a different back obviously.  I’ve yet to actually run the battery down to the point where it shuts off.  If I’m using it REALLY heavily then it’ll last a day and a half, maybe more, if it’s mostly sitting idle on my night stand or something it lasts a good week without a plugin.  You definitely seem to get the claimed 10 hours of active/non-standby battery time, unlike the HTC Incredible when it first came out where you were lucky to get 3-4 hrs on standby.

I still don’t yet have 4G, not that there is coverage in Montana at all anyway.  The inbuilt 32GB of storage has been sufficient so I haven’t had need to pop in an SD card yet, though that is supposedly functional now that the first round of software updates came out.

The integrated WiFi is 802.11 a/b/g/n – the 802.11a was great for me when I was in the apartment complex where the 2.4GHz spectrum was basically unusable due to so many APs.

You get a solid front camera rating in at 5MP and a solid rear camera rating in at 2MP — both are video capable, but I haven’t dug into the video capabilities very much.  I’m sure someone, somewhere, has.

It has a HDMI “D” connector, I think they call that microHDMI, I haven’t had a chance to use this yet either, but supposedly it is capable of 720p output.  No idea if it outputs sound or not (it SHOULD!)

And The Downs

*NO* ability to charge from USB on the Xoom.  I’m not even sure if it runs from USB power when it’s plugged in, but it certainly does not charge via USB.  The only charging option is a 12V 1.5A wall-wart (global 100-240V 50/60Hz) with an absolutely tiny diameter barrel connector.  I understand why they went this way, they upped to a 7.4V instead of 3.7V cell, but they could have built in a voltage booster so you could atleast run off USB in a pinch, or charge over a 24 hour period.  The other complaint I have about the charging arrangement is that the connector sticks out from the tablet pretty far when plugged in (see the picture, the USB connector there gives you a sense of size I hope) and is very likely to be broken off.

The touch screen seems to occasionally lose it’s marbles a bit, but I’m not sure if I should blame the touchscreen or the screen protector Verizon sells in their kit.  Locking and then restarting the screen with the power button on the back clears it up.  I’m hoping this is either the screen protector, or, a simple software fix as it is kind of irritating at times.

The “dock” is a useless piece of trash.  It’s almost impossible to get the stupid thing to line up so you can even use it, it only has audio output and charging capability (no USB nor HDMI pass-through).  Changing the “shoe” on the bottom of the Xoom to include some holes for alignment pins would fix this.

New Apps/Features

The new GMail app for Android 3.0 is SO much better than the old for the phones.  The layout it’s using though really requires the extra screen real-estate.

The new browser is faster, and the context bar(?) at the top where it shows your tabs, lets you touch to get the address bar, open new tab, close a tab, etc, is far more intuitive and easy to use than the old browser was.

One of the more interesting new apps I haven’t played much with yet is the Movie Studio app.  This lets you take video and pictures and actually edit together whole sequences right on the Xoom.  It’s actually fairly speedy, probably taking advantage of hardware acceleration to achieve that.

The CNN app that they demo-ed sort of sucks, the stack widget can’t or won’t display anything but Top Stories, the scrolling when you’re reading stories is ALWAYS along the left hand side of the device making reading anything very awkward with the majority of the screen taken up by whatever extra media is associated with the story.  There’s also no way to get to the home screen if you jump into the CNN App from the widget (the back button doesn’t always do it for some reason, sometimes it takes you back to the Android Home screen, sometimes it actually successfully puts you at the CNN App’s home)

The YouTube Stack Widget also sucks because, again, no control over what it’s displaying.

Older apps and widgets are still a bit flaky, despite Android 3.0 being backwards compatible, some apps do bad things that don’t show up until you’re running multi-core.  There also may be bugs in Dalvik, so we’ll see how this fleshes out in the months to come.

Command Line Goodness

And just a bit of command line output goodness so anyone whose curious can see exactly what the thing is running and what hardware/modules get active in this non-4G Xoom.

Full dmesg output

<6>[    0.000000] Initializing cgroup subsys cpu
<5>[    0.000000] Linux version 2.6.36.3-g2a65edc (android-build@apa28.mtv.corp.google.com) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Mon Feb 7 15:24:33 PST 2011
<4>[    0.000000] CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7f
<4>[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
<4>[    0.000000] Machine: stingray
<4>[    0.000000] Ignoring unrecognised tag 0x41000810
<6>[    0.000000] powerup reason=0x00000080
<4>[    0.000000] WiFi MAC Addr [4] = 0x<snip>
<4>[    0.000000]  40 fc 89 2f 5e 26
<6>[    0.000000] Found tegra_fbmem: 007d0000@1e018000
<6>[    0.000000] Reserved 1ff00000@00100000 for ram console
<6>[    0.000000] Tegra reserved memory:
<6>[    0.000000] LP0:                    1e7f1020 - 1e7f301f
<6>[    0.000000] Bootloader framebuffer: 1e018000 - 1e7e7fff
<6>[    0.000000] Framebuffer:            2e800000 - 2effffff
<6>[    0.000000] 2nd Framebuffer:         2f000000 - 2fffffff
<6>[    0.000000] Carveout:               30000000 - 3fffffff
<6>[    0.000000] HACK: Old framebuffer:  1e018000 - 1e7e7fff
<4>[    0.000000] Memory policy: ECC disabled, Data cache writealloc
<7>[    0.000000] On node 0 totalpages: 189952
<7>[    0.000000] free_area_init_node: node 0, pgdat c056b2a0, node_mem_map c063a000
<7>[    0.000000]   Normal zone: 1536 pages used for memmap
<7>[    0.000000]   Normal zone: 0 pages reserved
<7>[    0.000000]   Normal zone: 188416 pages, LIFO batch:31
<4>[    0.000000]   HighMem zone: 512 pages exceeds realsize 0
<6>[    0.000000] PERCPU: Embedded 8 pages/cpu @c0e42000 s8512 r8192 d16064 u65536
<6>[    0.000000] pcpu-alloc: s8512 r8192 d16064 u65536 alloc=16*4096
<6>[    0.000000] pcpu-alloc: [0] 0 [0] 1
<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 188416
<5>[    0.000000] Kernel command line: mem=1024M@0M tegra_fbmem=8192000@0x1e018000 video=tegrafb ramconsole=1M@511M console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc gpt gpt_sector=0x03b9dfff mot_prod=1 androidboot.serialno=<snip> hw_rev=p3 lp0_vec=8192@0x1e7f1020 androidboot.bootloader=1035 androidboot.baseband=N_02.0F.00R lcd_manfid=AUO mem_vid=0x303 mem_pid=0x5454
<6>[    0.000000] usb_serial_num=<snip>
<6>[    0.000000] hw_rev=0x83000000
<6>[    0.000000] lcd_manfid=AUO
<6>[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
<6>[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
<6>[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[    0.000000] Memory: 510MB 232MB = 742MB total
<5>[    0.000000] Memory: 736196k/736196k available, 312380k reserved, 0K highmem
<5>[    0.000000] Virtual kernel memory layout:
<5>[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
<5>[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
<5>[    0.000000]     DMA     : 0xff000000 - 0xffe00000   (  14 MB)
<5>[    0.000000]     vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)
<5>[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
<5>[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
<5>[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
<5>[    0.000000]       .init : 0xc0008000 - 0xc0034000   ( 176 kB)
<5>[    0.000000]       .text : 0xc0034000 - 0xc0501000   (4916 kB)
<5>[    0.000000]       .data : 0xc0528000 - 0xc056bda0   ( 272 kB)
<6>[    0.000000] Hierarchical RCU implementation.
<6>[    0.000000]     RCU dyntick-idle grace-period acceleration is enabled.
<6>[    0.000000]     RCU-based detection of stalled CPUs is disabled.
<6>[    0.000000]     Verbose stalled-CPUs detection is disabled.
<6>[    0.000000] NR_IRQS:448
<6>[   17.693756] Calibrating delay loop... 1992.29 BogoMIPS (lpj=9961472)
<6>[   17.963399] pid_max: default: 32768 minimum: 301
<4>[   17.964031] Mount-cache hash table entries: 512
<6>[   17.964942] Initializing cgroup subsys debug
<6>[   17.964959] Initializing cgroup subsys cpuacct
<6>[   17.964982] Initializing cgroup subsys freezer
<6>[   17.965080] CPU: Testing write buffer coherency: ok
<6>[   17.965377] Calibrating local timer... 249.86MHz, setting to 2.50MHz.
<4>[   18.063626] CPU1: Booted secondary processor
<6>[   18.343470] Brought up 2 CPUs
<6>[   18.343486] SMP: Total of 2 processors activated (3991.14 BogoMIPS).
<6>[   18.351416] regulator: core version 0.5
<6>[   18.351840] NET: Registered protocol family 16
<6>[   18.352853] host1x bus init
<6>[   18.353781] Tegra Revision: A03 prime SKU: 8 CPU Process: 0 Core Process: 0
<6>[   18.355988] stingray_init_emc: Elpida memory found
<6>[   18.360723] console [ttyFIQ0] enabled
<6>[   18.360927] Registered FIQ tty driver ee087d80
<6>[   18.360944] CPCAP: delaying cpcap_audio probe
<6>[   18.362474] ram_console: got buffer at 1ff00000, size 100000
<6>[   18.362636] ram_console: uncorrectable error in header
<6>[   18.362645] ram_console: no valid data in buffer (sig = 0xfff7ffd7)
<6>[   18.370687] console [ram-1] enabled
<6>[   18.372353] CPCAP: delaying cpcap_validity probe
<6>[   18.372443] CPCAP: delaying cpcap_led_driver probe
<6>[   18.372599] CPCAP: delaying cpcap_led_driver probe
<6>[   18.372686] CPCAP: delaying cpcap_3mm5 probe
<6>[   18.372843] CPCAP: delaying cpcap_whisper probe
<3>[   18.373560] hdmi: couldn't get regulator vcsi
<6>[   18.836057] initialize the ov5650 sensor
<6>[   18.836519] initialize the soc2030 sensor
<6>[   18.844593] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
<6>[   18.844953] tegra_arb_init: initialized
<4>[   18.845165] tegra_iovmm_register: added iovmm-gart
<4>[   18.857791] bio: create slab <bio-0> at 0
<7>[   18.858654] machine_constraints_voltage: override 'stingray_panel_reg' min_uV, 1 -> 5000000
<7>[   18.858819] machine_constraints_voltage: override 'stingray_panel_reg' max_uV, 2147483647 -> 5000000
<6>[   18.858910] regulator: stingray_panel_reg: 5000 mV
<7>[   18.859087] reg-fixed-voltage reg-fixed-voltage.0: stingray_panel_reg supplying 5000000uV
<5>[   18.860701] SCSI subsystem initialized
<6>[   18.861010] usbcore: registered new interface driver usbfs
<6>[   18.861267] usbcore: registered new interface driver hub
<6>[   18.861588] usbcore: registered new device driver usb
<6>[   18.864326] max8649 3-0060: Detected MAX8952 (ID: 0x201a)
<6>[   18.865534] regulator: max8649: 770 <--> 1100 mV at 1000 mV
<6>[   18.865672] max8649 3-0060: Max8649 regulator device is detected.
<6>[   18.867585] Bluetooth: Core ver 2.15
<6>[   18.867774] NET: Registered protocol family 31
<6>[   18.867933] Bluetooth: HCI device and connection manager initialized
<6>[   18.868024] Bluetooth: HCI socket layer initialized
<6>[   18.868444] Switching to clocksource timer_us
<6>[   18.869268] tegra-nvmap tegra-nvmap: created carveout iram (256KiB)
<6>[   18.869469] tegra-nvmap tegra-nvmap: created carveout generic-0 (262144KiB)
<6>[   18.871476] NET: Registered protocol family 2
<6>[   18.871750] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[   18.872563] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
<6>[   18.874284] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
<6>[   18.875165] TCP: Hash tables configured (established 131072 bind 65536)
<6>[   18.875322] TCP reno registered
<6>[   18.875411] UDP hash table entries: 512 (order: 2, 16384 bytes)
<6>[   18.875595] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
<6>[   18.875955] NET: Registered protocol family 1
<6>[   18.877034] Unpacking initramfs...
<6>[   18.888343] Freeing initrd memory: 140K
<6>[   18.888648] PMU: registered new PMU device of type 0
<6>[   18.888926] tegra_audio_probe
<6>[   18.889065] tegra_audio_probe: i2s_clk rate 24000000
<6>[   18.889747] setup_dma
<6>[   18.889960] tegra_audio_probe
<6>[   18.890094] tegra_audio_probe: i2s_clk rate 2000000
<6>[   18.891094] setup_dma
<6>[   18.891412] tegra_spdif_probe
<6>[   18.891839] spdif_set_sample_rate: spdif_clk rate 5644800
<6>[   18.892324] setup_dma
<6>[   18.893683] usbnet init
<6>[   18.916775] ashmem: initialized
<6>[   18.918317] fuse init (API version 7.15)
<6>[   18.919705] io scheduler noop registered (default)
<6>[   18.924073] tegra_grhost tegra_grhost: initialized
<6>[   18.924268] host1x: tegradc tegradc
<6>[   18.924793] tegradc tegradc.0: probed
<6>[   18.925581] tegradc tegradc.0: probed
<6>[   18.937303] host1x: tegradc tegradc
<6>[   18.937968] tegradc tegradc.1: probed
<6>[   18.938908] tegradc tegradc.1: probed
<6>[   18.939455] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>[   18.940553] tegra_uart.0: ttyHS0 at I/O 0x0 (irq = 68) is a unknown
<6>[   18.940807] Registered UART port ttyHS0
<6>[   18.940930] tegra_uart.2: ttyHS2 at I/O 0x0 (irq = 78) is a unknown
<6>[   18.941227] Registered UART port ttyHS2
<6>[   18.941350] tegra_uart.3: ttyHS3 at I/O 0x0 (irq = 122) is a unknown
<6>[   18.941674] Registered UART port ttyHS3
<6>[   18.941796] tegra_uart.4: ttyHS4 at I/O 0x0 (irq = 123) is a unknown
<6>[   18.942105] Registered UART port ttyHS4
<6>[   18.942270] Initialized tegra uart driver
<6>[   18.946234] loop: module loaded
<6>[   18.946370] Android kernel panic handler initialized (bind=crashdata)
<6>[   18.946459] AK8975 compass driver: init
<3>[   18.946673] akm8975 3-000c: unable to get regulator 3-000c
<6>[   18.947059] input: compass as /devices/virtual/input/input0
<6>[   18.947571] kxtf9 accelerometer driver
<3>[   18.947791] kxtf9 3-000f: unable to get regulator
<6>[   19.050024] input: accelerometer as /devices/virtual/input/input1
<6>[   19.050525] kxtf9 3-000f: kxtf9 probed
<6>[   19.050831] cap_prox_hw_init: HW init
<6>[   19.260414] cap_prox_probe: msg->status 0x20
<6>[   19.260865] cap_prox_probe: Request IRQ = 395
<6>[   19.261223] cap-prox 3-0012: cap-prox probed
<6>[   19.261869] input: max9635_als as /devices/virtual/input/input2
<6>[   19.263790] L3G4200D gyroscope driver
<3>[   19.263984] l3g4200d_probe:Enter
<3>[   19.264077] l3g4200d 2-0068: unable to get regulator
<6>[   19.264390] input: gyroscope as /devices/virtual/input/input3
<6>[   19.264683] l3g4200d_probe:Gyro probed
<7>[   19.265100] mdm6600_ctrl_init
<6>[   19.265227] mdm6600_ctrl mdm6600_ctrl: mdm_ctrl_probe
<6>[   19.267058] mdm6600_ctrl: modem status: undefined -> awake [power on]
<6>[   19.267429] BMP085 barometer driver
<3>[   19.268460] bmp085 0-0077: unable to get regulator
<6>[   19.268830] input: barometer as /devices/virtual/input/input4
<6>[   19.271716] ts27010 mux registered
<6>[   19.279302] regulator: sw2: 1000 <--> 1200 mV at 1200 mV
<6>[   19.281342] regulator: sw4: 1000 <--> 1200 mV at 1200 mV
<6>[   19.281797] regulator: sw5: 5050 mV
<6>[   19.282705] regulator: vcam: 2900 mV
<6>[   19.284728] regulator: vcsi: 1200 mV
<6>[   19.285599] regulator: vdac: 1800 mV
<6>[   19.287598] regulator: vdig: 1875 mV
<6>[   19.288026] regulator: vfuse: 1500 <--> 3150 mV
<6>[   19.289644] regulator: vhvio: 2775 mV
<6>[   19.291626] regulator: vsdio: 3000 mV
<6>[   19.292764] regulator: vpll: 1800 mV
<6>[   19.293192] regulator: vrf1: 2500 <--> 2775 mV
<6>[   19.293577] regulator: vrf2: 2775 mV
<6>[   19.294071] regulator: vrfref: 2500 <--> 2775 mV
<6>[   19.295587] regulator: vwlan1: 1800 <--> 1900 mV at 1800 mV
<6>[   19.297561] regulator: vwlan2: 3300 mV
<6>[   19.298074] regulator: vsim: 1800 <--> 2900 mV
<6>[   19.298513] regulator: vsimcard: 1800 <--> 2900 mV
<6>[   19.299052] regulator: vvib: 1300 <--> 3000 mV
<6>[   19.299513] regulator: vusb: 3300 mV
<6>[   19.301075] regulator: vaudio: 2775 mV normal standby
<6>[   19.302018] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0018
<6>[   19.314410] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0038
<6>[   19.326763] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0058
<6>[   19.339066] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0078
<6>[   19.351420] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0098
<6>[   19.363750] cpcap_uc cpcap_uc: Loading 4 word(s) at 0x00b8
<6>[   19.370129] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0120
<6>[   19.382427] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0140
<6>[   19.394787] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0160
<6>[   19.407087] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0180
<6>[   19.419449] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x01a0
<6>[   19.431744] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x01c0
<6>[   19.444106] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x01e0
<6>[   19.456433] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0200
<6>[   19.468799] cpcap_uc cpcap_uc: Loading 2 word(s) at 0x0220
<6>[   19.473616] cpcap_uc cpcap_uc: Loading 5 word(s) at 0x0224
<6>[   19.479994] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0231
<6>[   19.492294] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0251
<6>[   19.504651] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0271
<6>[   19.516952] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0291
<6>[   19.529312] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x02b1
<6>[   19.541609] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x02d1
<6>[   19.553967] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x02f1
<6>[   19.566266] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0311
<6>[   19.578630] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0331
<6>[   19.590925] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0351
<6>[   19.603285] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0371
<6>[   19.615585] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0391
<6>[   19.627942] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x03b1
<6>[   19.640241] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x03d1
<6>[   19.652603] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x03f1
<6>[   19.664900] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0411
<6>[   19.677261] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0431
<6>[   19.689539] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0451
<6>[   19.701761] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0471
<6>[   19.713999] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0491
<6>[   19.726328] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x04b1
<6>[   19.738583] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x04d1
<6>[   19.750894] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x04f1
<6>[   19.763163] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0511
<6>[   19.775430] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0531
<6>[   19.787759] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0551
<6>[   19.800030] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0571
<6>[   19.812358] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0591
<6>[   19.824627] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x05b1
<6>[   19.836955] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x05d1
<6>[   19.849236] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x05f1
<6>[   19.861552] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0611
<6>[   19.873790] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0631
<6>[   19.886116] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0651
<6>[   19.898388] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0671
<6>[   19.910716] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x0691
<6>[   19.922954] cpcap_uc cpcap_uc: Loading 16 word(s) at 0x06b1
<6>[   19.935284] cpcap_uc cpcap_uc: Loading 5 word(s) at 0x06d1
<6>[   19.946268] cpcap_uc cpcap_uc: Loaded HWCFG data: 0
<6>[   19.946507] cpcap_uc cpcap_uc: Started macro 4: 0
<6>[   19.959266] input: cpcap-key as /devices/virtual/input/input5
<6>[   19.959430] cpcap_key cpcap_key: CPCAP key device probed
<6>[   19.959653] cpcap spi1.0: Probing CPCAP device cpcap_audio
<6>[   19.961508] cpcap spi1.0: Probing CPCAP device cpcap_validity
<6>[   19.961916] cpcap_validity cpcap_validity: Started macro 14: 0
<6>[   19.962234] cpcap_validity cpcap_validity: Started macro 15: 0
<6>[   19.962328] cpcap spi1.0: Probing CPCAP device cpcap_led_driver
<6>[   19.962626] cpcap spi1.0: Probing CPCAP device cpcap_led_driver
<6>[   19.962846] cpcap spi1.0: Probing CPCAP device cpcap_3mm5
<3>[   19.963285] regulator_check_voltage: operation not allowed for vaudio
<6>[   19.964457] cpcap spi1.0: Headset key event: old=0, new=0
<6>[   19.964697] cpcap spi1.0: New headset state: 0
<6>[   19.964790] cpcap spi1.0: Probing CPCAP device cpcap_whisper
<6>[   19.965540] PPP generic driver version 2.4.2
<6>[   19.965893] PPP Deflate Compression module registered
<6>[   19.965982] PPP BSD Compression module registered
<6>[   19.966819] PPP MPPE Compression module registered
<6>[   19.966912] NET: Registered protocol family 24
<6>[   19.967819] usbcore: registered new interface driver asix
<6>[   19.967989] usbcore: registered new interface driver cdc_ether
<6>[   19.968302] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[   20.008697] tegra-ehci tegra-ehci.1: Tegra EHCI Host Controller
<6>[   20.008968] tegra-ehci tegra-ehci.1: new USB bus registered, assigned bus number 1
<6>[   20.038600] tegra-ehci tegra-ehci.1: irq 53, io mem 0xc5004000
<6>[   20.058582] tegra-ehci tegra-ehci.1: USB 2.0 started, EHCI 1.00
<6>[   20.058843] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[   20.058933] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[   20.059089] usb usb1: Product: Tegra EHCI Host Controller
<6>[   20.059177] usb usb1: Manufacturer: Linux 2.6.36.3-g2a65edc ehci_hcd
<6>[   20.059333] usb usb1: SerialNumber: tegra-ehci.1
<6>[   20.059968] hub 1-0:1.0: USB hub found
<6>[   20.060155] hub 1-0:1.0: 1 port detected
<6>[   20.063233] tegra-ehci tegra-ehci.2: Tegra EHCI Host Controller
<6>[   20.063358] tegra-ehci tegra-ehci.2: new USB bus registered, assigned bus number 2
<6>[   20.088604] tegra-ehci tegra-ehci.2: irq 129, io mem 0xc5008000
<6>[   20.108582] tegra-ehci tegra-ehci.2: USB 2.0 started, EHCI 1.00
<6>[   20.108765] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[   20.108925] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[   20.109014] usb usb2: Product: Tegra EHCI Host Controller
<6>[   20.109173] usb usb2: Manufacturer: Linux 2.6.36.3-g2a65edc ehci_hcd
<6>[   20.109260] usb usb2: SerialNumber: tegra-ehci.2
<6>[   20.109916] hub 2-0:1.0: USB hub found
<6>[   20.110024] hub 2-0:1.0: 1 port detected
<6>[   20.110653] usbcore: registered new interface driver cdc_acm
<6>[   20.110813] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[   20.110973] Initializing USB Mass Storage driver...
<6>[   20.111215] usbcore: registered new interface driver usb-storage
<6>[   20.111374] USB Mass Storage support registered.
<6>[   20.111680] usbcore: registered new interface driver usbserial
<6>[   20.111839] usbserial: USB Serial Driver core
<6>[   20.112043] USB Serial support registered for MDM 6600 modem usb-serial driver
<6>[   20.112314] usbcore: registered new interface driver mdm6600
<6>[   20.112562] USB Serial support registered for moto-flashmdm
<6>[   20.112800] usbcore: registered new interface driver moto-flashmdm
<6>[   20.112890] NVidia Tegra High-Speed USB SOC Device Controller driver (Apr 20, 2007)
<6>[   20.118359] android init
<6>[   20.118510] android_probe pdata: c0547da8
<6>[   20.118700] android_bind
<7>[   20.118858] android_bind_config
<4>[   20.118943] Gadget Android: controller 'fsl-tegra-udc' not recognized
<6>[   20.119275] android_usb gadget: android_usb ready
<6>[   20.119365] fsl-tegra-udc: bind to driver android_usb
<6>[   20.119528] f_adb init
<6>[   20.119683] android_register_function adb
<6>[   20.119768] f_mtp init
<6>[   20.119852] android_register_function mtp
<6>[   20.119936] f_rndis init
<6>[   20.120208] android_register_function rndis
<6>[   20.120299] rndis_function_bind_config MAC: <snip>
<4>[   20.120495] android_usb gadget: using random self ethernet address
<4>[   20.120590] android_usb gadget: using random host ethernet address
<6>[   20.121150] usb0: MAC <snip>
<6>[   20.121239] usb0: HOST MAC <snip>
<6>[   20.121481] mtp_bind_config
<6>[   20.123148] adb_bind_config
<6>[   20.124910] qtouch_ts_probe: xpos_msb 4 xpos_lsb 4 ypos_msb 4 ypos_lsb 0
<6>[   20.125003] qtouch_force_reset: Forcing HW reset
<6>[   20.409109] qtouch_process_info_block: Build version is 0x10
<6>[   20.409202] qtouch_process_info_block: Num obj: 18 addr: 7
<6>[   20.409360] qtouch_process_info_block: Reading addr: 7
<6>[   20.409970] qtouch_process_info_block: Object 37 @ 0x0076 (130) insts 1 rep_ids 0
<6>[   20.410129] qtouch_process_info_block: Reading addr: 13
<6>[   20.410715] qtouch_process_info_block: Object 44 @ 0x00f8 (1) insts 1 rep_ids 0
<6>[   20.410874] qtouch_process_info_block: Reading addr: 19
<6>[   20.411531] qtouch_process_info_block: Object 5 @ 0x00f9 (9) insts 1 rep_ids 0
<6>[   20.411621] qtouch_process_info_block: Reading addr: 25
<6>[   20.412277] qtouch_process_info_block: Object 6 @ 0x0102 (6) insts 1 rep_ids 1
<6>[   20.412364] qtouch_process_info_block: Reading addr: 31
<6>[   20.413023] qtouch_process_info_block: Object 38 @ 0x0108 (64) insts 1 rep_ids 0
<6>[   20.413111] qtouch_process_info_block: Reading addr: 37
<6>[   20.413769] qtouch_process_info_block: Object 7 @ 0x0148 (3) insts 1 rep_ids 0
<6>[   20.413857] qtouch_process_info_block: Reading addr: 43
<6>[   20.414514] qtouch_process_info_block: Object 8 @ 0x014b (10) insts 1 rep_ids 0
<6>[   20.414673] qtouch_process_info_block: Reading addr: 49
<6>[   20.415260] qtouch_process_info_block: Object 9 @ 0x0155 (34) insts 1 rep_ids 16
<6>[   20.415418] qtouch_process_info_block: Reading addr: 55
<6>[   20.416006] qtouch_process_info_block: Object 15 @ 0x0177 (11) insts 2 rep_ids 1
<6>[   20.416163] qtouch_process_info_block: Reading addr: 61
<6>[   20.416592] qtouch_process_info_block: Object 18 @ 0x018d (2) insts 1 rep_ids 0
<6>[   20.416750] qtouch_process_info_block: Reading addr: 67
<6>[   20.417179] qtouch_process_info_block: Object 22 @ 0x018f (17) insts 1 rep_ids 1
<6>[   20.417337] qtouch_process_info_block: Reading addr: 73
<6>[   20.417837] qtouch_process_info_block: Object 24 @ 0x01a0 (19) insts 1 rep_ids 4
<6>[   20.417927] qtouch_process_info_block: Reading addr: 79
<6>[   20.418427] qtouch_process_info_block: Object 25 @ 0x01b3 (14) insts 1 rep_ids 1
<6>[   20.418515] qtouch_process_info_block: Reading addr: 85
<6>[   20.419029] qtouch_process_info_block: Object 27 @ 0x01c1 (7) insts 1 rep_ids 1
<6>[   20.419117] qtouch_process_info_block: Reading addr: 91
<6>[   20.419618] qtouch_process_info_block: Object 28 @ 0x01c8 (6) insts 1 rep_ids 1
<6>[   20.419774] qtouch_process_info_block: Reading addr: 97
<6>[   20.420202] qtouch_process_info_block: Object 40 @ 0x01ce (5) insts 1 rep_ids 0
<6>[   20.420358] qtouch_process_info_block: Reading addr: 103
<6>[   20.420789] qtouch_process_info_block: Object 41 @ 0x01d3 (7) insts 1 rep_ids 0
<6>[   20.420947] qtouch_process_info_block: Reading addr: 109
<6>[   20.421377] qtouch_process_info_block: Object 43 @ 0x01da (6) insts 1 rep_ids 0
<6>[   20.421824] qtouch_process_info_block: qtouch-obp-ts found.
<6>[   20.421829]   family 0xa0, variant 0x0, ver 0x10, build 0xff
<6>[   20.421833]   matrix 33x42, 18 objects, info blk chksum 0x203301
<6>[   20.422149] qtouch_ts_probe: FW version is 0x10 Build 0xFF
<6>[   20.422305] qtouch_ts_probe: Chip type matched
<6>[   20.422390] qtouch_ts_probe: Reflash not needed
<6>[   20.422910] input: qtouch-touchscreen as /devices/virtual/input/input6
<6>[   20.423296] qtouch_ts_probe: request_irq [362] success.
<6>[   20.423493] do_cmd_proc_msg:EEPROM checksum matches
<6>[   20.423579] do_cmd_proc_msg: Reset done.
<6>[   20.423664] do_cmd_proc_msg: Self-calibration started.
<3>[   20.424091] gpiomatrix: set_irq_wake failed for input 136, irq 328
<3>[   20.424264] gpiomatrix: set_irq_wake failed for input 137, irq 329
<6>[   20.424423] GPIO Matrix Keypad Driver: Start keypad matrix for stingray-keypad in interrupt mode
<6>[   20.424607] GPIO Input Driver: Start gpio inputs for stingray-keypad in interrupt mode
<6>[   20.424934] input: stingray-keypad as /devices/virtual/input/input7
<6>[   20.425658] using input dev cpcap-key for key reset
<6>[   20.425759] using input dev stingray-keypad for key reset
<6>[   20.425953] using input dev cpcap-key for key reset
<6>[   20.426823] using rtc device, cpcap_rtc, for alarms
<6>[   20.426984] cpcap_rtc cpcap_rtc: rtc core: registered cpcap_rtc as rtc0
<6>[   20.427587] i2c /dev entries driver
<6>[   20.428557] Linux video capture interface: v2.00
<6>[   20.428597] usb 2-1: new high speed USB device using tegra-ehci and address 2
<6>[   20.429070] trpc_sema_init: registered misc dev 10:32
<6>[   20.429296] trpc_node_register: Adding 'local' to node list
<6>[   20.431268] trpc_node_register: Adding 'avp-remote' to node list
<6>[   20.431604] tegra_avp_probe: driver registered, kernel 30100000(f0c00000), msg area 2d9d0000/2d9d0110
<6>[   20.431898] tegra_camera: probe
<6>[   20.432257] ov5650 sensor driver loading
<6>[   20.432449] ov5650: probing sensor.
<6>[   20.432793] soc2030: probing sensor.
<6>[   20.433109] dw9714l sensor driver loading
<6>[   20.433296] dw9714l: probing sensor.
<6>[   20.434770] Driver for 1-wire Dallas network protocol.
<6>[   20.435138] Driver for Tegra SoC 1-wire controller
<6>[   20.436176] bq24617 bq24617: Using STAT and DETECT for detection.
<6>[   20.436973] device-mapper: uevent: version 1.0.3
<6>[   20.437495] device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
<6>[   20.437633] Bluetooth: HCI UART driver ver 2.2
<6>[   20.437722] Bluetooth: HCI H4 protocol initialized
<6>[   20.437808] Bluetooth: HCILL protocol initialized
<6>[   20.438624] cpuidle: using governor ladder
<6>[   20.439309] cpuidle: using governor menu
<6>[   20.439501] sdhci: Secure Digital Host Controller Interface driver
<6>[   20.439667] sdhci: Copyright(c) Pierre Ossman
<4>[   20.439934] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[   20.440122] mmc0: no vmmc regulator found
<7>[   20.440417] Registered led device: mmc0::
<6>[   20.440763] mmc0: SDHCI controller on tegra [sdhci-tegra.1] using ADMA
<6>[   20.440856] sdhci1: initialized irq 47 ioaddr fe600200
<4>[   20.441114] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[   20.441228] mmc1: no vmmc regulator found
<7>[   20.441549] Registered led device: mmc1::
<6>[   20.441794] mmc1: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<6>[   20.441959] sdhci3: initialized irq 63 ioaddr fe600600
<7>[   20.442565] Registered led device: notification-led
<7>[   20.442854] Registered led device: privacy-led
<7>[   20.444415] Registered led device: lcd-backlight
<7>[   20.446334] Registered led device: flash
<7>[   20.446564] Registered led device: torch
<6>[   20.447555] tegra-aes tegra-aes: registered
<6>[   20.451529] usbcore: registered new interface driver usbhid
<6>[   20.451773] usbhid: USB HID core driver
<6>[   20.452349] logger: created 64K log 'log_main'
<6>[   20.452597] logger: created 256K log 'log_events'
<6>[   20.452906] logger: created 64K log 'log_radio'
<6>[   20.453127] logger: created 64K log 'log_system'
<6>[   20.453686] oprofile: using arm/armv7-ca9
<6>[   20.453869] GACT probability NOT on
<6>[   20.453961] Mirror/redirect action on
<6>[   20.454116] u32 classifier
<6>[   20.454197]     Actions configured
<6>[   20.454283] Netfilter messages via NETLINK v0.30.
<6>[   20.454501] nf_conntrack version 0.5.0 (11505 buckets, 46020 max)
<6>[   20.454982] ctnetlink v0.93: registering with nfnetlink.
<6>[   20.458199] xt_time: kernel timezone is -0000
<6>[   20.458630] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[   20.458977] arp_tables: (C) 2002 David S. Miller
<6>[   20.459237] TCP cubic registered
<6>[   20.459905] NET: Registered protocol family 10
<6>[   20.461033] lo: Disabled Privacy Extensions
<6>[   20.461919] Mobile IPv6
<6>[   20.462010] IPv6 over IPv4 tunneling driver
<6>[   20.462756] sit0: Disabled Privacy Extensions
<6>[   20.463680] ip6tnl0: Disabled Privacy Extensions
<6>[   20.463964] NET: Registered protocol family 17
<6>[   20.464173] NET: Registered protocol family 15
<6>[   20.464486] Bluetooth: L2CAP ver 2.15
<6>[   20.464601] Bluetooth: L2CAP socket layer initialized
<6>[   20.464612] usb 2-1: New USB device found, idVendor=22b8, idProduct=2a70
<6>[   20.464623] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[   20.464631] usb 2-1: Product: Flash MZ600
<6>[   20.464637] usb 2-1: Manufacturer: Motorola, Incorporated
<6>[   20.465236] Bluetooth: SCO (Voice Link) ver 0.6
<6>[   20.465321] Bluetooth: SCO socket layer initialized
<6>[   20.465593] Bluetooth: RFCOMM TTY layer initialized
<6>[   20.465699] Bluetooth: RFCOMM socket layer initialized
<6>[   20.465856] Bluetooth: RFCOMM ver 1.11
<6>[   20.465941] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[   20.466026] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[   20.470698] mdm6600 2-1:1.0: MDM 6600 modem usb-serial driver converter detected
<4>[   20.471276] Disabling clock audio left on by bootloader
<4>[   20.471515] Disabling clock vfir left on by bootloader
<4>[   20.471635] Disabling clock pll_p_out4 left on by bootloader
<4>[   20.471806] Disabling clock pll_c_out1 left on by bootloader
<6>[   20.472013] Enabling Tegra protected aperture at 0x2e800000
<6>[   20.472056] usb 2-1: MDM 6600 modem usb-serial driver converter now attached to ttyUSB0
<6>[   20.472329] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 1
<6>[   20.472454] mdm6600 2-1:1.1: MDM 6600 modem usb-serial driver converter detected
<4>[   20.473493] regulator_init_complete: incomplete constraints, leaving vusb on
<6>[   20.473718] usb 2-1: MDM 6600 modem usb-serial driver converter now attached to ttyUSB1
<4>[   20.474014] regulator_init_complete: incomplete constraints, leaving vcsi on
<6>[   20.474199] mdm6600 2-1:1.2: MDM 6600 modem usb-serial driver converter detected
<3>[   20.475295] regulator_check_voltage: operation not allowed for vusb
<6>[   20.475762] usb 2-1: MDM 6600 modem usb-serial driver converter now attached to ttyUSB2
<6>[   20.475825] cpcap_whisper cpcap_whisper: CPCAP Whisper detection probed
<6>[   20.476367] mdm6600 2-1:1.3: MDM 6600 modem usb-serial driver converter detected
<6>[   20.476835] cpcap_rtc cpcap_rtc: setting system clock to 2011-03-30 16:55:50 UTC (1301504150)
<6>[   20.477398] Freeing init memory: 176K
<6>[   20.478177] usb 2-1: MDM 6600 modem usb-serial driver converter now attached to ttyUSB3
<6>[   20.478835] mdm6600 2-1:1.4: MDM 6600 modem usb-serial driver converter detected
<6>[   20.481572] usb 2-1: MDM 6600 modem usb-serial driver converter now attached to ttyUSB4
<6>[   20.647778] keychord: using input dev stingray-keypad for fevent
<6>[   20.698760] whisper_notify: accy=USB
<6>[   20.703030] cpcap-otg cpcap-otg: SUSPEND --> PERIPHERAL
<6>[   20.722880] mmc1: new high speed MMC card at address 0001
<6>[   20.723529] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
<4>[   20.728076] Primary GPT is invalid, using alternate GPT.
<6>[   20.728266]  mmcblk0: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[   20.749357] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: (null)
<6>[   26.365164] EXT4-fs (mmcblk0p10): recovery complete
<6>[   26.372539] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)
<4>[   26.415043] EXT4-fs (mmcblk0p9): warning: mounting fs with errors, running e2fsck is recommended
<6>[   26.418763] EXT4-fs (mmcblk0p9): recovery complete
<6>[   26.422202] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<4>[   26.469363] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
<6>[   26.585340] warning: `adbd' uses 32-bit capabilities (legacy support in use)
<6>[   26.585572] enabling adb
<6>[   26.598792] adb_open
<6>[   26.682814] gps_brcm4750_ioctl: Setting gps gpio reset pin: 0
<6>[   26.683000] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
<6>[   26.683267] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[   26.683408] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[   26.684760] gps_brcm4750_ioctl: Setting gps gpio reset pin: 1
<6>[   26.684906] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
<6>[   26.763575] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[   26.763672] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<6>[   27.277577] tear_down_dma
<6>[   27.277737] setup_dma
<6>[   27.279997] tear_down_dma
<6>[   27.280159] setup_dma
<6>[   44.689354] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[   44.689543] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<4>[   50.594319] wifi_set_power = 1
<4>[   51.003270] wifi_set_carddetect = 1
<4>[   51.004381]
<4>[   51.004385] Dongle Host Driver, version 4.218.248.20
<6>[   51.038448] request_suspend_state: wakeup (3->0) at 33339878001 (2011-03-30 16:56:21.050062001 UTC)
<4>[   51.051347] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[   51.051488] mmc0: new high speed SDIO card at address 0001
<4>[   51.056551] DHD: dongle ram size is set to 294912(orig 294912)
<4>[   51.170987] Firmware version = wl0: Jan 12 2011 13:48:56 version 4.218.248.20
<4>[   51.313321] wlan0: Broadcom Dongle Host Driver mac=<snip>
<4>[   54.186655] STA connect received 1
<6>[   54.883460] mtp_open
<6>[   55.870921] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[   55.871024] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<3>[   65.188394] binder: release proc 600, transaction 8298, not freed
<6>[   70.719196] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[   70.719302] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[   91.509091] whisper_notify: accy=none
<6>[   91.510297] cpcap-otg cpcap-otg: PERIPHERAL --> SUSPEND
<6>[   94.760897] binder: 832:833 refcount change on invalid ref 20
<6>[   95.478897] binder: 832:833 refcount change on invalid ref 31
<6>[  100.968782] whisper_notify: accy=USB
<6>[  100.969131] cpcap-otg cpcap-otg: SUSPEND --> PERIPHERAL
<6>[  112.229274] mtp_release
<6>[  115.909260] whisper_notify: accy=none
<6>[  115.910877] cpcap-otg cpcap-otg: PERIPHERAL --> SUSPEND
<6>[  136.329252] whisper_notify: accy=USB
<6>[  136.330662] cpcap-otg cpcap-otg: SUSPEND --> PERIPHERAL
<6>[  136.662973] mtp_open
<6>[  136.824673] android_usb gadget: high speed config #1: android

cat /proc/cpuinfo (mmmm dual corey goodness – tho cpuinfo doesn’t show it – i also removed the serial number, just in case…)

Processor    : ARMv7 Processor rev 0 (v7l)
processor    : 0
BogoMIPS    : 1992.29

processor    : 1
BogoMIPS    : 1998.84

Features    : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer    : 0×41
CPU architecture: 7
CPU variant    : 0×1
CPU part    : 0xc09
CPU revision    : 0

Hardware    : stingray
Revision    : 8300
Serial        : <snip>
A lil bit of df (/mnt/sdcard appears to be aliased to the internal data storage in absence of an actual sd card via a fuse driver)

Filesystem             Size   Used   Free   Blksize
/dev                   359M    32K   359M   4096
/mnt/asec              359M     0K   359M   4096
/mnt/obb               359M     0K   359M   4096
/system                236M   193M    42M   4096
/data                   28G     1G    27G   4096
/cache                 166M     4M   162M   4096
/pds                     1M   106K     1M   2048
/mnt/sdcard             28G     1G    27G   4096

cat /proc/mounts

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/pdsb /pds ext2 ro,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Thats it!

Fast forward to 2010. It’s been long enough, I figure the AMD/ATI integration should’ve helped them out by now, right?  Buy a new machine with two ATI Radeon HD 5870′s. Capable of 850MHz GPU clock and a 1200MHz memory clock, before overclocking or tweaking. Right out of the box I get underscan on my HDMI connection. No worries I think, fire up ATI Catalyst Control Center (CCC) and turn it off, problem fixed. Really retarded that they do that at all, but whatever.

Cue reboot to do the obligatory windows update…WTF? Underscan again? OK maybe drivers got punked, reset it, yay. All is good. A day or so later, another reboot. ?!??! UNDERSCAN AGAIN!?!?! Go get latest Catalyst drivers. They don’ properly install so I have to uninstall them, run driver sweeper, and then try the install again. Back to underscan…reset…but now the underscan is clearly on on EVERY reboot. Resort to Googling. Apparently this bug has been around for a damn long time. And may even be that it keeps coming back. How about this ATI. Since almost NO HDMI compatible display device is going to desire underscan, JUST DISABLE IT BY DEFAULT!? No nVidia card I’ve had has had this issue.

So on top of this really painfully obvious underscan issue, the driver installer/uninstaller doesn’t work right.  Its so bad in fact that ATI’s own people often point customers to driver sweeper instead of FIXING the damn thing.  Installing new drivers is not remotely seamless like it should be.  Upgrades should always be pain free, download installer and run.  With ATI’s packages running the installer like that may or may not get you fully updated depending on the phase of the moon, color of your hair, and whether the geese have flown south for the winter or not.

Another irritating one. And one I’ve attached a GPU-Z screenshot for. With Adobe Flash 10.1, playing any flash accelerated video, IE from YouTube, will lock your Radeon HD 5870 to 400/900, no matter what. I fired up Kombustor and FurMark to prove it. Close the YouTube window and your clocks unlock to 850/1200. This is another bug that goes WAY WAY back after a bit of Googling.

Seriously ATI?

The attached image shows me first firing up a YouTube clip in FireFox.  The Video clock jumps to 400/900 and sticks…a little odd, especially if the video is paused but whatever…. Then I fire up MSI Kombustor (same as FurMark).  The GPU load jumps to 100% but the clocks stay locked at 400/900.  I close the YouTube clip, and the clocks then unlock and shoot up to 850/1200.  The Kombustor/FurMark frame rates reflect the hobbled video card clocks.  Nothing I do unlocks the clock from 400/900 as long as Flash is playing video.  This is with the latest Catalyst 10.9a (Hotfix) drivers.  I had to install these to get rid of the previously mentioned underscan idiocy.

Same behavior with Google Chrome and Microsoft Internet Explorer 8.  This is all running on Windows 7 Ultimate x64.

So in short, don’t get ATI. They can’t get their drivers right. You never know when a bug will come back, or when/IF they’ll fix performance critical bugs. I shouldn’t have to make certain to close each and every browser window to play a game, get max performance for a transcode, etc. Not on a machine with 4x 3.2GHz cores.  The experience here with this card follows similar bad experiences with the older card and software (I had underscan issues on that one too, and performance issues that may or may not have been similar, but I never looked into it too deeply).

You drop thousands of dollars for a high end gaming machine/workstation.  1/4 or more of that will be in the video cards, and this is what ATI delivers.  I’ve found articles on AMD/ATI’s own forum from users indicatign BOTH these issues go back to *at least* mid 2009, and probably earlier.  Why am I not blaming Flash?  Even if Flash is asking for video acceleration, or asking for a 400/900 clock, the ATI drivers should STILL adapt the clock to the GPU load.  If the GPU pegs out it should let the clock go.

Ahem…*cough* Now that that’s out of my system. I made a decision at the beginning of this month to move all of my hosting to an Amazon EC2 instance. While nowhere near ideal for web hosting and not really much cheaper than my current hosting arrangements, and quite frankly only cheaper as long as my bandwidth usage stays down! I decided to switch for a number of reasons. Part of those are the fact I honestly don’t want to deal with the hardware anymore if I can avoid it.  Tehy really really really NEED to get IPv6 support though…and that will be the deciding factor as to if I stay using EC2 or not.  Without IPv6 they’re garbage and I’ll go elsewhere and pay more, because I’ll have no choice, just to get IPv6 support.

The web sites will have about the same CPU and RAM as they had before, but may actually be somewhat faster because the storage should be faster. The (soon to be) old hosting setup I’d elected to build uses NFSv4 and the Linux automounter, an experiment that proved to me that Linux NFSv4 is NOT ready for prime time (even in my limited setup NFSv4 will occasionally go off into the woods and NEVER come back short of a reboot of the machine, this happens most often on the web server and once in a while to the mail server) the automounter has been stable but NFSv4 mounts are dog slow, with, or without encryption setup.

So if you notice any oddities this week that is most likely why.  I’ve already finished moving my @wgops.com email over to the new setup and it seems to be working fine.  This weekend I’m going to try to get dotblag.com moved over to the new setup.  If that goes well then I’ll get in touch with the few people I host and we’ll get them moved over to the new machine too.  This is actually a really small move, but I’m going between completely unmanaged hosting, to trying out a management UI/platform, DTC.  If things don’t go well with the dotblag.com move then I’ll have to scramble and figure out something else ASAP!  I can’t really afford to pay for both the old hosting and the new hosting.

Incidentally if you need reliable  Colo, VPS, or web hosting, especially if you’re running a dynamic PHP application powered site but don’t want to pay premiums for dedicated hosting, get in touch with Modwest.  I might be leaving them, but it’s not because there’s anything wrong with them!

I am NOT a GUI guy, photo guy, etc.  I traditionally have been a systems administrator, lately I’ve gone more whole hog into web application development.  But I still don’t do UI.  So color has never really felt that important to me.  I know my display isn’t right, and it bothers me a bit but it doesn’t cripple me.  Sometimes the grays wash out, they turn blue, colors just aren’t quite right.

My editor displays little gray pips for spaces, they show up well on my 21″ (Sun GDM-5010PT) Sony Trinitron monitor w/ built in color correction/calibrations.  On my (cheap) ASUS G50vt laptop (the same one that the integrated keyboard has a horribly broken debounce to the point it misses keystrokes and words constantly), they’re almost invisible.  The color rendition is quite frankly, just plain bad.  I figure there’s nothing that can fix it.  But being an adventurous soul, I decide to plop down about $230 on a color calibration dongle and software.  If nothing else the Trinitron will probably look better, and I can quantify how bad the laptop is…Figuring worst case I’m out $230 and then won’t be tempted again.  But I’m still definitely as skeptic.

Flash forward a week….

Device arrives, I hook it up, download software from the manufacturers web site and install it.  The device came with a CD but as we all know, they’re always out of date, this one was from ~2007, there is rather quite a bit more up to date software available on the website from the manufacturer.

The software asks a few basic questions about the display, and it’s adjustment capabilities.  Advising on how they should be set, presumably to achieve correct calibration.

After answering the software’s questions which are basic, despite reviews to the contrary.  I hang the dongle over my laptops display as directed and tell it to go to work.  It displays black/white/red/green/blue and samples many levels of each.  After it’s done it applies the profile to the OS’s color calibration system (Windows 7 Ultimate x64 in this case).

Immediately I notice the display color is, overall, a bit warmer, that’s expected, since this display was always on the cool/cold side anyway.  I finish out the utility, and fire up my editor.

I can see the little gray pips that indicate spaces now…the gray title bars show up much more clearly now…

I fire up my web browser and go to newegg.com, which has this light manila background that never really showed up before.  It pops, just like it’s supposed to.  I go hit php.net, which I know has quite a lot of fairly subtle greys, blues, and purples.  Amazing, they all show up now. I spend a few minutes visiting some web sites, and am amazed at the details that now appear, and were so washed out before.  Even my WordPress admin area on this blog looks better, easier to read, as it was intended!

Now, like I said, not a GUI/graphics guy, but I know how to adjust my contrast, brightness, and backlight settings to correct black or white aliasing, simple issues.  But that’s nowhere near enough to fix an overall color rendering or temperature problem.  I can fiddle in the nVidia (or ATI) control panel applets and get it better, but never have I gotten it good, much less great, especially on this particular laptop display.

At this point I have to say wow.  My laptop display looks better than my 21″ Trinitron tube….I can’t wait to try it on that!  I’m definitely *sold*.

The specific device I grabbed was a Datacolor Spyder 3 w/ the Elite software because I figured if I like it or use it at all I’ll need multiple monitors, and multiple machines.

I’ve always said that if you’re doing any sort of graphics development,  you need color calibration.  I now would go so far as to say if you’ve ever been irritated by your laptop, or other display, you need color calibration.  If you’re doing ANY sort of UI work, at all, you need color calibration.  It is WELL worth it.

I wish I could show the difference, unfortunately I can’t, but it really is night and day.

CloudEngines saw fit to include relatively robust filesystem support sporting HFS+, NTFS as well as the usual ext2/3, FAT/FAT32/VFAT.  HFS+ is provided by custom kernel modules, that work better than their cousins integrated into the Linux kernel (I’ve had some experience with them).  I haven’t yet tested the NTFS support.

The really unique thing about the Pogoplug is that it is completely integrated with the Internet.  The API system allows you to write your own scripts, or use others.  You can even cross-compile and run binaries on the Pogoplug itself.  Setup was easier than anything I’ve ever used of this nature. I plugged my device in, and went to the Pogoplug site.  I created a login, it quickly identified my Pogoplug device (I assume the Pogoplug called home and it saw us both coming from the same IP) and I was able to immediately use the WebUI to upload and download files.  They don’t support SMB/CIFS, but they have OS level drivers for Windows, OS/X, and Linux readily available.  I’ve only tried the OS/X and Win64 (Windows 7) drivers and they work very well.  Honestly since they seem to be fully supporting multiple OSes, and SMB/CIFS is so complicated and slow I don’t feel like this is much of a minus.  It does limit native support to “Supported” OSes for now unless the WebUI/API access fits for you.  I don’t know what their product roadmap is but I did find a (broken) symlink/mention of Samba within the device itself, and for those users that are on other OSes and *really* want CIFS they can cross-compile and install/run their own Samba binaries.

The native clients I’ve tested under Windows 7 and OS/X 10.6 (Snow Leopard) seem to perform well and bug free.  I’ll be pushing them a bit harder in the coming days to see what happens.  So far though I’ve had no issues.  The Native clients can be set to multiple drive or single drive mode.  The Windows client defaults to single drive mode with all of your connected drives showing up as P:\<Device Name>.  The OS/X (and I assume Linux clients) default to multiple drive mode with all of your connected drives showing up as separately mounted volumes.

You also can not initialize (format) a drive from the Pogoplug.  So you have to format your removable devices with a PC/Mac first.  This rather minor since if you have this device, then you have a machine, and the drives are removable by nature.

Performance is also very good, thanks in no small part to the speedy embedded Orion SoC, the Ethernet controller also has TSO, Receive and Transmit Checksum Offloading (part of TOE) which helps keep the CPU free from a lot of overhead.  These offload features are common in higher end servers and many ‘gaming’ Ethernet adapters.  Having a 1.2GHz CPU and these helpful hardware offload engines means that the CPU doesn’t work too hard and the performance will generally be limited by the RAM speeds.  To get the full LAN performance you do need to install the native clients.  The unit may be a little slow when you first start it as it indexes your files for searching and generates thumbnails and video previews.  This latter bit enables one of the more interesting features, search.

You can search all of your Pogoplug drives relatively easily from the WebUI, I haven’t toyed with this much yet but on the drive after you mount it the Pogoplug software creates a .ceid file that includes the name of the device and the version of the metadata, and a .cedata directory holding an SQLite 3 database file for indexed information and directories for the generated thumbnails and video previews.

The Pogoplug also ‘integrates’ with Facebook, MySpace and Twitter.  The Twitter support is definitely buggy, I was able to authenticate to it for one drive but not for another, and after signing out I have been unable to authenticate again.  Once setup you can ‘share’ a folder to these services and the unit will post updates whenever the folders are changed.  The update includes a (public) link to the folder’s contents.  Users can then download the data.  However the data is pushed directly from your Pogoplug so you must be connected via broadband.

On the hardware side inside the case there’s documented JTAG and Serial Port.  What does this mean?  Well if you’re asking then it won’t matter to you.    Basically it means that with a JTAG dongle and a 3.3v FTDI to USB serial adapter you have a $130 ARM9 dev kit, not bad at all.

I haven’t (yet) opened mine…I may yet buy another to do just that.  The Orion/Feroceon has a SATA controller that’s turned off (and quite possibly not even pinned out) on this board.  It also has a second Gig-E MAC thats likewise not available.  The CloudEngines/Pogoplug Engineers do read their forums, and seem to be (refreshingly!) helpful to those people who ask specific questions about the hardware and essentially how to use it as a dev platform, de-brick it, etc.  Being so helpful as to even link to DigiKey Parts for the mating connectors to the JTAG/Serial ports.

There are some chinks.  It has a NEON PINK “foot”.  The device has no ‘shutdown’ command (either via WebUI or SSH, or anything) so you can’t cleanly shut down the unit, you have to manually eject via the WebUI.  Unplugging the device, at least with HFS+, can cause the filesystem to come up ReadOnly with no way to fix it from the Pogoplug short of ejecting the device and manually running the included chkhfs utility.  Even that may not work since the utility is based off hfsprogs, which aren’t very good.  It will claim errors, not tell you what they are, and refuse to fix them.  Morale, either eject before you unplug the Pogoplug, or use other, better supported, filesystems.  I also have no clue what happens to the device when it loses Internet connectivity.  It may turn into a pretty pink and white brick, I don’t know, that’s one of the only things that actually worry me so far. I’ll be toying with that in coming days and make an updated post time permitting.

I keep seeing a LOT of well meaning but mis-informed or mis-understood claims about IPv6, even in technical circles. What I am going to try to address here though is from the every persons point of view. What it is, why we need it, what it fixes, why it’s hard to deploy/make available, what it (may) mean for an individual user.

The article here was sparked by IO9′s Article.

What Is IPv6?

Well simply put it is Internet 2.0 or Web 2.0, despite what you may have heard from the media.  IPv6 is short for Internet Protocol Version 6.  We currently use IPv4. IPv6 has a truely massive number of addresses (really, it doesn’t relate in simple terms).  IPv4 has around 4 Billion addresses, of which about 3 Billion are useable.  IPv6 though is big enough to give every person on the earth, every device, every item, it’s own group of say a million addresses, and still have many trillions left over.

Why is IPv6 the Real Web 2.0?

AKA Why is it so had to get IPv6 out there?

Because it requires touching and replacing or modifying every router, every piece of software, every device, in order to support it.  Your web browser, your operating system (Windows, Linux, OS/X), your Internet router/gateway (which a LOT of people confuse between ethernet switches and these things), your wireless access points, your ISPs equipment, your TiVo, your smart phone, everything.  This is also why it’s so very hard to get out there.

Now the tech heads and geniuses out there responsible for this have developed a number of ways to assist this migration to IPv6.  To allow IPv4 and IPv6 to sort of talk to each other.  They can easily exist together, but talking to each other is another matter entirely.  These methods are not perfect, they suck actually.  From the IPv4 side, it’s like sending a letter addressed to a city rather than a person.  For IPv6 it’s easier, in fact, there’s a block of IPv6 addresses (these blocks of addresses are called a prefix, like an area code, so I’ll use the term prefix from here on out) that are set aside to map directly to the old IPv4 addresses.  That’s how big the address space in IPv6 is!  Whats the number?  OK you REALLY sure you want to know?  Fine.  2¹²⁸ — Two to the power of 128.  That’s in scientific notation 3.4*10³⁸ or a 34 followed by 38 zeroes (rounded). How big is that? Every single dollar bill of the American national debt could be individually numbered. And we’d still have a LOT of space left over. Heck we could give out a Trillion addresses to every person, device, or object on the planet, and still be likely to have leftovers.  The TCP/IP Guide has a Section On IPv6 Address Space Size

IPv4 addresses are everywhere.  Dotted quad’s we call them.  4.2.2.1 — 127.0.0.1 … etc.  Largely people are ignorant of them, and they damn well should be.  Numbers are for computers.  Humans name things, computers number them, and computers are REALLY good at translating and mapping between the two.  DNS is the protocol that does this.  And in that it’s been so successful that the vast majority of Internet users have no clue whatsoever that IP addresses (v4 or v6 or otherwise) even exist!  DNS itself needs to be revamped as a protocol in order to support IPv6 (and it largely has been) — and then redeployed too, globally.  This is taking place bit by bit.

E-Mail.  Every mail server has an IP address (or more than one in many cases).  It receives connections on that address from other mail servers and mail clients asking them to receive mail for, or send mail to, a given email address (user at domain).  Spam filtering software.  Anti-Virus software.

All of this stuff is on the list of things that need to be modified, or replaced for IPv6 support. The list is huge.

Why Do We Need IPv6?

We’re running out of IPv4 addresses.  No one in the beginning could possibly imagine that there would be such a huge number of devices connected to the Internet.  Now almost every phone, game console, and electronic device has some form of Internet connectivity.  That doesn’t necessarily mean each of these devices needs a globally unique address, but it makes things easier, faster, more reliable, and cheaper if each device does.  The reason is that if you use NAT (many many homes do this) your private address has to be mapped to a public one at some point.  This device has to keep track of each and every connection from each and every device that it’s performing this mapping for.  Worse some protocols put IP addresses inside of their data, and so the NAT has to know about these protocols, identify them, and modify the information inside the packets for these protocols!  (FTP is one such protocol, HTTP is not).

Well why not reuse all those “Web 1.0″ addresses?

IPv4 is “Web 1.0.”  The media gave us all that term, and most people have no idea what it means.  Web 2.0 (Go ahead and look, we’ll wait here) really only describes a bunch of web browser, JavaScript,  and HTML technologies and says nothing about the actual core guts of the internet IP, DNS, BGP (this is the ISP to ISP route sharing protocol — every ISP “core” router HAS to speak this to other ISPs), OSPF (this is one of a number of ISP internal route sharing protocols, MPLS.  Nor anything about a lot of other core internet protocols like HTTP, SMTP, IMAP, etc.

So wow I will get my own unique addresses?!

No, not likely.  This is because of the way that “core routers” (there’s no such thing by the way, which I will try to address in a moment) have to keep track of each unique destination.  Right now, and for the foreseeable future with both IPv6 and IPv4 the ay this works is that a ISP get a BIG block of addresses (BIG being relative in the terms of IPv4 or IPv6 — with IPv6 they get a LOT more space…enough in fact to have an IPv6 address within their own network for each IPv4 address and still have a billion left)… So they tell the other ISPs they’re connected to about that one big block, not about individual customers or devices.  They say to their neighbor “I can deliver packets to addresses beginning with 127.0, pass it along.”   Another ISP might have 127.1 another might have 127.2.0-15, etc.  IPv6 does the same thing.  IPv6 addresses are just so much longer I’m not using them in this example.  The neighbors only know about and remember the big block of addresses, not the individual addresses or smaller blocks given to individual customers.

Now within an ISP they keep track of many more much smaller blocks of addresses, maybe even down to individual addresses.  Inside an ISP similar trading of information on what addresses are served by which of their routers happens (no this does NOT happen with the average end user!).  The difference here is that since they’re all internal addresses, and a router notices when two or more addresses or blocks occur contiguously, they are often aggregated into a single larger block.  Think of it like this.  Router A is connected to B C D and E, E is connected to F and G.  F has 1 2 and G has 3 4.  E knows this, instead of telling A about 1 2 3 4 (and A further telling B C and D about 1 2 3 4) it just tells A 1-4.  Imagine this for a few hundred, and you can see the savings.  Instead of passing along each individual number it just tells it a range of numbers.  There are restrictions on how these ranges are made up (for the geeks out there it has to be on a bit boundary), but that’s the basic idea.

Wait what’s so different about inside an ISP versus outside?!  — simple, inside the ISP they know the adjacent addresses STAY adjacent and are inside the same entity, themselves.  Out in the bigger internet you can’t do that.  You might own 1 and 2, but someone else is 3 and 4.  And you don’t want packets for 3 and 4 arriving at your doorstep, now do ya?  Well that’s what would happen if the big ISPs aggregated routes together like that, because once a route is aggregated it loses it’s own unique identity.

Whats so wrong with having lots of routes then?  Two things, memory and speed.  Memory is finite.  And the memory used in big “core routers” is far more expensive (and far faster too) than your desktop or laptop memory.  Speed is the other reason.  Big routers have less than a microsecond to decide where a packet is supposed to be going, and do something about it. They make a huge number of these decisions in parallel too, and each of these decisions have to reference some part of the database of what-goes-where that the router has built up for itself based on who it’s connected to, and what they say they are connected to.

Earlier you said there’s no such thing as a “core router”?

Indeed I did.  For this discussion, you don’t have a router.  Indeed we at ISPs call what you have CPE, Cutomer Premise Equipment, or an End User Gateway Device.  They’re meant to connect one machine, or a very small number of machines (4-5 at most typically) to the ISPs router and from there the internet at large.

The internet is a bit more like a web.  A cobweb.  Lots of different parts connected in lots of different ways.  You as a end user are only connected at one point, to your ISP via your cable modem, DSL line, satellite, smart phone, or, old fashioned dial up modem.  Your ISP, if it’s a small local ISP will be connected to 2 or more (usualy atleast 3 or 4) larger ISPs, and possibly some other small local ISPs or local business customers that have their own routers.  Each of these routers tell each other who they’re connected to.  As connections between ISPs are made, and broken, this changes.  Each of these changes ripples through the internet, so when an ISP in say Missoula, MT disconnects from another ISP here in Montana that has been telling everyone it’s connected to that it is connected to that ISP, every big ISP knows in seconds, and every small ISP in some seconds after that.  So what just happened in Missoula, MT is known in Beijing, China in very short order.

This is also another reason why individuals can’t have unique addresses that move between ISPs  You may not move from one ISPs territory to another very often, but there are billions of people out there.  Imagine now that those updates too have to be propagated and stored.  Starting to see the problem?

Larger businesses with dozens or hundreds or workstations, or on site servers, or other specil high reliability requirements connect to ISPs in much the same way as ISPs connect to each other, they just don’t say to ISP B “hey I am connected to ISP A so you can reach ISP  A through me” but they do tell both A and B that they have the addresses 6 7 and 8 say.  This is called multihoming.  Why?  Well think of an ISP as a “home” for an address.  Your address exists at multiple “homes” when you connect with multiple ISPs and advertise to each of them your block of addresses.  There’s an intentional barrier to entry here because ISPs do not want, and cannot support, an unlimited number of these connections, because each of these connections requires the Internet as a whole to see and remember the unique block of addresses assigned to that business.  And whenever that business disconnects (say they’re upgrading their network or have a long lasting power outage) from one ISP or the other, the whole Internet hears about it, each router tells all it’s neighbors about that change in connectivity.

There’s a LOT of research going on into better ways of dealing with the global routing table (that’s what it’s called…but there really isn’t one table, it’s more like each router has it’s own idea or ideas at what the routing table looks like right *now* and if you wait even half a second, it’s going to change, probably several times) but no one has found a silver bullet yet.  And even if/when they do, there’s still the same problem we have with IPv6, all the ISPs have to adopt and deploy it, everywhere.

If there’s interest I’ll go into TCP/IP, UDP/IP, DNS, and BGP/OSPF/Routing in a separate article (or articles).  How a connection is established, what NAT is, what a Firewall is/does and why NAT and firewalling are different, and why routing is different than those two.

For a while now I’ve had a +12VDC wall wart that I use occasionally.  It always caused weird heating though in regulators.  I was never sure why, the multi-meter read it as having a fairly stable +12VDC.  I finally hooked it up to an oscilloscope today…well now atleast  I know why…

It’s supposed to be producing +12VDC, center positive.  What you’re looking at is the center pin (tip) on the yellow (CH1) channel, and the ring  (or barrel) on CH2.  The trigger is on CH1 @ the rising edge of the wave at 20V.  As you can see it’s getting voltages as high as +65V and as low as -110V.  It follows the AC line perfectly, the cycle time measured by the scope almost exactly matches that of the AC line.  In fact if I trigger on the AC line (this scope can trigger from it’s AC line input) the waveform stays completely steady.

The second picture shows in red what a multi-meter reads.  Which the scope reproduces by differencing CH1-CH2.  The ripple is a bit better when it has a load but it’s still producing these ridiculously high voltages.

So, it’s producing +12V…sorta.  Only as a function of the difference between it’s own +/- reference.  Even a good multimeter can be fooled by a bad signal.  Normally you’d probably never even notice this because you’d hook your multimeter up to your projects GND which is usually the – on the power supply.  If you’d tied this wall warts – to GND, you’d either cook it, or hit it’s current limiter, or both.  This little sucker is probably going to be dismantled and tossed.

BEWARE CHEAP WALL-WARTS!

SO! While I’m waiting for those, I was wondering, by comments, if you could make something what would you make?  You never know, I might just throw it together.

Oh and for those wondering what I fudged (and realized that it was fudged like really, just hours after sending it to the PCB house and past the point of no return) it’s a ZIF socket fixture for my STK500 (well or any AVR 10 Pin Programmer) for 28PIN ATMEGA168 compatible DIP parts The next rev will be much better.  I forgot to put space for an external oscillator which I use in most of my circuits…the cost of the oscillator and caps is negligible but gives you a much more stable, and if you want faster, clock. Without that you can’t actually program the microcontroller once it’s set to use an external clock.

The other board is going to undergo some serious changes too, but in it’s basic form will probably be used atleast initially as the basis for my own toaster reflow oven for soldering surface mount components (like QFN/MLF bastards with blind thermal pads).  It also makes it WAY easier to do SMD’s because you basically put some solder paste on the board, place the parts, then bake them.  You just basically touch the solder melting (flow) point for ~45 seconds or so, then let the parts cool.

I do have some ideas, but the ones I’ve got pending will depend on if the oven project is successful or not   It should be, but the one I’m thinking of will really need surface mount components.  So will an improved rev of the controller board for the oven itself, which is actually for a completely different project!   That’s the beauty of software.

I’ve finally found a relatively cheap place to have boards fabbed up, it just takes ~3 weeks turn-around.  But I can have single boards done for around $15 S&H + a cost for their size.

versions 1.2 (sent out for actual prototype) and version 1.3 (in progress) — depending on how well things work out with converting the 1.2 board to a toaster reflow oven…or if i can work out an alternate hot plate system v1.3 will quite probably switch to using SMD’s for the ATMega, the MAX232, most or all of the resistors and capacitors, and probably even the LEDs.

Why is SMD so much better?  Well first the parts are smaller, second, if you take a look at those pictures you see that the pins themselves on DIPs are *HUGE* compared to the traces.  And each pin/pad punches a hole through your board reducing the space you have to run signals.  v1.3 there as you see it took quite a bit of massaging to get everything.  v1.2 has a DB-9 (serial) port pictured, v1.3 right now has a Molex part that’s very similar to a PC to motherboard power connector.  I’m still debating on exactly what to deploy with that one.  Ultimately I want a weather tight connector.  The ones I’m looking at now actually mount with a pig tail, but they’re spendy, though they’re fully sealed.  Really it probably doesn’t matter as the parts are all pretty hard to kill.  The Molex connector causes the problem that I have a hard time getting the bigger traces to it for the relays, so the NO/NC/Center traces for the relays I was manually routing for a bit there…and may end up doing that in the final product too.  v1.3 also has three PTC self resetting fuses to protect the board that I omitted in v1.2.  I don’t ever plan on letting anyone else get ahold of v1.2, it is 100% prototype, v1.3 though I want to be the first real board.  I also set things up so you could make the board (well should be able to) somewhat Arduino compatible, but the oscillator I use is a lot faster than the Arduino sheet’s I’ve seen.  I have NO experience with them, but it was a simple hack to put the jumpers in so I could play with it.

For BOTH boards what you’re NOT seeing is the ground plane and +5v plane “fill” polygons of copper.  Thats part of what took a lot of tweaking in v1.3 — in v1.2 I didn’t look much at it.

Why?  Well…why not?