From: Antony Pavlov <antonynpavlov@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC v4 4/5] hw/arm/digic: add UART support
Date: Fri, 6 Sep 2013 17:00:15 +0400 [thread overview]
Message-ID: <20130906170015.9d069ef890a2631a2edf543e@gmail.com> (raw)
In-Reply-To: <CAFEAcA-F15J_QsWUVYLnk1A3Q_67oCR1QNNU6QM7EyyckysUVQ@mail.gmail.com>
On Fri, 6 Sep 2013 08:25:20 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 6 September 2013 07:54, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> > On Thu, 5 Sep 2013 19:17:50 +0100
> > Peter Maydell <peter.maydell@linaro.org> wrote:
> >> Does this UART really not have a FIFO?
> >
> > There is no public documentation on Digic chips.
> > Only Canon's engineers know something about Digic's FIFO (if it exists :).
>
> You can deduce its existence though -- does the
> UART let you feed two or three characters to it
> at faster than whatever the serial line speed is
> before it sets the "stop sending me bits" status
> bit, or does it stop after the first?
No, I can't :)
How can I check this mysterious "stop sending me bits" status bit?
Do you mean the UART hardware flow control pin?
I can't use hardware flow control as I have only 3-wire UART on the camera.
Moreover I have to enable hardware flow control in software, but I have
no information how to do it.
> If the real firmware uses this for anything remotely
> serious (ie for more than trivial and default-disabled
> debug info) it probably does have a FIFO. However,
> let's assume it doesn't for now.
>
> -- PMM
--
--
Best regards,
Antony Pavlov
next prev parent reply other threads:[~2013-09-06 13:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 7:52 [Qemu-devel] [RFC v4 0/5] hw/arm: add initial support for Canon DIGIC SoC Antony Pavlov
2013-09-05 7:52 ` [Qemu-devel] [RFC v4 1/5] hw/arm: add very " Antony Pavlov
2013-09-05 18:08 ` Andreas Färber
2013-09-05 21:23 ` Antony Pavlov
2013-09-05 21:38 ` Andreas Färber
2013-09-06 5:01 ` Antony Pavlov
2013-09-05 7:52 ` [Qemu-devel] [RFC v4 2/5] hw/arm/digic: prepare DIGIC-based boards support Antony Pavlov
2013-09-05 17:54 ` Peter Maydell
2013-09-06 7:12 ` Antony Pavlov
2013-09-05 7:52 ` [Qemu-devel] [RFC v4 3/5] hw/arm/digic: add timer support Antony Pavlov
2013-09-05 7:52 ` [Qemu-devel] [RFC v4 4/5] hw/arm/digic: add UART support Antony Pavlov
2013-09-05 18:17 ` Peter Maydell
2013-09-06 6:54 ` Antony Pavlov
2013-09-06 7:25 ` Peter Maydell
2013-09-06 13:00 ` Antony Pavlov [this message]
2013-09-06 13:40 ` Peter Maydell
2013-09-07 5:45 ` Antony Pavlov
2013-09-07 8:33 ` Peter Maydell
2013-09-05 7:52 ` [Qemu-devel] [RFC v4 5/5] hw/arm/digic: add NOR ROM support Antony Pavlov
2013-09-05 18:19 ` Peter Maydell
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=20130906170015.9d069ef890a2631a2edf543e@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).