[U-Boot] [PATCH] doc: Move fastboot protocol doc to android dir
Signed-off-by: Sam Protsenko semen.protsenko@linaro.org --- .../fastboot-protocol.txt} | 0 doc/android/fastboot.txt | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) rename doc/{README.android-fastboot-protocol => android/fastboot-protocol.txt} (100%)
diff --git a/doc/README.android-fastboot-protocol b/doc/android/fastboot-protocol.txt similarity index 100% rename from doc/README.android-fastboot-protocol rename to doc/android/fastboot-protocol.txt diff --git a/doc/android/fastboot.txt b/doc/android/fastboot.txt index ce852a4fd1..e774c66f56 100644 --- a/doc/android/fastboot.txt +++ b/doc/android/fastboot.txt @@ -5,8 +5,8 @@ Android Fastboot Overview ========
-The protocol that is used over USB and UDP is described in the -``README.android-fastboot-protocol`` file in the same directory. +The protocol that is used over USB and UDP is described in +``doc/android/fastboot-protocol.txt``.
The current implementation supports the following standard commands:
On Tue, Jul 02, 2019 at 09:14:57PM +0300, Sam Protsenko wrote:
Signed-off-by: Sam Protsenko semen.protsenko@linaro.org
Applied to u-boot/master, thanks!
Hi Sam,
On Thu, Jul 18, 2019 at 07:57:45PM -0400, Tom Rini wrote:
On Tue, Jul 02, 2019 at 09:14:57PM +0300, Sam Protsenko wrote:
Signed-off-by: Sam Protsenko semen.protsenko@linaro.org
Applied to u-boot/master, thanks!
This recent merge introduced a conflict when applying [1] to master. Are you aware of any other patches which would conflict with [1]? If not, I would proceed with sending a v3. TIA.
[1] https://patchwork.ozlabs.org/cover/1131356/ ("[U-Boot,v2,0/5] Fixes and improvements in BCB and Android docs")
Hi Eugeniu,
On Fri, Jul 19, 2019 at 12:12 PM Eugeniu Rosca roscaeugeniu@gmail.com wrote:
Hi Sam,
On Thu, Jul 18, 2019 at 07:57:45PM -0400, Tom Rini wrote:
On Tue, Jul 02, 2019 at 09:14:57PM +0300, Sam Protsenko wrote:
Signed-off-by: Sam Protsenko semen.protsenko@linaro.org
Applied to u-boot/master, thanks!
This recent merge introduced a conflict when applying [1] to master. Are you aware of any other patches which would conflict with [1]? If not, I would proceed with sending a v3. TIA.
Yeah, I forgot about it, sorry. No other conflicting patches pending. You can check my android-next branch [1] to check all patches I collected for sending (and my current work on top of it).
[1] https://github.com/joe-skb7/u-boot-misc/commits/android-next
[1] https://patchwork.ozlabs.org/cover/1131356/ ("[U-Boot,v2,0/5] Fixes and improvements in BCB and Android docs") -- Best Regards, Eugeniu.
On Fri, Jul 19, 2019 at 05:36:14PM +0300, Sam Protsenko wrote:
You can check my android-next branch [1] to check all patches I collected for sending (and my current work on top of it).
[1] https://github.com/joe-skb7/u-boot-misc/commits/android-next
It looks like we'll be able to dump the contents and fetch the meta-information of boot.img in the nearest future. Very cool. Thanks for the efforts.
On Sat, Jul 20, 2019 at 12:45 AM Eugeniu Rosca roscaeugeniu@gmail.com wrote:
On Fri, Jul 19, 2019 at 05:36:14PM +0300, Sam Protsenko wrote:
You can check my android-next branch [1] to check all patches I collected for sending (and my current work on top of it).
[1] https://github.com/joe-skb7/u-boot-misc/commits/android-next
It looks like we'll be able to dump the contents and fetch the meta-information of boot.img in the nearest future. Very cool. Thanks for the efforts.
Actually we are already able to dump the contents of image using "iminfo" command (once boot image is loaded to $loadaddr). But yeah, I'm basically trying to implement new boot scheme, for Android Boot Image v2. Not sure if I'll be in time before merge window closes, though. So it will be probably posted for next merge window, along with other boot flow stuff.
-- Best Regards, Eugeniu.
participants (3)
-
Eugeniu Rosca -
Sam Protsenko -
Tom Rini