summaryrefslogtreecommitdiff
path: root/target/config/Config.in.rootfs
AgeCommit message (Collapse)Author
2022-12-26use mmcblk0 for rootfs on rockpi4-plusWaldemar Brodkorb
2022-09-22add support for STM32F746G-DISCO deviceWaldemar Brodkorb
Tested with toolbox / simpleinit as userland. FDPIC/FLAT support both successfully tested. No LCD or Ethernet support.
2022-02-27sipeed-maix-bit: finetune, kernel boots, but helloworld segfautsWaldemar Brodkorb
2022-02-26riscv64: add support for nommu target systemsWaldemar Brodkorb
2022-02-15remove virtualbox supportWaldemar Brodkorb
2020-03-24usb rootfs needs filesystem ext4 to bootWaldemar Brodkorb
2019-09-30remove unfinished alternative os porting effortsWaldemar Brodkorb
2018-06-22linux+arc: update kernelWaldemar Brodkorb
2018-06-20foxboard: bugfixesWaldemar Brodkorb
2018-05-19genimage disk images are only available for x86_64 for nowWaldemar Brodkorb
2018-03-07add support for walduxWaldemar Brodkorb
2018-02-12hppa: add basic qemu supportWaldemar Brodkorb
2017-12-31dec-multia: make netboot possible, add aboot bootloaderWaldemar Brodkorb
2017-12-10allow USB boot for generic targetsWaldemar Brodkorb
2017-04-14remove arm foundation model sample, bit rotted. better use qemu sample for ↵Waldemar Brodkorb
aarch64
2017-04-14remove sim-or1k sample, bit rotted. better use qemu sample for or1kWaldemar Brodkorb
2017-03-17drop yaffs2 supportWaldemar Brodkorb
Yaffs2 is not upstream and does not work with newer 4.x Linux kernels. We like to switch to UBIFS for any embedded devices with NAND. Routerboards can be used with some application, which generates a YAFFS2 image including a Linux kernel, without any YAFFS2 filesystem support in the kernel on the host or target.
2017-03-17Implement UBIFS rootfs supportPhil Sutter
This implements UBIFS rootfs, enables it for mips targets and adds the necessary settings for rb532. Signed-off-by: Phil Sutter <phil@nwl.cc>
2017-03-17target: ADK_TARGET_ROOTFS_GENIMAGE fails without ADK_TARGET_QEMU_WITH_BOOTLOADERPhil Sutter
Therefore make the former select the latter. Signed-off-by: Phil Sutter <phil@nwl.cc>
2017-02-23rework firmware menu, we need to add some more options for images/filesystemWaldemar Brodkorb
2017-02-22raspberry-pi3: fix mini.config bootupWaldemar Brodkorb
- cmdline.txt is not required with full device tree capable kernel - force 270x option for mkknlimg trailer - we need ext4 filesystem support in the kernel other filesystems are rarely used at the moment - ATAGS and CMDLINE_FROM_BOOTLOADER not required with device tree capable kernel - overlay dtb files are renamed to dtbo suffix
2017-02-17select grub/grub-tools for dual-boot and x86/x86_64 architectureWaldemar Brodkorb
2017-02-09add basic support for edosk2674Waldemar Brodkorb
2017-02-09add dual-boot / fwupdate for systems with grub-supportWaldemar Brodkorb
2017-02-06add different genimage configs for PC Bios and EFIWaldemar Brodkorb
2016-11-28cleanup kernel rootfs choice, it is not well tested to use non-ext4 rootfs, ↵Waldemar Brodkorb
add a linux kernel submenu
2016-11-21or1k: rename or1k-sim to sim-or1k, by default 64mb ramWaldemar Brodkorb
2016-11-03qemu flash filesystem needs driversWaldemar Brodkorb
2016-10-23add target support for SGI O2 workstationWaldemar Brodkorb
2016-10-14nds32: ext4 does not compile, disable this rootfs for nowWaldemar Brodkorb
2016-09-10genimage: add better supportWaldemar Brodkorb
2016-09-05add some basic genimage supportWaldemar Brodkorb
2016-07-10nslu2: fix boot (initramfs via tftp tested)Waldemar Brodkorb
2016-07-10add back some basic support for Foxboard-LX832Waldemar Brodkorb
2016-03-25simplify qemu options, hide block choiceWaldemar Brodkorb
2016-03-12default to initramfs+piggyback for qemu/gdb simWaldemar Brodkorb
2016-03-10make parts of the menu visible if architecture is choosen to guarentee ↵Waldemar Brodkorb
defaults are set right
2016-03-07rework menu based config systemWaldemar Brodkorb
After the addition of bare metal toolchains the menu system allowed to create non-valid configurations. I reworked it so we can also add other operating system support if we wish. So first you choose your operating system, then your architecture and endianess, after that your embedded system, emulator or generic device and then you choose your task you want to run. Tasks may be toolchain, a new appliance/application or some preconfigured sets of packages and configurations as kodi, mpd, firefox and more. The tasks are limited to a plausible choice of hardware and software. Deduplicate CPU configuration. You don't wanna compile Kodi for a H8/300 microcontroller ;)
2015-12-26split rootfs options from target configWaldemar Brodkorb