| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
- prefix bootloader messages with (bootloader)
- remove the fancy right justified no newline business
Change-Id: Ica16ebe6a25971db423c5db06300a280d93faf3e
Signed-off-by: Brian Swetland <swetland@google.com>
|
| |
| |
| |
| |
| | |
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
|
|
|
|
|
|
| |
(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>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|