While in the past MIPS boards were either low-end PIC32 or found in routers running OpenWRT at most, Imagination themselves have recently released the Creator CI20 board (Ingenic, MIPS32) running Debian. And the Shield Pro (previously iGuardian) kickstarter project (Octeon-III, MIPS64) promises to become a playground for testing KVM hardware virtualization.

Porting openSUSE to MIPS will involve setting up an OBS instance linked to Factory (update: done) and cross-compiling a set of packages for an initial bootstrap (update: in progress). Maybe this can be scripted to some degree, as there will be some overlap with the ARM ILP32 port project.

For lack of hardware, qemu-linux-user would need to be used for building in OBS, as done initially for the AArch64 port.

Looking for hackers with the skills:

mips obs openbuildservice

This project is part of:

Hack Week 12 Hack Week 13 Hack Week 14

Activity

  • over 8 years ago: zzhou liked this project.
  • over 8 years ago: dsterba liked this project.
  • over 8 years ago: a_faerber joined this project.
  • over 8 years ago: wawiv74 started this project.
  • almost 9 years ago: dsterba liked this project.
  • about 9 years ago: joachimwerner liked this project.
  • about 9 years ago: mbrugger liked this project.
  • over 9 years ago: adrianSuSE liked this project.
  • over 9 years ago: a_faerber added keyword "mips" to this project.
  • over 9 years ago: a_faerber added keyword "obs" to this project.
  • over 9 years ago: a_faerber added keyword "openbuildservice" to this project.
  • over 9 years ago: a_faerber originated this project.

  • Comments

    • joachimwerner
      about 9 years ago by joachimwerner | Reply

      Does this mean that ultimately I could run openSUSE on this thing?

      http://www.hootoo.com/hootoo-tripmate-ht-tm06-wireless-router.html

      It's got a https://wikidevi.com/wiki/MediaTek_MT7620

      • a_faerber
        over 8 years ago by a_faerber | Reply

        For now I'm working on cross-compiling userspace binaries and bootstrapping core packages like rpm. mipsel with current default options should run on a wide range of devices; mips64 I'm building in parallel, which will be less widely supported. Bootloader and kernel support for individual devices I have not yet looked into at all - we may need to employ a similar scheme as for ARM, with devel:MIPS:Factory:Contrib:Foo projects for vendor kernels or U-Boot forks.

      • a_faerber
        over 8 years ago by a_faerber | Reply

        Actually I just received an AsiaRF board with an MT7620A. It's got a Ralink U-Boot 1.1.3, kernel 2.6.36 and Busybox on it. Not immediately usable as build worker, and chances are a Factory systemd won't work on such an old kernel.

    • a_faerber
      over 8 years ago by a_faerber | Reply

      An oSC talk will explain my bootstrap setup and the latest status, offering a platform for discussing collaboration.

    Similar Projects

    Linux on Cavium CN23XX cards by tsbogend

    Before Cavium switched to ARM64 CPUs they developed quite powerful MIPS based SOCs. The current upstream Linux kernel already supports some Octeon SOCs, but not the latest versions. Goal of this Hack Week project is to use the latest Cavium SDK to update the Linux kernel code to let it running on CN23XX network cards.


    Explore the integration between OBS and GitHub by pdostal

    Project Description

    The goals:

    1) When GitHub pull request is created or modified the OBS project will be forked and the build results reported back to GitHub. 2) When new version of the GitHub project will be published the OBS will redownload the source and rebuild the project.

    Goal for this Hackweek

    Do as much as possible, blog about it and maybe use it another existing project.

    Resources


    Learn obs/ibs sync tool by xlai

    Description

    Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

    Goals

    Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

    Resources

    • https://github.com/os-autoinst/openqa-trigger-from-obs
    • https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads


    Git CI to automate the creation of product definition by gyribeiro

    Description

    Automate the creation of product definition

    Goals

    Create a Git CI that will:

    • automatically be triggered once a change (commit) in package list is done.
    • run tool responsible to update product definition based on the changes in package list
    • test the updated product definition in OBS
    • submit a pull request updating the product definition in the repository

    NOTE: this Git CI may also be triggered manually

    Resources

    • https://docs.gitlab.com/ee/ci/
    • https://openbuildservice.org/2021/05/31/scm-integration/
    • https://github.com/openSUSE/openSUSE-release-tools


    Learn about OSB and contribute to `kustomize` and `k9s` packages to add ARM arch by dpock

    Description

    There are already k9s and kustomize packages that exist for openSUSE today. These could be used as the source for these binaries in our rancher projects. By using them we would benefit from CVE fixes included in our distribution of the packages not in cluded upstream. However they are not providing arm package builds which are required.

    Goals

    • [ ] Update the kustomize package in OBS to use the newest version and send change request

    Resources

    • k9s: https://build.opensuse.org/package/show/openSUSE:Factory/k9s
    • kustomize: https://build.opensuse.org/package/show/openSUSE:Factory/kustomize
    • Learning Docs: https://confluence.suse.com/display/packaging/Training%2C+Talks+and+Videos


    obs-service-vendor_node_modules by cdimonaco

    Description

    When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

    obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

    The tar will be used as source in the package building definitions.

    Goals

    • Create an obs service package that vendors the npm dependencies as tar archive.
    • Maybe add some macros to unpack the vendor package in the specfiles

    Resources