[gta04] Meeting minutes for GTA04 discussion 20080411

Andy Green andy at openmoko.com
Mon Apr 14 21:36:53 CEST 2008

Hash: SHA1

Somebody in the thread at some point said:
| On Mon, Apr 14, 2008 at 07:10:11PM +0100, Andy Green wrote:
|> | At least in GTA01/02, the issue is also that the CPU has to receive
|> | things on the UART, so almost no dead time is allowed. This may be
|> | similar also in GTA04, just with protocols that aren't quite as easy to
|> | handle as UART (which the MPU could do just fine, of course).
|> I'm not sure this is the case.  When I asked Erin and Sean Chiang about
|> this they made it sound like the CPU is polling for status, not waiting
|> for async response.  And that fits what I understood about the +++AT
|> - -based command set of these things.  In that case, we are just
|> periodically waking and polling from CPU and there is no issue.
| please dont' try to design hardware fixes for something that sounds like
| a software design or implementaiton problem (polling an UART for data)

Could you elaborate a bit?  Polling the module at all during a call is
bad news?  If so, what is the better way to find out about other side
ending the call, etc.

I'm asking from the point of view to see how to best keep the CPU down
during the call.

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


More information about the openmoko-kernel mailing list