From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Heinrich Schuchardt'" <heinrich.schuchardt@canonical.com>,
"'Rick Chen'" <rick@andestech.com>,
"'Leo'" <ycliang@andestech.com>
Cc: "'Bin Meng'" <bmeng.cn@gmail.com>,
"'Anup Patel'" <apatel@ventanamicro.com>, <u-boot@lists.denx.de>
Subject: RE: [PATCH v2 0/2] risc-v: implement DBCN based debug console
Date: Tue, 5 Sep 2023 08:42:04 +0900 [thread overview]
Message-ID: <000001d9df89$6951c360$3bf54a20$@samsung.com> (raw)
In-Reply-To: <20230904112404.81899-1-heinrich.schuchardt@canonical.com>
Hi,
> -----Original Message-----
> From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Sent: Monday, September 4, 2023 8:24 PM
> To: Rick Chen <rick@andestech.com>; Leo <ycliang@andestech.com>
> Cc: Bin Meng <bmeng.cn@gmail.com>; Anup Patel <apatel@ventanamicro.com>;
> Chanho Park <chanho61.park@samsung.com>; u-boot@lists.denx.de; Heinrich
> Schuchardt <heinrich.schuchardt@canonical.com>
> Subject: [PATCH v2 0/2] risc-v: implement DBCN based debug console
>
> Currently we only offer an SBI based debug UART for SBI v0.1.
> With OpenSBI 1.3 the Debug Console Extension (DBCN) has become available.
> This allows us to implement a debug UART in a device independent manor.
>
> v2:
> In the driver check that we are in S-mode.
Thanks for the update. I've tested both patches on my VisionFive2 board.
Reviewed-by: Chanho Park <chanho61.park@samsung.com>
Tested-by: Chanho Park <chanho61.park@samsung.com>
Best Regards,
Chanho Park
prev parent reply other threads:[~2023-09-04 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230904112326epcas2p266eee0d2264cf6cf1dd53e5c756cb1d0@epcas2p2.samsung.com>
2023-09-04 11:24 ` [PATCH v2 0/2] risc-v: implement DBCN based debug console Heinrich Schuchardt
2023-09-04 11:24 ` [PATCH v2 1/2] risc-v: implement DBCN write byte Heinrich Schuchardt
2023-09-04 11:24 ` [PATCH v2 2/2] risc-v: implement DBCN based debug console Heinrich Schuchardt
2023-09-05 2:39 ` Leo Liang
2023-09-04 23:42 ` Chanho Park [this message]
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='000001d9df89$6951c360$3bf54a20$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=apatel@ventanamicro.com \
--cc=bmeng.cn@gmail.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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