From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 03/12] Add initial RISC-V architecture support
Date: Fri, 29 Jun 2018 13:32:55 +0200 [thread overview]
Message-ID: <20180629113255.idhib3zi3vma4nco@pengutronix.de> (raw)
In-Reply-To: <20180629132710.88b512ddb6c8331d3655afa3@gmail.com>
On Fri, Jun 29, 2018 at 01:27:10PM +0300, Antony Pavlov wrote:
> On Fri, 29 Jun 2018 09:29:08 +0200
> >
> > Do you need these __bare_init* stuff? If not I would prefer to remove
> > it.
>
>
> Hmmm. You are right! I have not realized PBL for RISC-V yet so it's better
> to drop all these bare_inits.
This isn't needed for PBL either. It is only for cases where the boot
ROM only loads the initial image portion.
> >
> > > +static int of_riscv_init(void)
> > > +{
> > > + struct device_node *root;
> > > +
> > > + root = of_get_root_node();
> > > + if (root)
> > > + return 0;
> > > +
> > > + root = of_unflatten_dtb(__dtb_start);
> > > + if (!IS_ERR(root)) {
> > > + pr_debug("using internal DTB\n");
> > > + of_set_root_node(root);
> > > + if (IS_ENABLED(CONFIG_OFDEVICE))
> > > + of_probe();
> > > + }
> >
> > Can we just call of_unflatten_dtb()/of_set_root_node() from the board
> > code and use obj-dtb-y to include the dtb?
> >
> > That way a board can specify the dtb and not the config.
>
> Good idea! MIPS code lacks this feature at the moment.
>
> Can I use of_arm_init() as a reference?
Not sure what you mean. of_riscv_init() is nearly a copy of
of_arm_init() already.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-06-29 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 7:39 [PATCH v2 00/12] " Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 01/12] lib: Add shared copies of some GCC library routines Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 02/12] MIPS: Use generic GCC library routines from lib/ Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 03/12] Add initial RISC-V architecture support Antony Pavlov
2018-06-29 7:29 ` Sascha Hauer
2018-06-29 10:27 ` Antony Pavlov
2018-06-29 11:32 ` Sascha Hauer [this message]
2018-06-29 13:17 ` Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 04/12] RISC-V: add Erizo SoC support Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 05/12] RISC-V: add low-level debug macros for ns16550 Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 06/12] RISC-V: add nmon nano-monitor Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 07/12] RISC-V: erizo: add DEBUG_LL support Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 08/12] RISC-V: erizo: enable nmon Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 09/12] RISC-V: erizo: add nmon image creation Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 10/12] RISC-V: add erizo_generic_defconfig Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 11/12] scripts: add nmon-loader Antony Pavlov
2018-06-28 7:39 ` [PATCH v2 12/12] Documentation: add RISC-V docs Antony Pavlov
2018-06-29 7:30 ` [PATCH v2 00/12] Add initial RISC-V architecture support Sascha Hauer
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=20180629113255.idhib3zi3vma4nco@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox