From: Pantelis Antoniou <panto@intracom.gr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Kumar Gala <kumar.gala@motorola.com>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] Take two of the new serial uart driver.
Date: Mon, 07 Jun 2004 11:53:36 +0300 [thread overview]
Message-ID: <40C42D10.5030308@intracom.gr> (raw)
In-Reply-To: <1086598392.29255.15.camel@localhost.localdomain>
David Woodhouse wrote:
>On Mon, 2004-06-07 at 11:34 +0300, Pantelis Antoniou wrote:
>
>>Hmm, just multiply by 3 in udelay instead of 2.
>>
>>What is your baud rate? 9600?
>>
>
>Yeah. Why must we pick numbers out of the air instead of actually
>waiting for the hardware to say it's finished?
>
>
Actually I didn't pick it out of thin air.
It is mentioned in the manual that you must wait
two character times for the HW fifo to drain.
There is no hardware event bit for FIFO empty.
It's just that the udelay call is not really exact.
So +1 and we're all OK! :)
So did it work now?
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-07 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 14:13 [PATCH] Take two of the new serial uart driver Pantelis Antoniou
2004-06-03 16:21 ` David Woodhouse
2004-06-04 6:31 ` Pantelis Antoniou
2004-06-05 9:12 ` David Woodhouse
2004-06-05 19:22 ` Tom Rini
2004-06-05 22:02 ` David Woodhouse
2004-06-06 1:30 ` Tom Rini
2004-06-07 8:11 ` Pantelis Antoniou
2004-06-07 8:36 ` David Woodhouse
2004-06-07 8:34 ` Pantelis Antoniou
2004-06-07 8:53 ` David Woodhouse
2004-06-07 8:53 ` Pantelis Antoniou [this message]
2004-06-07 9:06 ` David Woodhouse
2004-06-07 9:12 ` David Woodhouse
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=40C42D10.5030308@intracom.gr \
--to=panto@intracom.gr \
--cc=dwmw2@infradead.org \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).