If you get your own Vendor ID from usb.org, then you can make up your
own Product IDs however you like. But if you do not have a Vendor ID,
you need to find someone that does and have them allocate one for you
based on whatever numbering scheme they use.
Google has its own vendor ID (0x18D1) that we used for Nexus One, and
sometimes use temporarily while phones are under development. But
most android phones use a vendor/product ID assigned by the
manufacturer (HTC, Motorola, Samsung, etc).
Mike
On Thu, Jul 15, 2010 at 9:23 PM, Arindam Roy <rarin...@gmail.com> wrote:
> A noobish query;
> Where do you get the values for th product id?
> usb_products[] = {
> 168 {
> 169 .product_id = 0x4e11,
> Thanks,
> Arindam
> On Thu, Jul 15, 2010 at 10:28 PM, Mike Lockwood <lockw...@android.com>
> wrote:
>>
>> Hi Danke,
>>
>> The USB serial module probably wants to own the entire USB interface,
>> which means there would be no way to use adb at the same time.
>>
>> I would recommend using the f_acm.c function driver instead, which we
>> already have working with the android composite driver (we were going
>> to use it for tethering in froyo but decided to use RNDIS ethernet
>> instead). To do that you would need to enable CONFIG_USB_ANDROID_ACM
>> in the kernel config and add support for it in your board file. See:
>>
>>
>> http://android.git.kernel.org/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/board-mahimahi.c;hb=android-msm-2.6.32
>>
>> for an example.
>>
>> Mike
>>
>> On Thu, Jul 15, 2010 at 11:29 AM, Danke Xie <danke....@gmail.com> wrote:
>> > I was trying to connect to the serial port on the Android device from
>> > the host PC. What I was doing was loading the "usbserial" driver:
>> >
>> > modprobe usbserial product=<product id> vendor=<vendor id>
>> >
>> > It seems it does recognize all serial functions in the USB and created
>> > several ttyUSB ports/devices. However, it seems (at least on my
>> > device) that the interface used by ADB is also picked up by
>> > "usbserial", and because of that, I couldn't use ADB to connect to the
>> > device until I unload usbserial.
>> >
>> > Do you know if this is an issue? Is there a way to get both usbserial
>> > and ADB to work?
>> >
>> > Thanks!
>> >
>> > --
>> > unsubscribe: android-kernel+unsubscr...@googlegroups.com
>> > website: http://groups.google.com/group/android-kernel
>> >
>>
>>
>>
>> --
>> Mike Lockwood
>> Google android team
>>
>> --
>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
>> website: http://groups.google.com/group/android-kernel
>
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
--
Mike Lockwood
Google android team
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
