GitHub-Mirror/meta-riscv
2
0
Fork 0
mirror of https://github.com/Fishwaldo/meta-riscv.git synced 2025-03-16 20:11:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
OpenEmbedded/Yocto layer for RISC-V Architecture
16 commits 9 branches 0 tags 8 MiB
BitBake 72.9%
Makefile 21.7%
Shell 3%
CMake 2.4%
Find a file
Khem Raj b8db3af843 qemuriscv64: Switch to riscv forks of qemu and gdb 
Use linux-libc-headers from oe-core

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-03-08 23:07:14 -08:00
conf qemuriscv64: Switch to riscv forks of qemu and gdb 2018-03-08 23:07:14 -08:00
recipes-core/glibc glibc: Fix mcontext_t 2017-10-06 20:56:51 -07:00
recipes-devtool gdb: Add riscv version 2018-03-08 23:04:24 -08:00
recipes-extended/ghostscript ghostscript: Fix typo in FILESEXTRAPATHS_prepend 2018-02-15 01:08:42 -08:00
recipes-kernel/linux linux-riscv: Upgrade to 4.15 2018-03-08 23:02:34 -08:00
recipes-support nspr: Add riscv support 2017-10-04 12:01:30 -07:00
LICENSE Initial commit 2017-10-02 23:08:43 -07:00
README.md Use openembedded-core base for intructions 2017-10-22 08:15:39 -07:00

README.md

meta-riscv

RISC-V Architecture Layer for OpenEmbedded/Yocto

Description

This is the general hardware specific BSP overlay for the RISC-V based devices.

More information can be found at: https://riscv.org/ (Official Site)

The core BSP part of meta-riscv should work with different OpenEmbedded/Yocto distributions and layer stacks, such as:

  • Distro-less (only with OE-Core).
  • Angstrom.
  • Yocto/Poky (main focus of testing).

Dependencies

This layer depends on:

  • URI: git://github.com/openembedded/openembedded-core
    • branch: master
    • revision: HEAD
  • URI: git://github.com/openembedded/bitbake
    • branch: master
    • revision: HEAD

Quick Start

  1. source openembedded-core/oe-init-build-env riscv-build
  2. Add this layer to bblayers.conf and the dependencies above
  3. Set MACHINE in local.conf to one of the supported boards
  4. bitbake core-image-minimal
  5. Boot in qemu.

Maintainers

  • Khem Raj <raj dot khem at gmail.com>