From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nios2: zap nios2-generic board dir
Date: Mon, 19 Oct 2015 01:43:10 +0200 [thread overview]
Message-ID: <201510190143.10616.marex@denx.de> (raw)
In-Reply-To: <56242E3C.9080807@wytron.com.tw>
On Monday, October 19, 2015 at 01:41:48 AM, Thomas Chou wrote:
> Hi Marek,
Hi,
> On 10/18/2015 11:35 PM, Marek Vasut wrote:
> >> +config SYS_CONFIG_NAME
> >> + string "Board header file"
> >> + help
> >> + This option should contain the base name of board header file.
> >> + The header file include/configs/<CONFIG_SYS_CONFIG_NAME>.h
> >> + should be included from include/config.h.
> >
> > I suspect we don't want this, since we're probing from DT. This option
> > should default to something like include/configs/nios2.h , no ?
>
> This is needed as the Kconfig doesn't cover every config option yet. We
> still need a per board file. But this is supposed to be removed when
> Kconfig is done for every option.
Don't we support just nios2-generic board ?
> Now, the legacy board header, defconfig and dts are all that we need to
> add a new board to nios2. I should add a README.nios2 after I finished
> the conversion of altera_tse to driver model.
Yeah :) Thanks!
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-10-18 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 8:36 [U-Boot] [PATCH] nios2: zap nios2-generic board dir Thomas Chou
2015-10-18 15:35 ` Marek Vasut
2015-10-18 23:41 ` Thomas Chou
2015-10-18 23:43 ` Marek Vasut [this message]
2015-10-18 23:55 ` [U-Boot] [PATCH v2] " Thomas Chou
2015-10-23 0:18 ` Thomas Chou
2015-10-23 0:20 ` 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=201510190143.10616.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox