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-groups-io <devel@edk2.groups.io>,
	Jagadeesh Ujja <jagadeesh.ujja@arm.com>,
	 Thomas Panakamattam Abraham <thomas.abraham@arm.com>
Subject: Re: [edk2-devel] [edk2] [PATCH v2 edk2-platforms] Platform/ARM/Drivers: Add Nor Flash Driver
Date: Mon, 29 Apr 2019 10:17:17 +0200	[thread overview]
Message-ID: <CAKv+Gu-kFo7DH+n=KR-CJR8ibbZ3wdmS=Z+RZw=wJhgCpYd9eA@mail.gmail.com> (raw)
In-Reply-To: <20190429075816.y4gyeyqt4kp7lffk@bivouac.eciton.net>

On Mon, 29 Apr 2019 at 09:58, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Mon, Apr 29, 2019 at 08:52:46AM +0200, Ard Biesheuvel wrote:
> > > > > I am not sure if any other platform is using
> > > > > “ArmPlatformPkg/Drivers/NorFlashDxe” and may require block I/O and
> > > > > disk  I/O protocols
> > > > > if we remove “support of block I/O and disk  I/O protocols” then we
> > > > > can share the common code easily.
> > > > >
> > > >
> > > > I see your point.
> > > >
> > > > The only reason you need block i/o and disk i/o is to use ordinary
> > > > partition and filesystem drivers. I guess Juno uses this for its magic
> > > > filesystem? If not, I'd be glad to get rid of it.
> > > >
> > > >
> > > Yes  "block i/o and disk i/o  of “ArmPlatformPkg/Drivers/NorFlashDxe”
> > > driver is used even
> > > in RD-platforms(edk2-platforms/Platform/ARM/SgiPkg/)(and JUNO) to list
> > > partition. we don't want to break
> > > legacy and want to have separate
> > > "Platform/ARM/Drivers/StandaloneMmNorFlash/" driver.
> >
> > In that case, could we move the existing code into
> > edk2-platforms/Platform/ARM first? And then rip out the block i/o and
> > disk i/o parts from the common driver?
> >
> > Leif, any thoughts?
>
> I guess my only thought is what to do about RDKQemu? Probably is
> doesn't make any use of the special sauce, but need to verify?
>
> Then we conside stripping it out of the ARM platforms
> medium-term. It's one of the last bastions of "let's be different".
> Even if it should be kept around, surely it could be revamped to sit
> on top of a sane, generic NorFlashDxe?
>
> I mean, the actually relevant bit is basically
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mtd/afs.c,
> isn't it?
>
> +Thomas.
>

AIUI, these things are entirely separate. Exposing NOR flash via block
I/O and disk I/O permits the standard partition driver and FAT
filesystem driver to bind to it, so that you can have a standard FAT
ESP on NOR flash. I don't this is related at all to the BootMonFs
stuff

  reply	other threads:[~2019-04-29  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 13:10 [PATCH v2 edk2-platforms] Platform/ARM/Drivers: Add Nor Flash Driver Jagadeesh Ujja
     [not found] ` <CADpYukZHE6NY-U=EycJBVGbQ-XcxXpeT9w6svzWMePjvQXFciQ@mail.gmail.com>
2019-04-24  9:05   ` [edk2] " jagadeesh.ujja
2019-04-24 13:06     ` [edk2-devel] " Ard Biesheuvel
2019-04-29  5:59       ` Jagadeesh Ujja
2019-04-29  6:52         ` Ard Biesheuvel
2019-04-29  7:58           ` Leif Lindholm
2019-04-29  8:17             ` Ard Biesheuvel [this message]
2019-04-29  8:52               ` Leif Lindholm
2019-04-29 12:21                 ` Jagadeesh Ujja
2019-05-02  8:48                   ` Ard Biesheuvel

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-kFo7DH+n=KR-CJR8ibbZ3wdmS=Z+RZw=wJhgCpYd9eA@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