At Google I/O, the attendee brought back Samsung GALAXY Tab 10.1. I had a chance to touch it.

At first I tried to connect it to Windows 7 PC by USB cable. But it said failed to install USB driver. Someone said Samsung special develop tool includes the USB driver. But I don’t want install such kind of big software. I just want USB driver for GLAXY Tab. I thought NexusOne’s USB driver might work with small change of configuration file, it didn’t get well.

However, when I tried from Ubuntu virtual machine on VMWare it worked fine. I show you what I did.
(Japanese version of this page)

Checking vender ID of USB

Connecting GALAXY Tab with USB cable and disable USB host connection and enable USB connection of VMWare virtual machine. Then use lsusb command.

$ lsusb 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 04e8:685e Samsung Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ 

It shows vendor ID is 0x04e8, product ID is 0x685e.

Adding udev rule

$ sudo vi /etc/udev/rules.d/51-android.rules 

Add a line below.

SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"

Then restart udev.

$ sudo restart udev
udev start/running, process 28938

Connecting via adb

 $ adb devices
 * daemon not running. starting it now on port 5037 *
 * daemon started successfully *
 List of devices attached 
 33C11C2416024D7	device
 
 $ adb shell
 shell@android:/ $
 shell@android:/ $ cat /proc/cpuinfo
 Processor	: ARMv7 Processor rev 0 (v7l)
 processor	: 0
 BogoMIPS	: 1998.84
 
 processor	: 1
 BogoMIPS	: 1998.84
 
 Features	: swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 
 CPU implementer	: 0x41
 CPU architecture: 7
 CPU variant	: 0x1
 CPU part	: 0xc09
 CPU revision	: 0
 
 Hardware	: p3
 Revision	: 000b
 Serial		: 32479070f2cfba4e
 shell@android:/ $

OK.
/proc/cpuinfo shows 2 armv7 processor is running, no NEON and only 16 double registers at FPU.

I remember this target’s CPU is Tegra2 and they say it doesn’t have NEON.

About these ads