From: Bryan O'Donoghue <bodonoghue@codehermit.ie>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PXA27x usbtty start up sequence
Date: Sun, 13 May 2007 13:25:36 +0100 [thread overview]
Message-ID: <20070513132536.6ab397df@localhost.localdomain> (raw)
In-Reply-To: <20070512231906.GG11070@enneenne.com>
On Sun, 13 May 2007 01:19:07 +0200
Rodolfo Giometti <giometti@enneenne.com> wrote:
> Using serial console with a bootdelay of only 1 second is ok, but
> using usbtty is not. In fact is not possible to stop boot sequence
> anymore unless bootdelay is increased at least 10-15 seconds needed
> to run the terminal on the new ttyUSB0 device and to enter the
> password.
>
> Also I notice that when usbtty is selected as the default console
> the system doesn't start up until I connect the kermit/minicom to
> the new ttyUSB0 device.
Hmm, you might want to change
unsigned int len = 0;
while(len > 0) {
usbtty_poll();
space = maxlen - usbtty_output.size;
if(space){
/* Do stuff */
}
}
to
/* Not tested */
unsigned int len = 0;
while(len > 0) {
usbtty_poll();
/* Do stuff */
}
in __usbtty_puts()
puts() I guess _should_ be a 'best effort'. Better, still, maybe
we could add an environment variable which would switch puts()
between flow-control and 'best effort', so that people have the
choice.
/* Not tested */
unsigned int len = 0;
while(len > 0) {
usbtty_poll();
space = maxlen;
if(environment_variable_use_tty_flow_control)
space = maxlen - usbtty_output.size;
if(space){
/* Do stuff */
}
}
Bryan
next prev parent reply other threads:[~2007-05-13 12:25 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 [this message]
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
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=20070513132536.6ab397df@localhost.localdomain \
--to=bodonoghue@codehermit.ie \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.