From: Joel Johnson <mrjoel@lixil.net>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] arm: mvebu: clearfog: add SCSI to distro bootcmd
Date: Fri, 17 Apr 2020 01:08:03 -0600 [thread overview]
Message-ID: <f13e8a7b3dcd7442d54609deb125d4b6@lixil.net> (raw)
In-Reply-To: <5dff7af1-dfac-11de-8677-9a5a3bc28a0c@denx.de>
On 2020-04-16 00:13, Stefan Roese wrote:
> On 16.04.20 06:09, Joel Johnson wrote:
>> On 2020-03-23 04:20, Stefan Roese wrote:
>>> Added Josua to Cc.
>>>
>>> On 29.01.20 04:59, Joel Johnson wrote:
>>>> Include attempting to boot from SCSI (SATA) devices within generated
>>>> board distro bootcmd environment. The reasoning for boot ordering is
>>>> that MMC and USB are external and removable, while when a case is in
>>>> use, replacing M.2 or mSATA drives requires disassembly. Therefore,
>>>> to boot SCSI, [bootable] external media must be removed. If SCSI
>>>> were
>>>> placed before MMC or USB, then removing a bootable SCSI drive to
>>>> enable MMC or USB booting would be more difficult.
>>>>
>>>> Signed-off-by: Joel Johnson <mrjoel@lixil.net>
>>>
>>> Josua posted a similar patch (different order though):
>>>
>>> http://patchwork.ozlabs.org/patch/1239539/
>>>
>>> I tend to pull your patch though in the next merge window, if nobody
>>> objects. So:
>>>
>>> Reviewed-by: Stefan Roese <sr@denx.de>
>>>
>>> Thanks,
>>> Stefan
>>
>> I just wanted to send a bump on this series. With the first pull
>> request of the merge window you merged Josua's patch. I'd still
>> advocate for my original reasoning on the boot order priority, but in
>> either case the second patch in this series is unique and
>> non-conflicting since it adds support for the additional SCSI buses
>> depending on configuration.
>>
>> Josua - any objection to moving USB boot before SCSI in the priority
>> order?
>>
>> I'll rebase the series on current master since it will conflict, but
>> wanted to try to get consensus on the approach before doing so.
>
> Okay from me for this.
>
> Thanks,
> Stefan
Looking again it looks like *both* were merged and resulted in some
duplication, I just sent a related simple patch to correct.
Joel
prev parent reply other threads:[~2020-04-17 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 3:59 [PATCH 1/2] arm: mvebu: clearfog: add SCSI to distro bootcmd Joel Johnson
2020-01-29 3:59 ` [PATCH 2/2] arm: mvebu: clearfog: support multiple SATA boot Joel Johnson
2020-03-23 10:23 ` Stefan Roese
2020-03-22 18:53 ` [PATCH 1/2] arm: mvebu: clearfog: add SCSI to distro bootcmd Joel Johnson
2020-03-23 10:27 ` Stefan Roese
2020-03-23 15:38 ` Joel Johnson
2020-03-23 10:20 ` Stefan Roese
2020-04-16 4:09 ` Joel Johnson
2020-04-16 6:13 ` Stefan Roese
2020-04-17 7:08 ` Joel Johnson [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-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=f13e8a7b3dcd7442d54609deb125d4b6@lixil.net \
--to=mrjoel@lixil.net \
--cc=u-boot@lists.denx.de \
/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