From: Pavel Machek <pavel@ucw.cz>
To: Arve Hj?nnev?g <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Brian Swetland <swetland@google.com>
Subject: Re: dream: fastboot getting protocol errors
Date: Mon, 9 Nov 2009 11:42:54 +0100 [thread overview]
Message-ID: <20091109104254.GA8757@elf.ucw.cz> (raw)
In-Reply-To: <20091109103602.GC2207@elf.ucw.cz>
On Mon 2009-11-09 11:36:02, Pavel Machek wrote:
> Hi!
>
> I'm still fighting with porting MMC support to current mainline.
>
> Meanwhile: I'm getting this *way* too often -- with the htcUSB to
> 2xUSB reduction. Any ideas?
>
> root@amd:/data/l/android# ./fastboot -c "console=tty0
> root=/dev/mmcblk0p1 rootdelay=5 fbcon=rotate:1" boot
> /data/l/linux-msm/arch/arm/boot/zImage
> creating boot image...
> creating boot image - 1667072 bytes
> downloading 'boot.img'... FAILED (command write failed (Protocol
> error))
> root@amd:/data/l/android#
>
> ...and then it just goes away after powercycling the phone...
And this is another failure mode: display says "FASTBOOT", and serial
console says
UART0:Cmd>szCPLDstrlen=0x5
+usbloader_init
-usbloader_init
(but no message about usb highspeed mode), and fastboot hangs with
root@amd:/data/l/android# ./fastboot -c "console=tty0
root=/dev/mmcblk0p1 rootdelay=5 fbcon=rotate:1" boot
/data/l/linux-dream-mainline/arch/arm/boot/zImage
creating boot image...
creating boot image - 1421312 bytes
< waiting for device >
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-11-09 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 10:36 dream: fastboot getting protocol errors Pavel Machek
2009-11-09 10:42 ` Pavel Machek [this message]
2009-11-09 12:59 ` Brian Swetland
2009-11-09 13:13 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091109104254.GA8757@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arve@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox