From: "Sunil V L" <sunilvl@ventanamicro.com>
To: Ran Wang <wangran@bosc.ac.cn>
Cc: devel@edk2.groups.io, wangyang@bosc.ac.cn,
YunFeng Yang <yangyunfeng@bosc.ac.cn>,
YaXing Guo <guoyaxing@bosc.ac.cn>,
Bamvor Jian ZHANG <zhangjian@bosc.ac.cn>,
Daniel Schaefer <git@danielschaefer.me>
Subject: Re: [edk2-devel] [PATCH] NanhuDev:Add BOSC NanhuDev platform
Date: Thu, 14 Mar 2024 10:58:38 +0530 [thread overview]
Message-ID: <ZfKLBr9tGQhcaeCl@sunil-laptop> (raw)
In-Reply-To: <ab413a6f-f9d9-4f22-bb2a-706f0691ecd5@bosc.ac.cn>
Hi Ran,
On Mon, Mar 11, 2024 at 12:29:53PM +0800, Ran Wang wrote:
> Hi Sunil,
>
> On 2024/3/8 19:44, Sunil V L wrote:
> > On Fri, Mar 08, 2024 at 12:31:26AM -0800, WangYang wrote:
> > > Hi,Sunil V L
> > >
> > > How about this status.
> > >
> > >
> > > > -----原始邮件-----
> > > > 发件人: WangYang <wangyang@bosc.ac.cn>
> > > > 发送时间: 2024-02-28 14:34:11 (星期三)
> > > > 收件人: devel@edk2.groups.io, sunilvl@ventanamicro.com
> > > > 抄送: "Yang Wang" <wangyang@bosc.ac.cn>, "Ran Wang" <wangran@bosc.ac.cn>, "YunFeng Yang" <yangyunfeng@bosc.ac.cn>, "YaXing Guo" <guoyaxing@bosc.ac.cn>, "Bamvor Jian ZHANG" <zhangjian@bosc.ac.cn>
> > > > 主题: [edk2-devel] [PATCH] NanhuDev:Add BOSC NanhuDev platform
> > > >
> > > > This commit adds the initial support for BOSC's
> > > > nanhu platform which provides up to 2 RISC-V RV64
> > > > processor cores.
> > > >
> > Somehow I missed this when you sent first. What do you mean by "initial
> > support" here?
> >
>
> The "initial" means so far we only support minimal system (CPU + UART), will
> integrate more periphrals in the future.
>
Okay. Can you boot an OS with this minimal support? Why not add full
support itself? Since the structure needs to be reviewed, it would be
better to have complete picture IMO.
> > Looks like you are following old integrated opensbi approach.
> > If so, I recommend you to look at payload design. You can see Sophgo
> > board as reference.
>
> Thanks for advices, so we need to rebase our work on
> Silicon/Sophgo/SG2042Pkg/Sec/Sec* rather than
> RISC-V/PlatformPkg/Universal/Sec/Riscv64/Sec*, right?
>
Yes. It is better to use edk2 as a payload for opensbi.
> > Also, please remember to CC all maintainers as per Maintainers.txt.
>
> Does the "all maintainers" mean all mentioned in Maintainers.txt, or just
> RISC-V related?
>
You need to copy the overall maintainers for edk2-platforms repo (Mike
and Leif). They need to approve the structure for your platforms. Then
you can copy RISC-V maintainers. Add one patch to update the maintainers
for your platform as well.
Thanks,
Sunil
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116732): https://edk2.groups.io/g/devel/message/116732
Mute This Topic: https://groups.io/mt/104619268/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-03-14 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17B7F347DFE5DC11.6249@groups.io>
2024-03-08 8:31 ` [edk2-devel] [PATCH] NanhuDev:Add BOSC NanhuDev platform WangYang
2024-03-08 11:44 ` Sunil V L
[not found] ` <ab413a6f-f9d9-4f22-bb2a-706f0691ecd5@bosc.ac.cn>
2024-03-14 5:28 ` Sunil V L [this message]
2024-03-14 9:23 ` Ran Wang
2024-02-28 6:34 WangYang
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-list 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=ZfKLBr9tGQhcaeCl@sunil-laptop \
--to=devel@edk2.groups.io \
/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