Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Joshua Watt" <JPEWhacker@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [yocto][meta-rockchip][PATCH v2 0/4] Add Rock Pi 4 Support
Date: Thu, 23 Jan 2020 13:46:41 -0600	[thread overview]
Message-ID: <20200123194645.1240023-1-JPEWhacker@gmail.com> (raw)
In-Reply-To: <20200123160821.778821-1-JPEWhacker@gmail.com>

Add support for building the Raxada Rock Pi 4 development board

V2: Machine has been renamed "rock-pi-4" to match the manufacturers name

Joshua Watt (4):
  arm-trusted-firmware: Add recipe
  gcc-arm-none-eabi-native: Add recipe
  rk3399: Add generic rk3399 support
  rock-pi-4: Add machine

 README                                        |  1 +
 conf/machine/include/rk3066.inc               |  3 +
 conf/machine/include/rk3188.inc               |  3 +
 conf/machine/include/rk3288.inc               |  3 +
 conf/machine/include/rk3399.inc               | 27 ++++++
 conf/machine/include/rockchip-defaults.inc    |  2 -
 conf/machine/rock-pi-4.conf                   | 28 ++++++
 ...hip-Prevent-macro-expansion-in-paths.patch | 94 +++++++++++++++++++
 .../arm-trusted-firmware_2.2.bb               | 44 +++++++++
 recipes-bsp/u-boot/u-boot%.bbappend           |  8 ++
 ...cc-arm-none-eabi-native_9-2019-q4-major.bb | 37 ++++++++
 recipes-graphics/mesa/mesa_%.bbappend         |  1 +
 wic/rk3399-boot.wks                           | 24 +++++
 wic/rock-pi-4.wks                             |  7 ++
 14 files changed, 280 insertions(+), 2 deletions(-)
 create mode 100644 conf/machine/include/rk3399.inc
 create mode 100644 conf/machine/rock-pi-4.conf
 create mode 100644 recipes-bsp/arm-trusted-firmware/arm-trusted-firmware/0001-rockchip-Prevent-macro-expansion-in-paths.patch
 create mode 100644 recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
 create mode 100644 recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb
 create mode 100644 wic/rk3399-boot.wks
 create mode 100644 wic/rock-pi-4.wks

-- 
2.24.1


  parent reply	other threads:[~2020-01-23 19:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 16:08 [yocto][meta-rockchip][PATCH 0/4] Add RockPi 4 support Joshua Watt
2020-01-23 16:08 ` [yocto][meta-rockchip][PATCH 1/4] arm-trusted-firmware: Add recipe Joshua Watt
2020-01-23 16:08 ` [yocto][meta-rockchip][PATCH 2/4] gcc-arm-none-eabi-native: " Joshua Watt
2020-01-23 19:49   ` Khem Raj
2020-01-23 19:59     ` Joshua Watt
2020-01-23 20:06       ` Khem Raj
2020-01-23 20:14         ` Joshua Watt
2020-01-23 20:46           ` Denys Dmytriyenko
2020-01-23 22:34           ` Khem Raj
2020-01-23 16:08 ` [yocto][meta-rockchip][PATCH 3/4] rk3399: Add generic rk3399 support Joshua Watt
2020-01-23 16:08 ` [yocto][meta-rockchip][PATCH 4/4] rock-pi-4-rk3399: Add machine Joshua Watt
2020-01-23 19:46 ` Joshua Watt [this message]
2020-01-23 19:46   ` [yocto][meta-rockchip][PATCH v2 1/4] arm-trusted-firmware: Add recipe Joshua Watt
2020-01-23 20:39     ` Denys Dmytriyenko
2020-01-23 19:46   ` [yocto][meta-rockchip][PATCH v2 2/4] gcc-arm-none-eabi-native: " Joshua Watt
2020-01-23 19:46   ` [yocto][meta-rockchip][PATCH v2 3/4] rk3399: Add generic rk3399 support Joshua Watt
2020-01-23 19:46   ` [yocto][meta-rockchip][PATCH v2 4/4] rock-pi-4: Add machine Joshua Watt

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=20200123194645.1240023-1-JPEWhacker@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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