[maemo-developers] [maemo-developers] Unresolved issues (Week 43)

From: Komal Shah komal_shah802003 at yahoo.com
Date: Mon Oct 30 14:48:08 EET 2006
--- Tommi Komulainen <tommi.komulainen at nokia.com> wrote:

> Here is a list of issues raised on this list I think have not been
> concluded so far, in no particular order. The easiest way to get off
> the
> list is to provide answers, but you can also try convincing me other
> ways. 
> This is an attempt to improve our communication by providing a short
> summary reminder for busy people to act on. I'll try to keep up with
> the
> experiment for a few weeks and see what happens.
> The list is getting huge. Please help us out by answering to the
> questions.


>       *
> http://maemo.org/pipermail/maemo-developers/2006-October/005813.html
>         Maemo and Ubuntu Edgy: Is it safe?
>         (USB API changed in Edgy. As a result the flasher stopped
>         working.)
>         2nd mention
>         "Why is the flasher not open source?"
>       *

Let me answer this, based on my understanding with OMAP1/2, eventhough
I am not the developer of flasher.

What flasher tries to do is to establish USB level communication with
the hardware/OMAP1 chip and can do cold flash, when the device has
nothing on it. At this time it has to use ROM code (might be
properitery by Texas Instruments), for establishing USB level
communication details. 

So, in the Linux-OMAP community we have not seen bootloaders/utilities,
which does the (cold)flashing using USB link. For TI developed EVMs, it
provides Win32 binary only utilities like CSST to flash the
signed/unsigned images (like u-boot image) using serial port or USB as
a medium of transfer.

---Komal Shah

Want to start your own business? Learn how on Yahoo! Small Business 

More information about the maemo-developers mailing list