Licences

Which licence each part of DSlot's card is under, and what that means for you.

Everything DSlot’s and nibOS’s projects wrote is free software: you may use it, study it, change it and pass it on, under the GPL or the permissive MIT and Apache-2.0.

The split🔗

PartLicence
DSlot, the game shelfGPL-3.0-or-later
nibOS’s own code, the system underneath: the hardware layer, the tools, the image build, the system’s scripts and units, the safe mode, the start-up picturesGPL-3.0-or-later
DSperate, DS and GBAGPL-3.0-or-later
nibkit, the SDK, and the template appMIT
inkdot, inktick, nibcaseMIT or Apache-2.0, at your option

The GNU General Public License, version 3 or later, is the Free Software Foundation’s text, unchanged. MIT and Apache-2.0 are the usual permissive licences; both let you use the code in anything, with the copyright notice kept.

What keeps its own licence🔗

PartLicence
Linux, with nibOS’s kernel patchesGPL-2.0
U-Boot, with nibOS’s patchesGPL-2.0-or-later
The RG DS+’s device treeGPL-2.0-or-later or MIT
Arch Linux ARM’s packagesEach its own, listed in the image’s packages.txt
Roboto Condensed, the font in DSlot and the menusSIL Open Font License 1.1
The system cards’ console photosPublic domain, or CC BY 4.0, credited on each card
The libretro cores nibcase playsEach its own: GPL-2.0, GPL-3.0 or Zlib, except Snes9x, FinalBurn Neo and PicoDrive (below)
nibOS’s PortMaster profileMIT, PortMaster’s own licence

Snes9x (the SNES), FinalBurn Neo (Arcade) and PicoDrive (the Mega Drive, Mega-CD, 32X and Pico) are each under their own non-commercial licence, so DSlot’s card image may not be sold, or passed on as part of anything sold. The image’s NOTICE says so. nibOS’s own image includes none of them.

Firmware🔗

Two pieces of firmware the RG DS+ needs aren’t free software. the card includes them unchanged, under licences that allow it, and lists them in every image’s NOTICE:

Not included🔗

The source🔗

Every image’s NOTICE gives the commit of each project in it and the written offer of the complete corresponding source for its GPL and LGPL parts, which is published beside each release. The repositories are on GitHub; each has its LICENSE and, where it builds in other people’s code, a list of it with its licences.

This site🔗

The site’s repository has the licence texts.