From: P J P <ppandit@redhat.com>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>, Huawei PSIRT <psirt@huawei.com>,
Qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] char: cadence: check divider against baud rate
Date: Thu, 20 Oct 2016 11:25:47 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1610201116520.27908@wniryva> (raw)
In-Reply-To: <CAKmqyKMLvYDTvofMF=5k2sYNKPS+HtWYvz6RCdsd4AQG97H6nQ@mail.gmail.com>
+-- On Wed, 19 Oct 2016, Alistair Francis wrote --+
| I don't think the Cadence datasheets are public. If you can't find it
| from a simple Google search I don't think you have access.
I see, okay.
I think it'll greatly help if device emulator writers include a link to its
specification/datasheet resources in the respective source file. At least if
these are publicly available. That way one knows for sure which specifications
to follow while debugging, instead of searching and sifting through multiple
different versions. OR Maybe there could a field in the MAINTAINERS file which
would point to respective reference resources. (just a thought)
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-10-20 5:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 9:47 [Qemu-devel] [PATCH] char: cadence: check divider against baud rate P J P
2016-10-18 9:50 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2016-10-18 18:46 ` P J P
2016-10-19 9:49 ` Alistair Francis
2016-10-19 10:11 ` P J P
2016-10-19 13:42 ` Alistair Francis
2016-10-20 5:55 ` P J P [this message]
2016-10-20 17:21 ` Edgar E. Iglesias
2016-10-21 7:47 ` P J P
2016-10-24 7:46 ` Alistair Francis
2016-10-24 13:25 ` P J P
2016-10-25 0:28 ` Alistair Francis
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=alpine.LFD.2.20.1610201116520.27908@wniryva \
--to=ppandit@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=psirt@huawei.com \
--cc=qemu-arm@nongnu.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).