public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Debugging, Why USB is not stable
Date: Wed, 01 Sep 2010 17:15:56 +0200	[thread overview]
Message-ID: <m2tym9cx5f.fsf@ohwell.denx.de> (raw)
In-Reply-To: <AANLkTim46eoOsfNKXXP0x44bnwrU6yHS5tGVBsgjOA0r@mail.gmail.com> (Remy Bohmer's message of "Tue, 31 Aug 2010 20:12:37 +0200")

Hi Remy,

>> Only the fact that USB is a nightmare to work with. ?No, honestly, we
>> have a continuous stream of USB related problems with the current USB
>> code.
>
> This is not what I notice on the amount of fixes that are posted on the list...

Most problems go without a fix if there is an easy hardware replacement.
Even diagnosing such a problem is usually too expensive for customers.

> The only fixes I have seen the last year or two were related to newly
> added host-controller support. Apart from that it is quite silent in
> the u-boot-usb tree...
> But, anyway. I know it has some stability issues, although it is now
> much better compared to a year ago...

Yes it is and without a question I greatly appreciate your work for the
USB part.

>>?As I understand it this results from the ever more diverging USB
>> implementation in U-Boot and e.g. in the Linux kernel.
>
> Indeed, It has diverged that much that I did not succeed in finding
> the real origin of the code...
>
>> Sometimes I get the impression that we would save a lot of headache by
>> starting afresh and porting the current Linux code into U-Boot thus
>> leverage all this, but nobody yet dared to start such a feat.
>
> Hey... I have dared to start it!
> (But it is a real pain to do it properly, and I stopped half way due
> to lack of time...)

I can understand that also.  My intention of the mail was to transport
my personal view of the whole area.  USB problems in my experience have
a very high cost even to diagnose, let alone fix.

Cheers
  Detlev

-- 
Test applications  with a variety of tools.  Don't assume everything works if
you've tested  with only  one client.  Also, assume the low end of technology
for clients and don't create applications which can only be used by Graphical
User Interfaces.                                       -- RFC 1855
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

      reply	other threads:[~2010-09-01 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 23:12 [U-Boot] Debugging, Why USB is not stable Gérald Kerma
2010-08-30  9:12 ` Detlev Zundel
2010-08-30  9:37   ` Bas Mevissen
2010-08-30  9:52     ` Detlev Zundel
2010-08-30 10:13       ` Bas Mevissen
2010-08-30 10:20         ` Detlev Zundel
2010-08-31 18:12   ` Remy Bohmer
2010-09-01 15:15     ` Detlev Zundel [this message]

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=m2tym9cx5f.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=u-boot@lists.denx.de \
    /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