From: Tom Rini <trini@konsulko.com>
To: Stefan Roese <sr@denx.de>
Cc: "Tony Dinh" <mibodhi@gmail.com>,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Marek Beh�n" <marek.behun@nic.cz>,
"Pali Roh�r" <pali@kernel.org>,
"David Purdy" <david.c.purdy@gmail.com>
Subject: Re: [PATCH v2 4/8] arm: kirkwood: Pogoplug-V4 : Add board include configs file
Date: Thu, 13 Jan 2022 08:36:27 -0500 [thread overview]
Message-ID: <20220113133627.GK9207@bill-the-cat> (raw)
In-Reply-To: <8eb39c1f-9523-5017-af45-3d3bba07c443@denx.de>
[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]
On Thu, Jan 13, 2022 at 02:32:00PM +0100, Stefan Roese wrote:
> On 12/23/21 08:26, Tony Dinh wrote:
> > Add include configs file for Pogoplug V4 board
> >
> > Signed-off-by: Tony Dinh <mibodhi@gmail.com>
> > ---
> >
> > (no changes since v1)
> >
> > include/configs/pogo_v4.h | 94 +++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 94 insertions(+)
> > create mode 100644 include/configs/pogo_v4.h
> >
> > diff --git a/include/configs/pogo_v4.h b/include/configs/pogo_v4.h
> > new file mode 100644
> > index 0000000000..b449986e8c
> > --- /dev/null
> > +++ b/include/configs/pogo_v4.h
> > @@ -0,0 +1,94 @@
> > +/* SPDX-License-Identifier: GPL-2.0+ */
> > +/*
> > + * Copyright (C) 2014-2021 Tony Dinh <mibodhi@gmail.com>
> > + *
> > + * Based on
> > + * Copyright (C) 2012
> > + * David Purdy <david.c.purdy@gmail.com>
> > + *
> > + * Based on Kirkwood support:
> > + * (C) Copyright 2009
> > + * Marvell Semiconductor <www.marvell.com>
> > + * Written-by: Prafulla Wadaskar <prafulla@marvell.com>
> > + */
> > +
> > +#ifndef _CONFIG_POGO_V4_H
> > +#define _CONFIG_POGO_V4_H
> > +
> > +/*
> > + * Machine type definition and ID
> > + */
> > +#define MACH_TYPE_POGO_V4 3960
> > +#define CONFIG_MACH_TYPE MACH_TYPE_POGO_V4
>
> Are you really using the pretty old CONFIG_MACH_TYPE to boot Linux
> on this device?
>
> > +
> > +/*
> > + * High Level Configuration Options (easy to change)
> > + */
> > +#define CONFIG_FEROCEON_88FR131 /* #define CPU Core subversion */
> > +#define CONFIG_KW88F6192 /* SOC Name */
>
> At least CONFIG_FEROCEON_88FR131 is available in Kconfig
> (arch/arm/mach-kirkwood/Kconfig), so there should be no need to add it
> via some header.
>
> Please double-check other macros in this header as well for availability
> in Kconfig.
At this point you can now make CI do this for you as we have a test that
will fail if there's unmigrated symbols in your board header file. The
logic can also be copy/pasted out to a script to run by yourself too.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-13 13:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 7:26 [PATCH v2 0/8] arm: kirkwood: Add support for Pogoplug V4 Tony Dinh
2021-12-23 7:26 ` [PATCH v2 1/8] arm: kirkwood: Pogoplug-V4 : Add DTS files Tony Dinh
2022-01-13 13:32 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 2/8] arm: kirkwood: Pogoplug V4 : Add board defconfig file Tony Dinh
2022-01-13 13:33 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 3/8] arm: kirkwood: Pogoplug-V4 : Add Kconfig files Tony Dinh
2022-01-13 13:35 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 4/8] arm: kirkwood: Pogoplug-V4 : Add board include configs file Tony Dinh
2022-01-13 13:32 ` Stefan Roese
2022-01-13 13:36 ` Tom Rini [this message]
2022-01-14 0:50 ` Tony Dinh
2022-01-14 1:41 ` Tom Rini
2021-12-23 7:26 ` [PATCH v2 5/8] arm: kirkwood: Pogoplug-V4 : Add board kwbimage file Tony Dinh
2022-01-13 13:36 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 6/8] arm: kirkwood: Pogoplug-V4 : Add board Make file Tony Dinh
2022-01-13 13:37 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 7/8] arm: kirkwood: Pogoplug-V4 : Add board implementation Tony Dinh
2022-01-13 13:38 ` Stefan Roese
2021-12-23 7:26 ` [PATCH v2 8/8] arm: kirkwood: Pogoplug-V4 : Add board maintainer Tony Dinh
2022-01-13 13:40 ` Stefan Roese
2022-01-13 23:32 ` Tony Dinh
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=20220113133627.GK9207@bill-the-cat \
--to=trini@konsulko.com \
--cc=david.c.purdy@gmail.com \
--cc=marek.behun@nic.cz \
--cc=mibodhi@gmail.com \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--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