From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mips: ath79: Move SYS_SOC and SYS_VENDOR to board Kconfig
Date: Thu, 28 Jan 2016 15:53:38 +0100 [thread overview]
Message-ID: <201601281553.38944.marex@denx.de> (raw)
In-Reply-To: <BLU436-SMTP2119F190398067B607B5693FFDA0@phx.gbl>
On Thursday, January 28, 2016 at 03:43:58 PM, Wills Wang wrote:
> On Thursday, January 28, 2016 09:44 PM, Marek Vasut wrote:
> > On Thursday, January 28, 2016 at 02:31:11 PM, Wills Wang wrote:
> >> On Thursday, January 28, 2016 07:51 AM, Marek Vasut wrote:
> >>> In order to support boards with ath79 from different vendors and
> >>> thus located under /board/$VENDOR/ , we need to define SYS_VENDOR
> >>> and SYS_SOC in the board-level Kconfig. Move these two variables
> >>> into board-level Kconfig for both ap121 and ap143 boards.
> >>>
> >>> Signed-off-by: Marek Vasut <marex@denx.de>
> >>> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
> >>> Cc: Wills Wang <wills.wang@live.com>
> >>> ---
> >>>
> >>> arch/mips/mach-ath79/Kconfig | 6 ------
> >>> board/ath79/ap121/Kconfig | 6 ++++++
> >>> board/ath79/ap143/Kconfig | 6 ++++++
> >>> 3 files changed, 12 insertions(+), 6 deletions(-)
> >>>
> >>> diff --git a/arch/mips/mach-ath79/Kconfig
> >>> b/arch/mips/mach-ath79/Kconfig index 95f7de9..8f07a77 100644
> >>> --- a/arch/mips/mach-ath79/Kconfig
> >>> +++ b/arch/mips/mach-ath79/Kconfig
> >>> @@ -1,12 +1,6 @@
> >>>
> >>> menu "QCA/Athroes 7xxx/9xxx platforms"
> >>>
> >>> depends on ARCH_ATH79
> >>>
> >>> -config SYS_VENDOR
> >>> - default "ath79"
> >>> -
> >>> -config SYS_SOC
> >>> - default "ath79"
> >>> -
> >>>
> >>> config SOC_AR933X
> >>>
> >>> bool
> >>> select SUPPORTS_BIG_ENDIAN
> >>>
> >>> diff --git a/board/ath79/ap121/Kconfig b/board/ath79/ap121/Kconfig
> >>> index ec72914..a4e5690 100644
> >>> --- a/board/ath79/ap121/Kconfig
> >>> +++ b/board/ath79/ap121/Kconfig
> >>> @@ -1,5 +1,11 @@
> >>>
> >>> if BOARD_AP121
> >>>
> >>> +config SYS_VENDOR
> >>> + default "ath79"
> >>> +
> >>> +config SYS_SOC
> >>> + default "ath79"
> >>> +
> >>>
> >>> config SYS_BOARD
> >>>
> >>> default "ap121"
> >>>
> >>> diff --git a/board/ath79/ap143/Kconfig b/board/ath79/ap143/Kconfig
> >>> index 118b9b5..2e54fa7 100644
> >>> --- a/board/ath79/ap143/Kconfig
> >>> +++ b/board/ath79/ap143/Kconfig
> >>> @@ -1,5 +1,11 @@
> >>>
> >>> if BOARD_AP143
> >>>
> >>> +config SYS_VENDOR
> >>> + default "ath79"
> >>> +
> >>> +config SYS_SOC
> >>> + default "ath79"
> >>> +
> >>>
> >>> config SYS_BOARD
> >>>
> >>> default "ap143"
> >>
> >> I plan to place ap121 and ap143 into board/qca, and then
> >> move these into board directory.
> >
> > That's fine, but keep this patch or something along those lines, since
> > I want to create board/arduino/yun/ soon after your stuff is accepted.
> >
> > btw. I got both EHCI and ethernet operational, but I am still struggling
> > with booting the board from the SPI NOR. I think there's something broken
> > in start.S or lowlevel_init.S . Which board do you use for your
> > development and testing ?
>
> My private board was made by myself, it originate from AP121, and
> it's circuit is compatible with AP121.
How do you program your board ? Do you have EJTAG?
What SPI NOR do you use?
next prev parent reply other threads:[~2016-01-28 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 23:51 [U-Boot] [PATCH 1/3] mips: ath79: Fix compiler warning on const assignment Marek Vasut
2016-01-27 23:51 ` [U-Boot] [PATCH 2/3] mips: ath79: Drop SYS_MIPS_CACHE_INIT_RAM_LOAD Marek Vasut
2016-01-28 13:25 ` Wills Wang
2016-01-28 13:26 ` Marek Vasut
2016-01-27 23:51 ` [U-Boot] [PATCH 3/3] mips: ath79: Move SYS_SOC and SYS_VENDOR to board Kconfig Marek Vasut
2016-01-28 13:30 ` Wills Wang
2016-01-28 13:31 ` Wills Wang
2016-01-28 13:44 ` Marek Vasut
2016-01-28 14:43 ` Wills Wang
2016-01-28 14:53 ` Marek Vasut [this message]
2016-01-29 8:46 ` Wills Wang
2016-01-29 8:50 ` Marek Vasut
2016-01-28 13:23 ` [U-Boot] [PATCH 1/3] mips: ath79: Fix compiler warning on const assignment Wills Wang
2016-01-28 13:25 ` Marek Vasut
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=201601281553.38944.marex@denx.de \
--to=marex@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 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.