mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
To: Sascha Hauer <>, Ahmad Fatoum <>
Cc:, Jules Maselbas <>
Subject: Re: [PATCH v2 3/4] RISC-V: board-dt-2nd: add PBL console support for virt
Date: Thu, 15 Apr 2021 09:53:17 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Sascha,

On 15.04.21 09:15, Sascha Hauer wrote:
>> +static const struct fdt_device_id console_ids[] = {
>> +	{ .compatible = "riscv-virtio", .data = virt_ns16550_init },
>> +	{ /* sentinel */ }
> This is only board specific. If we go that path of parsing fdt for early
> output can't we just do like Linux and establish earlycon?

Yes, we'll get there eventually. What I'd really like to have is to be
able to, at compile time, associate a debug console with a PBL entry point
that would also work prior to relocation. That debug console should be
inherited into barebox proper to be used until a console driver was

We are not there yet though and I still didn't figure some stuff out.
So I'd prefer postponing this more generic until a second boards needs it.


Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

barebox mailing list

  reply	other threads:[~2021-04-15  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 11:06 [PATCH v2 1/4] PBL: fdt: implement fdt_device_get_match_data Ahmad Fatoum
2021-04-10 11:06 ` [PATCH v2 2/4] RISC-V: debug_ll: ns16550: split off debug_ll from generic parts Ahmad Fatoum
2021-04-10 11:06 ` [PATCH v2 3/4] RISC-V: board-dt-2nd: add PBL console support for virt Ahmad Fatoum
2021-04-15  7:15   ` Sascha Hauer
2021-04-15  7:53     ` Ahmad Fatoum [this message]
2021-04-10 11:06 ` [PATCH v2 4/4] RISC-V: delete unused mach-virt subdirectory Ahmad Fatoum

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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