| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
downloads"
* commit 'c4eaebbe7a0c125663f74e3961b62de8d3611a51':
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is needed for products like xoom-cdma and xoom-cdma-lte.
The xoom-cdma-lte product requires an lte baseband binary but
it's not needed for xoom-cdma.
This is implemented by allowing an optional product parameter
to "required" statements. The parameter is separated from
"required" by a colon so the version-baseband-2 requirment in
board-info.txt for stingray becomes:
require-for-product:xoom-cdma-lte version-baseband-2=ltedc_u_03.25.00|ltedc_u_03.19.00
In the above statement, only xoom-cdma-lte requires version-baseband-2
and the baseband can be lte_u_03.25.00 or lte_u_03.19.00. For other
products version-baseband-2 will be ignored.
Change-Id: I786bec5f5661c2243d87925b064fc6124d3cffa1
|
| |
| |
| |
| | |
Change-Id: I89d4a6d14e542d8f2d7832d94b0a7cee6eb88305
|
| |
| |
| |
| | |
Change-Id: I350feab372e105755509c81604d57b2de1a69163
|
|\ \
| |/
| |
| |
| | |
* commit 'f1c2a7352f19cf729f91bf2559fc93ef12c74dca':
fastboot: Add help message for continue command
|
| |
| |
| |
| |
| | |
Change-Id: I578b1b7c2d74d09d44ce9100bfe582aaa25c31b1
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
|
| |
| |
| |
| | |
Change-Id: I665572a2212f1239b02b7816e37ada210afbdb48
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '42b871f1bfc116d53d1bff9d7497415494b2e0e0'
* commit '42b871f1bfc116d53d1bff9d7497415494b2e0e0':
Check fastboot oem command line length
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Merge commit 'c37ba1c916d73fbf35c6faba1e252e2916d2d41d' into gingerbread-plus-aosp
* commit 'c37ba1c916d73fbf35c6faba1e252e2916d2d41d':
Check fastboot oem command line length
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I301af09c4ec460c9049b75cc7f4d2c50cfe00ceb
Signed-off-by: Bruce Beare <brucex.j.beare@intel.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ClearPipeStallBothEnds() appears to fail on some devices, but if we ignore
that error then fastboot does work. So ignore the error.
Change-Id: Ic866ece28a57c081e34079e1a032fa8155301ddf
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
bootloader chatter
Merge commit 'beb72464ff8c501597cd7e098090f7d131dc5ccb'
* commit 'beb72464ff8c501597cd7e098090f7d131dc5ccb':
fastboot: make it so I can actually see the bootloader chatter
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- prefix bootloader messages with (bootloader)
- remove the fancy right justified no newline business
Change-Id: Ica16ebe6a25971db423c5db06300a280d93faf3e
Signed-off-by: Brian Swetland <swetland@google.com>
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
Merge commit 'a8c7404956b4370162a87ae09b851266a4933b54'
* commit 'a8c7404956b4370162a87ae09b851266a4933b54':
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"
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The kernel panic seems to be related to the driver trying to allocate
too many pages from the IO mapper. That may be caused by the fact
that we try to perform a 100+ MiB transfer in a single IO operation.
This change breaks the transfer down into 1 MiB chunks.
So far after a day of testing, no kernel panics have occurred compared
to 5 in the previous 24 hours!
Change-Id: I8d27a546e0c0bf4fe2f0fc7fcad65a88d3e6bee0
|
|\ \ \
| |/ / |
|
| |/
| |
| |
| |
| | |
Change-Id: Ied48302b50412f27dcf49d40913e4b900f3bd153
Signed-off-by: Dima Zavin <dima@android.com>
|
| |
| |
| |
| |
| |
| | |
(Merged from master Change I3d0e4cab)
Change-Id: Ib3fd566bdaf09d5893a6b0c66168c76c6b0d92eb
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When using fastboot in scripts, it currently is necessary to parse the
output for FAILED messages and possible other indications of
error. This happens relatively often, for example when there are radio
update issues. Fortunately, fb_execute_queue already has a notion that
an error has occured which is used to abort the queue execution.
This change makes the status value be returned from fb_execute_queue
to main which can then return it as an exit status. usage cases were
also changed to return 1.
Note the code already returned 1 for error in one other case when
there was a problem with boot, so there is a precedent for return 1 on
error in this program.
Change-Id: Ib0463b08c8f2569495e248dd84e331f7e3691039
|
|/
|
|
| |
Change-Id: I3d0e4cabd65d9de17036901a22ec3277a6d58e64
|
|
|
|
|
|
| |
(For diagnosing slow flashes.)
Change-Id: Ibbcbd080db551c8590ca8bfe50e9ddb45eea5661
|
|
|
|
|
| |
Change-Id: I07451363f4d4ac8665598722491968e6ee0953ee
Signed-off-by: Dima Zavin <dima@android.com>
|
|\
| |
| |
| | |
Change-Id: I187f29848c223c8c548323e0fa20ea0f3b8a3909
|
| |\ |
|
| | |
| | |
| | |
| | | |
Change-Id: I1d88d2a8b3f5c0a9bade2a207b5d9c5a0b776655
|
| |\ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Erik Gilling <konkers@android.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge commit 'ef063fe3066153dab5389b6baba6cb4e36888106'
* commit 'ef063fe3066153dab5389b6baba6cb4e36888106':
Add support for Acer devices
FreeBSD support for usb-connected devices in adb
Make get_my_path() safer
Fix use of memset function
|
| |\ \ \
| | |/ /
| |/| /
| | |/ |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Add adb's ANDROID_SERIAL to fastboot too.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We noticed this when trying to script on-device testing for the dalvik
continuous build.
Also fix a typo in adb's help.
|
|/ / /
| | |
| | |
| | | |
We need to reset 'writable' each time round the loop (i.e. for each device).
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|/ |
|
|
|
|
| |
Signed-off-by: Dima Zavin <dima@android.com>
|
|
|
|
|
|
|
| |
Add the --base flag to mkbootimg and -b flag to fastboot, to allow
the default kernel base address (0x10000000) to be changed.
Signed-off-by: Brian Swetland <swetland@google.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|