From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755872AbZKINNn (ORCPT ); Mon, 9 Nov 2009 08:13:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755827AbZKINNn (ORCPT ); Mon, 9 Nov 2009 08:13:43 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:50730 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755828AbZKINNm (ORCPT ); Mon, 9 Nov 2009 08:13:42 -0500 Date: Mon, 9 Nov 2009 14:13:41 +0100 From: Pavel Machek To: Brian Swetland Cc: Arve Hj?nnev?g , kernel list , linux-arm-kernel Subject: Re: dream: fastboot getting protocol errors Message-ID: <20091109131340.GB23292@elf.ucw.cz> References: <20091109103602.GC2207@elf.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 2009-11-09 04:59:10, Brian Swetland wrote: > On Mon, Nov 9, 2009 at 2:36 AM, 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... > > Unfortunately, I think that's just flakies in the htc bootloader. I'm > not aware of any simple workaround. Do you not see it fail if you use > a straight USB A->miniB cable? No, that seems to work reliably. > I think that bootloader will still honor a secondstage bootloader > embedded in the boot.img (mkbootimg --second foo), or you could > replace the zimage in the boot.img with a second stage bootloader. > Either way, dunno if you want to dig into bootloader hackery to try to > resolve usb issues. Ok, so its time to simply retry until it works... Thanks for info! Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html