From: Marcin Wojtas <mw@semihalf.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
nadavh@marvell.com, Neta Zur Hershkovits <neta@marvell.com>,
Kostya Porotchkin <kostap@marvell.com>,
Hua Jing <jinghua@marvell.com>, Alexander Graf <agraf@suse.de>,
semihalf-dabros-jan <jsd@semihalf.com>,
Nir Erez <nerez@marvell.com>
Subject: Re: [platforms: PATCH 01/11] Platform/Marvell/Documentation: Refactor PortingGuide
Date: Fri, 1 Sep 2017 17:56:20 +0200 [thread overview]
Message-ID: <CAPv3WKf_yFcDH64_rqAnkVCgB0CeeLTFhOhJ650RsP9y7n3sqg@mail.gmail.com> (raw)
In-Reply-To: <20170901154515.wcxkzpvrytgnwkqh@bivouac.eciton.net>
2017-09-01 17:45 GMT+02:00 Leif Lindholm <leif.lindholm@linaro.org>:
> On Fri, Sep 01, 2017 at 05:08:39PM +0200, Marcin Wojtas wrote:
>> Hi Leif,
>>
>> 2017-09-01 16:36 GMT+02:00 Leif Lindholm <leif.lindholm@linaro.org>:
>> > On Fri, Sep 01, 2017 at 03:08:13PM +0200, Marcin Wojtas wrote:
>> >> From: Nir Erez <nerez@marvell.com>
>> >>
>> >> This patch introduces following improvements to the PortingGuide
>> >> * Replace split documentation with single file
>> >> * Align format to Doxygen constraints
>> >
>> > * Add Build description.
>> > (Comment on that below.)
>> >
>> > Since you are moving things around, I take this as license to
>> > bikeshed:
>> >
>> > I think we should start looking towards separating the development
>> > board and SoC portions, like is done for most other platforms. After
>> > all, the goal is to get additional platforms (not just the EVB).
>> >
>> > Not saying this is something that needs to happen overnight, but it
>> > would make sense to make a start by moving these docs to
>> > Silicon/Marvell/Documentation as part of this patch.
>>
>> I can add it there, no problem. About Silicon vs Platform - I checked
>> the code and basically we'd have to move everything from
>> Platform/Marvell to Silicon/Marvell and leave just subdirectories with
>> board files (dsc, fdf + dtb):
>> Platform/Marvell/Armada70x0Db
>> Platform/Marvell/Armada80x0Db
>> Platform/Marvell/Armada80x0McBin
>> etc.
>> Is it what you mean?
>
> Yeah, exactly. (Although depending on point if view, maybe
> Marvell/Armada80x0McBin should be SolidRun/MacchiatoBin.)
Personally, I'd keep all Marvell boards under Platform/Marvell, so
that not to make a mess, but we can discuss it later of course.
> I'm hoping there could be a lot of sharing of common bits of files in
> generic .dsc.inc/.fdf.inc - both here and under Silicon/Marvell.
On our working branch, there is single dsc.inc and .fdf for all boards
and I think such shareability can be maintained further.
>
>> I'm wondering when will be good moment for this - I'm rebasing 70 OPP
>> patches slowly in my extra time, so maybe after the SPI patchset? Or
>> better after we merge everything to Platform and then do the code
>> shifting? What is your feeling about it?
>
> Well, if I was going to take a hard line on this, that was an option I
> had during the initial import to OpenPlatformPkg. Since I didn't, this
> is very much a "I would be happy to see this happen" kind of thing.
>
> So it's sort of up to you.
>
> But I'll throw in that I am planning to go into hiding for a couple of
> days next week to try and once and for all create some generic config
> fragments that can be reused across all platforms instead of copying
> the same bits along everywhere. So it would make sense to wait with
> any larger interventions until that work is complete.
>
Ok. I have a lot of stuff queued, before adding the new A8040 boards,
so I can proceed with fixes/enhancements, that won't be problematic to
halt in the middle and do the shift.
Thanks,
Marcin
next prev parent reply other threads:[~2017-09-01 15:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 13:08 [platforms: PATCH 00/11] Armada 70x0/80x0 SPI improvements Marcin Wojtas
2017-09-01 13:08 ` [platforms: PATCH 01/11] Platform/Marvell/Documentation: Refactor PortingGuide Marcin Wojtas
2017-09-01 14:36 ` Leif Lindholm
2017-09-01 15:08 ` Marcin Wojtas
2017-09-01 15:45 ` Leif Lindholm
2017-09-01 15:56 ` Marcin Wojtas [this message]
2017-09-01 13:08 ` [platforms: PATCH 02/11] Drivers/Spi/MvSpiDxe: Log and return correct error Marcin Wojtas
2017-09-01 14:05 ` Ard Biesheuvel
2017-09-01 13:08 ` [platforms: PATCH 03/11] Drivers/Spi/MvSpiDxe: Fix write bug Marcin Wojtas
2017-09-01 14:44 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 04/11] Applications/SpiTool: Enable configurable CS and SCLK mode Marcin Wojtas
2017-09-01 14:47 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 05/11] Platform/Marvell/Armada70x0: set CS and SCLK Mode for SPI flash Marcin Wojtas
2017-09-01 14:48 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 06/11] Applications/SpiTool: Fix bug in error test Marcin Wojtas
2017-09-01 14:48 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 07/11] Applications/FirmwareUpdate: Fix 32-bit issues Marcin Wojtas
2017-09-01 14:54 ` Leif Lindholm
2017-09-01 15:16 ` Ard Biesheuvel
2017-09-01 15:51 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 08/11] Applications/SpiTool: " Marcin Wojtas
2017-09-01 14:56 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 09/11] Drivers/Spi/Devices/MvSpiFlash: Fix usage of erase size parameter Marcin Wojtas
2017-09-01 15:21 ` Leif Lindholm
2017-09-01 15:25 ` Marcin Wojtas
2017-09-01 15:51 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 10/11] Drivers/Spi/Devices/MvSpiFlash: Enable dynamic SPI Flash detection Marcin Wojtas
2017-09-01 15:33 ` Leif Lindholm
2017-09-01 17:20 ` Marcin Wojtas
2017-09-01 22:03 ` Leif Lindholm
2017-09-01 13:08 ` [platforms: PATCH 11/11] Drivers/Spi/Devices/MvSpiFlash: Fix bank selection for Spansion Marcin Wojtas
2017-09-01 15:34 ` Leif Lindholm
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=CAPv3WKf_yFcDH64_rqAnkVCgB0CeeLTFhOhJ650RsP9y7n3sqg@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