On Mon, 29 Apr 2019 at 14:21, Jagadeesh Ujja <jagadeesh.u...@arm.com> wrote: > > hi Ard/Leif > > On Mon, Apr 29, 2019 at 2:22 PM Leif Lindholm <leif.lindh...@linaro.org> > wrote: > > > > On Mon, Apr 29, 2019 at 10:17:17AM +0200, Ard Biesheuvel wrote: > > > > 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 > > > > If so, that's even sillier. If it has any business remaining > > supported, that should be a separate driver consuming NorFlashDxe. > > > > And if ARM feels their platforms need it, they can write that driver. > > > > So how about we don't move it and just nuke the BlockIo/DiskIo bits? > > > > / > > Leif > > > I am little bit confused here, please confirm > I have to copy “ArmPlatformPkg/Drivers/NorFlashDxe” to > edk2-platforms/Platform/ARM/Drivers first and then rip out the block > i/o > and disk i/o parts to get StandaloneNorFlash driver? And retain > “ArmPlatformPkg/Drivers/NorFlashDxe” as it is ? >
No. The idea is to remove block i/o and disk i/o from the NOR flash driver altogether, unless anyone has a compelling use case for them. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#39903): https://edk2.groups.io/g/devel/message/39903 Mute This Topic: https://groups.io/mt/31319945/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
