From: Graham Leva <celaxodon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] package/linux-nvidia for Jetson Nano SD
Date: Fri, 6 Nov 2020 18:29:24 -0600 [thread overview]
Message-ID: <20201107002925.6561-1-celaxodon@gmail.com> (raw)
Hello,
I would like to submit some packages to support building NVIDIA's Jetson
line of boards, beginning with the Jetson Nano 4GB developer module. This
will be the the first of roughly 10 commits -- 9 packages for various
code repositories for building NVIDIA's Linux for Tegra kernel and an
additional commit for the board/nvidia files and defconfig.
I wasn't sure whether or not to submit this as a patch series or
as standalone patches. Happy to resubmit if the preference
is for a patch series.
While this is not an officially supported project by NVIDIA, I
have received approval from legal and management for these patches.
I also wanted to say that I've become a big fan of Buildroot after
creating this port. This is an excellent project, and I've learned a
tremendous amount from it. Thank you for all the hard work!
Kind regards,
Graham Leva
Graham Leva (1):
package/linux-nvidia: add nvidia linux kernel extensions package
DEVELOPERS | 3 +++
linux/Config.ext.in | 10 ++++++++++
package/Config.in | 1 +
package/linux-nvidia/Config.in | 7 +++++++
package/linux-nvidia/linux-nvidia.hash | 2 ++
package/linux-nvidia/linux-nvidia.mk | 20 ++++++++++++++++++++
6 files changed, 43 insertions(+)
create mode 100644 package/linux-nvidia/Config.in
create mode 100644 package/linux-nvidia/linux-nvidia.hash
create mode 100644 package/linux-nvidia/linux-nvidia.mk
--
2.17.1
next reply other threads:[~2020-11-07 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 0:29 Graham Leva [this message]
2020-11-07 0:29 ` [Buildroot] [PATCH 1/1] package/linux-nvidia: add nvidia linux kernel extensions package Graham Leva
2020-11-29 22:36 ` Graham Leva
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=20201107002925.6561-1-celaxodon@gmail.com \
--to=celaxodon@gmail.com \
--cc=buildroot@busybox.net \
/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