public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Pete Batard <pete@akeo.ie>
Subject: Re: [PATCH edk2-platforms] Silicon/Bcm2836: add random number generator driver
Date: Fri, 1 Feb 2019 10:33:15 +0100	[thread overview]
Message-ID: <CAKv+Gu_1Tnqg-Eeqp=AWTpvV97TBsh5Bu=5QxNTdaYuULkq9JA@mail.gmail.com> (raw)
In-Reply-To: <20190131183503.tjujxj2anjewsyh6@bivouac.eciton.net>

On Thu, 31 Jan 2019 at 19:35, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Thu, Jan 31, 2019 at 06:14:45PM +0100, Ard Biesheuvel wrote:
> > On Thu, 31 Jan 2019 at 16:05, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> > >
> > > On Wed, Jan 30, 2019 at 08:39:43PM +0100, Ard Biesheuvel wrote:
> > > > Expose the SoC's RNG peripheral via the EFI_RNG_PROTOCOL.
> > > > This is used by Linux to seed the KASLR routines.
> > > >
> > > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > >
> > > Not tested, but looks fine. Only question: could we add those few
> > > #defines to IndustryStandard/Bcm2836.h (should that really be
> > > #IndustryStandard, btw?) rather than creating a tiny standalone one?
> > > (more below)
> > >
> >
> > Sure.
> >
> > Re IndustryStandard/, I deliberately chose something idiomatic for
> > EDK2, and this is the least inappropriate one. I could live with
> > Chipset/ as well, but dumping headers under Include/ directly is not
> > the solution IMO.
>
> I disagree. Dumping the main SoC header under the top-level SoC
> directory (and same pattern for platform) is idiomatic.
> Dumping all kinds of random files there isn't, I agree (although that
> happens too).
>
> BeagleBoardPkg/Include/BeagleBoard.h
> OvmfPkg/Include/OvmfPlatforms.h
> Vlv2TbltDevicePkg/Include/Platform.h
>
> Silicon/Hisilicon/Hi6220/Include/Hi6220.h
>
> An alternative pattern is an include directory named after the
> SoC/Platform.
>
> Omap35xxPkg/Include/Omap3530/
>
> You used
>
> Silicon/Socionext/SynQuacer/Include/Platform/
>
> which I also don't mind.
>
> If you'd prefer it, I'd be happy with Platform/ and Silicon/.
>
> But we'd better settle on something before Pete changes too much based
> on my feedback.
>

Yeah. I'll park this until Pete's stuff is merged.


      reply	other threads:[~2019-02-01  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 19:39 [PATCH edk2-platforms] Silicon/Bcm2836: add random number generator driver Ard Biesheuvel
2019-01-31 15:05 ` Leif Lindholm
2019-01-31 17:14   ` Ard Biesheuvel
2019-01-31 18:35     ` Leif Lindholm
2019-02-01  9:33       ` Ard Biesheuvel [this message]

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-list 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='CAKv+Gu_1Tnqg-Eeqp=AWTpvV97TBsh5Bu=5QxNTdaYuULkq9JA@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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