From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Marc Olberding <molberding@nvidia.com>,
Eddie James <eajames@linux.ibm.com>
Cc: joel@jms.id.au, openbmc@lists.ozlabs.org
Subject: Re: [PATCH u-boot 0/2] aspeed: Add support for msx4
Date: Tue, 02 Dec 2025 09:54:25 +1030 [thread overview]
Message-ID: <8ec00dc3dfdf32edcd86ca007a596eb43acb66de.camel@codeconstruct.com.au> (raw)
In-Reply-To: <aSZVxjFQ0+pqc/hq@molberding.nvidia.com>
On Tue, 2025-11-25 at 17:20 -0800, Marc Olberding wrote:
> On Wed, Nov 26, 2025 at 10:52:51AM +1030, Andrew Jeffery wrote:
> > Hi Marc,
> Hi Andrew
> > On Fri, 2025-11-21 at 16:02 -0800, Marc Olberding wrote:
> > > Add a board file and dts for msx4. the board file is required
> > > as the BMC is strapped for ABR boot support, and this functionality
> > > isn't desired as support in linux is lacking.
> > >
> >
> > Can you expand on this? What's missing?
>
> As far as I could tell, support to pet and eventually disable the FMC_WDT2
> doesn't exist in the linux kernel (I'm happy to be wrong, I'm not in love with this workaround)
>
> So when the 2600 is strapped for dual SPI ABR, we just end up boot looping
> between the two spi flashes, since no one pets the wdt.
>
> This patch just disables this support altogether.
Hmm, yeah, I think I recall disabling it in a u-boot environment script
back at IBM. Maybe Eddie can track down whether that's still the case.
Andrew
prev parent reply other threads:[~2025-12-01 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 0:02 [PATCH u-boot 0/2] aspeed: Add support for msx4 Marc Olberding
2025-11-22 0:02 ` [PATCH u-boot 1/2] Add a new board for the gigabyte msx4 Marc Olberding
2025-11-26 0:30 ` Andrew Jeffery
2025-11-26 1:30 ` Marc Olberding
2025-12-01 23:14 ` Andrew Jeffery
2025-12-01 23:33 ` Marc Olberding
2025-12-01 23:43 ` Andrew Jeffery
2025-11-22 0:02 ` [PATCH u-boot 2/2] arch: arm: dts: Add dts for the nvidia msx4 board Marc Olberding
2025-11-26 0:22 ` [PATCH u-boot 0/2] aspeed: Add support for msx4 Andrew Jeffery
2025-11-26 1:20 ` Marc Olberding
2025-12-01 23:24 ` Andrew Jeffery [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=8ec00dc3dfdf32edcd86ca007a596eb43acb66de.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=molberding@nvidia.com \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.