[PATCH 1/1] uboot-pcf50633-default-curr-lim-1A.patch

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
> On Thu, Feb 21, 2008 at 08:35:56PM +0800, Werner Almesberger wrote:
>> Harald Welte wrote:
>>> I think this is what I would call a serioous 'quality of implementation
>>> issue'.
>> Don't worry, nobody has any plans to ship devices with that sort
>> of evilness.
> 
> ok, great. thanks :)  sorry if that was a misunderstanding on my part.

Actually I would ship the thing pulling a fixed 500mA perfectly happily.
 But it happens this is likely sufficiently easy to fix it'll get done
beforehand.

This issue takes its place amongst a pretty large number of major things
that it would be good to fix before ship.  If there's time for
everything then great, if there isn't then really only the ones that
cannot be fixed post-ship have the full call to hold the thing up.  It
means we should focus on the ones that MUST be fixed pre-ship first
which we have been doing for some time.  You consider this one of those
but against the full spread of deficits, I don't.

The people in control of when to press the build and ship button (not
you, Werner or myself) have a good clear grip on the spread of issues
and since its their money they get to decide when it balances out.

On why support for no-battery is important now, it is so the usage case
is continuously tested against regressions now we have it working to the
rule it does.  Until recently, the battery case was not actually being
tested at all -- now that's a "MUST".

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHvY+COjLpvpq7dMoRAgncAKCP2kQQKtTDHPtoIz94YABTNMzRxACfd3fn
wO4N8cC0qhLz06/zMnRksEc=
=GnVQ
-----END PGP SIGNATURE-----