From: Peter Maydell <peter.maydell@linaro.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: Rajath Shashidhara <rajaths@cs.utexas.edu>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Looking for issues/features for my first contribution
Date: Sat, 9 Nov 2019 16:01:16 +0000 [thread overview]
Message-ID: <CAFEAcA-tNBNGE75+MZ3+r_9iLA-_3+meoseVxhgzJZ5PvDofuA@mail.gmail.com> (raw)
In-Reply-To: <CAL1e-=hcS8_2Y1YJS01GTwFbMYBJmWopYkSDi_aw6yzOHk=3Lg@mail.gmail.com>
On Fri, 8 Nov 2019 at 19:32, Aleksandar Markovic
<aleksandar.m.mail@gmail.com> wrote:
>
> > [a] Is there any particular reason that you picked DS3231 ? Linux kernel
> > has drivers for DS3232/34 only [1]. I did read the datasheets of both
> > 3232 & 3231 and found that they are quite similar except for the 236
> > bytes of SRAM support found only in 3232.
> >
>
> Yes, DS3231 is a part of a board we want to support in future.
We should probably prefer to go with a device that's a
missing part of a board we already support -- generally
the project prefers not to take device models that don't
have a use, ie they go in with the board model rather
than before. This also means we have some way of testing
the code :-)
thanks
-- PMM
next prev parent reply other threads:[~2019-11-09 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 23:50 Looking for issues/features for my first contribution Rajath Shashidhara
2019-11-07 10:37 ` Aleksandar Markovic
2019-11-07 13:33 ` Aleksandar Markovic
2019-11-07 18:49 ` Rajath Shashidhara
2019-11-08 2:39 ` Rajath Shashidhara
2019-11-08 9:08 ` Alex Bennée
2019-11-08 13:05 ` Richard Henderson
2019-11-08 19:31 ` Aleksandar Markovic
2019-11-09 16:01 ` Peter Maydell [this message]
2019-11-09 21:08 ` Aleksandar Markovic
2019-11-10 14:33 ` Peter Maydell
2019-11-08 19:36 ` Aleksandar Markovic
2019-11-08 21:54 ` BALATON Zoltan
2019-11-09 19:46 ` Aleksandar Markovic
2019-11-09 21:33 ` Rajath Shashidhara
2019-11-09 23:55 ` Aleksandar Markovic
2019-11-07 11:18 ` Alex Bennée
2019-11-07 13:54 ` Stefan Hajnoczi
2019-11-07 18:51 ` Rajath Shashidhara
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=CAFEAcA-tNBNGE75+MZ3+r_9iLA-_3+meoseVxhgzJZ5PvDofuA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rajaths@cs.utexas.edu \
/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).