From: Arnd Bergmann <arnd@arndb.de>
To: Li Chen <lchen@ambarella.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>, Li Chen <me@linux.beauty>
Subject: Re: Is hardware board required if hope to upstream a new arm/arm64 soc?
Date: Mon, 11 Jul 2022 16:49:09 +0200 [thread overview]
Message-ID: <CAK8P3a24y2HzXtBGHf1F=dJ2+6b+w+MhiK0R5EOC-fjiuf+5bA@mail.gmail.com> (raw)
In-Reply-To: <CH2PR19MB4024E9BE48E386D1D8949A39A0BE9@CH2PR19MB4024.namprd19.prod.outlook.com>
On Wed, Oct 20, 2021 at 9:47 AM Li Chen <lchen@ambarella.com> wrote:
>
> Hi, all
>
> I wonder if a soc design vendor try to get their new socs upstreamed, do
> maintainers need to get hardware/boards from vendors to verify bootable
> or other issues?
Hi Li,
I found your old email today after I saw your recent kernel patches.
To answer your original question: there is no requirement to have hardware
available anywhere, in fact I have very little hardware from any of the
platforms.
The deal is that upstream maintainers care about long-term maintainability,
I want to make sure that adding a new platform does not make it harder
for other developers to do tree-wide changes that require modifications
to each platform, to avoid regressions.
Whether the code works correctly in the first place is up to the
downstream maintainer who submits the code. If you want to add
a new platform, I expect you to test the code.
On the other hand, if you want to integrate a platform into automated
test setups, the kernelci.org team is usually happy to either add
boards into their fully automated labs, or to link up to third-party
labs that are able to run kernels built by kernelci.
Let me know if you have any other questions about upstreaming,
I would very much like to see ambarella SoCs get supported by
the kernel.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-11 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 7:47 Is hardware board required if hope to upstream a new arm/arm64 soc? Li Chen
2021-10-26 5:55 ` Li Chen
2022-07-11 14:49 ` Arnd Bergmann [this message]
2022-07-12 3:05 ` Li Chen
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='CAK8P3a24y2HzXtBGHf1F=dJ2+6b+w+MhiK0R5EOC-fjiuf+5bA@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=lchen@ambarella.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=me@linux.beauty \
/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;
as well as URLs for NNTP newsgroup(s).