History log of /system/core/fastboot/usb_linux.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
a61bcad58ba1f7359183a333ee58303ed67e4a2f 02-May-2012 Scott Anderson <saa@android.com> resolved conflicts for merge of 13081c69 to master

Change-Id: I631e466fc53e9b0f4a39f24f959b4ae9b626bdda
13081c6915220db03886b177f1a8e0b2c63467c9 06-Apr-2012 Scott Anderson <saa@android.com> fastboot: Add ability to specify device path

For manufacturing and testing, there is a need to talk to
whatever device is connected to a given port on the host. This
change modifies fastboot's "-s" option to take either a serial
number or a device path. The device paths of the connected
devices can be listed using "fastboot -l devices" whose output
will resemble:

016B75D60A00600D usb:2-5 fastboot
AD3C12020173 usb:1-4.3 fastboot

The second column lists the device paths. If the -l option is
not given, the output from "fastboot devices" will be the same as
it used to be (i.e. the paths will not be printed).

Finally, note that the format of the device paths are platform
dependent. The example above is from Linux. On OS-X, the paths
will be "usb:" followed by hex digits. For Windows, the device
paths will be printed as "????????????" and the -s option will
not be able to select a device until someone implements the
underlying functionality in usb_windows.c.

Change-Id: I1f01b8f47acd32edb0ac18db107316a2c923bbde
Signed-off-by: Scott Anderson <saa@android.com>
f8ff3a5ae21ce34f22928709cc6f992ff2fdd56e 19-Apr-2012 JP Abgrall <jpa@google.com> fastboot: Keep borked bootloaders happy by shrinking URB len.

Some devices will fail to return the requested data if the final
URB len of the request to > 255.
So shrink the current data buffer from 128 to 127 in the acse of getting
the serial number seems to work just fine.

Change-Id: Ic24e6c86ec93f002dc721d92309b3f880f281f20
5ae3f93f3bafbeb1fc9a3324475c58c725749c5e 28-Feb-2012 Anatol Pomazau <anatol@google.com> Remove trailing whitespaces

Change-Id: I6f83333a6ee0fbc562a12bb9555c43a44c98768e
c840653efd8d05a33778d3e73c3521977564bde3 08-Jul-2011 mgross <mark.gross@intel.com> fastboot: set the language local string

Set the language local string to 0x409 (English US / en-us) such that
fastboot will successfully read the usb descriptor serial number string.
The usbdevfs ioctl fails when the wIndex is not initialized with the
local for the unicode of the usb descriptor string. usbdevfs is an
obsolete interface and fastboot probably needs a re-write to use libusb
like what is in adb.

Change-Id: I3687f84643f53c736f14b3ae7793185d9b5cccc0
Signed-off-by: Mark D Horn <mark.d.horn@intel.com>
913eb8bf874fcec647667bd7113da65b6e38488a 08-Mar-2011 David Krause <david.krause@motorola.com> Enlarge USB bulk transfer size for faster downloads

The default USB transfer bulk is fixed as 4096 in fastboot util code for
Windows and Linux. Enlarging the bulk size can greatly improve the image
download speed via USB.

For Windows, adjust the max bulk size to 1MB to maximize the USB transfer
speed. With this change, the USB transfer speed can be doubled to 20MB/s.

For Linux, adjust the max bulk size to 16384 to maximize the USB transfer
speed according to MAX_USBFS_BUFFER_SIZE definition in drivers/usb/core/devio.c.

For OSX, the maxLenToSend is already 1MB in code.

Change-Id: If6af8c6301f6f6c2ef345e37241706f16d8f5cda
931bdcc09a3d805cf25033951adb95c8e5159e46 01-Jul-2010 Werner Johansson <werner.johansson@sonyericsson.com> Set explicit timeout on USB control transfer

This attempts to solve the intermittent issues with serial number
showing up as all question marks when issuing "fastboot devices"
c500be926cf07c43aeb828ae86b04b856c6b7c63 08-Oct-2009 Elliott Hughes <enh@google.com> Fix flashstation breakage.

We need to reset 'writable' each time round the loop (i.e. for each device).
b4add9b74525210478bac702d27fdaf9cf7ab18f 07-Oct-2009 Elliott Hughes <enh@google.com> Make fastboot say "no permissions" for non-writable devices.

Without this patch, "adb devices" will say "no permissions" when it sees
a device it can't write to, but "fastboot devices" will silently ignore it.
This is confusing to n00bs, especially since it doesn't seem to be widely
known that a device's USB id might be different in the bootloader (meaning
two udev rules are needed). It can also be confusing if you're sshed in,
when you can't access the device because you won't be in the "plugdev"
group, but "fastboot devices" won't make this clear.

I'm not sure about the Mac OS and Windows changes. AIUI, devices are always
writable on those platforms, but I don't use either, so I can't test this.
This patch shouldn't alter the behavior on either of those platforms.
b2de4db941f5329f9f19e70feff5786b2d5acbb6 18-Aug-2009 Dan Murphy <D.Murphy@motorola.com> fastboot: Add retry to USB read call.

If the USB connection to the device is reset but is still there
the code should retry to re-connect the device and continue.

This is a short term fix for a bootloader issue.
We should revisit and look for a better solution.

Signed-off-by: Dan Murphy <D.Murphy@motorola.com>
Signed-off-by: Mike Lockwood <lockwood@android.com>
dd7bc3319deb2b77c5d07a51b7d6cd7e11b5beb0 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
e54eebbf1a908d65ee8cf80bab62821c05666d70 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
4f6e8d7a00cbeda1e70cc15be9c4af1018bdad53 21-Oct-2008 The Android Open Source Project <initial-contribution@android.com> Initial Contribution