Home
last modified time | relevance | path

Searched refs:romfs (Results 26 – 50 of 624) sorted by relevance

12345678910>>...25

/dports/emulators/qemu42/qemu-4.2.1/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu/qemu-6.2.0/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu5/qemu-5.2.0/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-utils/qemu-4.2.1/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-powernv/qemu-powernv-3.0.50/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-guest-agent/qemu-5.0.1/roms/SLOF/board-qemu/llfw/
H A DMakefile23 STG1OBJ = startup.o version.o boot_abort.o romfs.o io_generic.o board_io.o
35 romfs.o: ../../llfw/romfs.S
36 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu60/qemu-6.0.0/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu42/qemu-4.2.1/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu/qemu-6.2.0/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu5/qemu-5.2.0/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-utils/qemu-4.2.1/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-powernv/qemu-powernv-3.0.50/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/qemu-guest-agent/qemu-5.0.1/roms/SLOF/board-js2x/llfw/
H A DMakefile23 STG1OBJ = startup.o boot_abort.o romfs.o hw.o io_generic.o board_io.o
37 romfs.o: ../../llfw/romfs.S
38 $(CC) $(CFLAGS) -c ../../llfw/romfs.S
/dports/emulators/yuzu/yuzu-0b47f7a46/src/core/file_sys/
H A Dpatch_manager.cpp354 auto extracted = ExtractRomFS(romfs); in ApplyLayeredFS()
402 romfs = std::move(packed); in ApplyLayeredFS()
416 if (romfs == nullptr) { in PatchRomFS()
417 return romfs; in PatchRomFS()
429 const auto new_nca = std::make_shared<NCA>(update, romfs, ivfc_offset); in PatchRomFS()
434 romfs = new_nca->GetRomFS(); in PatchRomFS()
441 romfs = new_nca->GetRomFS(); in PatchRomFS()
446 ApplyLayeredFS(romfs, title_id, type, fs_controller); in PatchRomFS()
448 return romfs; in PatchRomFS()
582 if (romfs == nullptr) { in ParseControlNCA()
[all …]
/dports/emulators/yuzu/yuzu-0b47f7a46/src/core/file_sys/system_archive/
H A Dsystem_archive.cpp86 const auto romfs = CreateRomFS(dir); in SynthesizeSystemArchive() local
88 if (romfs == nullptr) in SynthesizeSystemArchive()
92 return romfs; in SynthesizeSystemArchive()
/dports/misc/e2fsprogs-libblkid/e2fsprogs-1.46.5/lib/blkid/tests/
H A Dromfs.results1 TYPE='romfs'
2 LABEL='test-romfs'
/dports/misc/e2fsprogs-libuuid/e2fsprogs-1.46.5/lib/blkid/tests/
H A Dromfs.results1 TYPE='romfs'
2 LABEL='test-romfs'
/dports/sysutils/e2fsprogs/e2fsprogs-1.46.5/lib/blkid/tests/
H A Dromfs.results1 TYPE='romfs'
2 LABEL='test-romfs'
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/filesystems/
H A Dromfs.rst16 while romfs is less than a page, about 4000 bytes (assuming i586
21 with romfs, it needed 3079 blocks.
24 genromfs. It is available on http://romfs.sourceforge.net/
26 As the name suggests, romfs could be also used (space-efficiently) on
30 However, the main purpose of romfs is to have a very small kernel,
36 flash, but with romfs, you can even spare off your ext2 or minix or
49 romfs operates on block devices as you can expect, and the underlying
145 Another thing to note is that romfs works on file headers and data
155 alarmed, I'm not getting that much romfs related mail. Now I can
159 romfs has also a mailing list, and to date, it hasn't received any
[all …]
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/filesystems/
H A Dromfs.rst16 while romfs is less than a page, about 4000 bytes (assuming i586
21 with romfs, it needed 3079 blocks.
24 genromfs. It is available on http://romfs.sourceforge.net/
26 As the name suggests, romfs could be also used (space-efficiently) on
30 However, the main purpose of romfs is to have a very small kernel,
36 flash, but with romfs, you can even spare off your ext2 or minix or
49 romfs operates on block devices as you can expect, and the underlying
145 Another thing to note is that romfs works on file headers and data
155 alarmed, I'm not getting that much romfs related mail. Now I can
159 romfs has also a mailing list, and to date, it hasn't received any
[all …]
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/filesystems/
H A Dromfs.rst16 while romfs is less than a page, about 4000 bytes (assuming i586
21 with romfs, it needed 3079 blocks.
24 genromfs. It is available on http://romfs.sourceforge.net/
26 As the name suggests, romfs could be also used (space-efficiently) on
30 However, the main purpose of romfs is to have a very small kernel,
36 flash, but with romfs, you can even spare off your ext2 or minix or
49 romfs operates on block devices as you can expect, and the underlying
145 Another thing to note is that romfs works on file headers and data
155 alarmed, I'm not getting that much romfs related mail. Now I can
159 romfs has also a mailing list, and to date, it hasn't received any
[all …]
/dports/net/libwebsockets/libwebsockets-v4.2.2/scripts/
H A Desp32.mk39 genromfs -f $(LWS_BUILD_PATH)/romfs.img -d $(PROJECT_PATH)/romfs-files ; \
40 RLEN=$$($$GNUSTAT -c %s $(LWS_BUILD_PATH)/romfs.img) ;\
47 cat $(LWS_BUILD_PATH)/romfs.img >> $(LWS_BUILD_PATH)/$(PROJECT_NAME).bin ; \
/dports/games/libretro-scummvm/scummvm-7b1e929/backends/platform/n64/
H A DREADME.N6424 and a romfs image, containing game datafiles and other useful data.
25 Prebuilt binaries needs to be joined with a romfs image containing datafiles
28 To generate a romfs image under linux/unix you need 'genromfs' tool from
29 http://romfs.sourceforge.net/, create a directory, copy game data inside,
30 and then generate the romfs image.
106 'vkeybd_default.zip' in the root of your romfs image.
/dports/games/scummvm/scummvm-2.5.1/backends/platform/n64/
H A DREADME.N6424 and a romfs image, containing game datafiles and other useful data.
25 Prebuilt binaries needs to be joined with a romfs image containing datafiles
28 To generate a romfs image under linux/unix you need 'genromfs' tool from
29 http://romfs.sourceforge.net/, create a directory, copy game data inside,
30 and then generate the romfs image.
106 'vkeybd_default.zip' in the root of your romfs image.
/dports/net/libwebsockets/libwebsockets-v4.2.2/lib/misc/
H A Dromfs.h60 romfs_get_info(romfs_t romfs, const char *path, size_t *len, size_t *csum);
62 romfs_mount_check(romfs_t romfs);

12345678910>>...25