From: Rodolfo Giometti <giometti@enneenne.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PXA27x usbtty start up sequence
Date: Sun, 20 May 2007 18:07:02 +0200 [thread overview]
Message-ID: <20070520160702.GB3887@enneenne.com> (raw)
In-Reply-To: <20070520145436.180807c6@localhost.localdomain>
On Sun, May 20, 2007 at 02:54:36PM +0100, Bryan O'Donoghue wrote:
> That's really quite odd. The following should be similar to what you
> did and it *does* seem to work just fine, for me.
I find the problem.
It's into usbtty_poll() which calls write_buffer() when the USB device
get connected (usbtty_configured() is true).
Function write_buffer() calls udc_endpoint_write() who calls driver
low level function. This low level function, PXA270 specific, waits
all data has been transmitted before returning to the caller, this
because I need to know when a packet has been transmetted before
sending a new one or I get some data lost during transmission.
When I connect kermit/minicom to /dev/USB0 the UDC sends stdout data
and everything works well...
How I can resolve the problem? Maybe using a timeout during
transmission?
Thanks,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at gnudd.com
Embedded Systems giometti at linux.it
UNIX programming phone: +39 349 2432127
next prev parent reply other threads:[~2007-05-20 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 23:19 [U-Boot-Users] PXA27x usbtty start up sequence Rodolfo Giometti
2007-05-13 12:25 ` Bryan O'Donoghue
2007-05-14 6:35 ` Rodolfo Giometti
2007-05-18 17:15 ` Rodolfo Giometti
2007-05-20 13:54 ` Bryan O'Donoghue
2007-05-20 16:07 ` Rodolfo Giometti [this message]
2007-05-20 21:40 ` Bryan O'Donoghue
2007-05-20 22:23 ` Rodolfo Giometti
2007-05-20 23:11 ` Bryan O'Donoghue
2007-05-20 23:59 ` Bryan O'Donoghue
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=20070520160702.GB3887@enneenne.com \
--to=giometti@enneenne.com \
--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