On 6 Nov, 09:51, "Cédric Berger" <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 04:57, Sean McNeil <[EMAIL PROTECTED]> wrote:
>
> > Mike Lockwood wrote:
> >> On Wed, Nov 5, 2008 at 5:53 AM, cedric.berger
> >> The Windows driver should work as long as you edit the VID and PID in
> >> the .inf file to match the values in android_adb.c:
>
> >> #define DRIVER_VENDOR_ID 0x18D1
> >> #define DRIVER_PRODUCT_ID 0x0001
> I indeed changed the
> .inf with the VID / PID I picked in windows manager when neo was
> plugged : I added
>
> ; For XP and later
> [Google.NTx86]
>
> ; Neo
> %USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev,
> USB\VID_1457&PID_5117
> %USB\VID_1457&PID_5117&Rev_0212.DeviceDescRelease%=androidusb.Dev,
> USB\VID_1457&PID_5117&Rev_0212
>
If adb.exe expects to use the Driver ID of 0x18d1 and we need to tell
windows to use a VID of 1457 to recognize the USB device, the
Freerunner is apparently telling the windows PC it is a VID 1457 USB
device. If the 0x18D1 is hardcoded into adb.exe someone need to
recompile it with the Freerunners VID (or change the VID used by the
Freerunner, but that is unwise as VIDs should be unique...). To
summarize - the lines
#define DRIVER_VENDOR_ID 0x18D1
#define DRIVER_PRODUCT_ID 0x0001
in android_adb.c must be changed to the VIDs and PIDs in the .inf file
to let adb work with the Freerunner under windows.
Best regards,
Anders Hedberg
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
