Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Adorable-Catgirl

Members
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Adorable-Catgirl

  1. .efi2 could probably be a CPIO archive. Entry point can be defined by a .cfg file in the root of the archive. Or, we could also check if it's a CPIO file or a Lua file. Dunno, it's up to you.
  2. uncpio is a rather simple binary CPIO extractor (File begins with 0x71C7 or 0xC771, made with cpio -oHbin). To acquire uncpio, run pastebin get YbrVjRwa /bin/uncpio.lua To use, make the directory you'll be extracting your CPIO archive to, cd into it, then run uncpio path/to/your/file.cpio And it will extract to the current directory. Currently only works in OpenOS, as far as I know.
  3. Fair. Also, we could use binary CPIO for bootable packages. That would probably be the best bet. It's standard and been around for a while. Also, OEFI v2 applications should end in `.efi2` to differentiate them from the OEFI v1 applications. OEFI v2 applications should also probably support a few basic arguments.
  4. So, some recommendations for OEFI v2: Storage of addresses in a binary format Maybe a standard set of commands for an OEFI shell? "oefi.loadfile(path)", which loads a file from the boot device Vendor prefixes on extensions to OEFI (ie "oefi.vendor.extensionmethod()") BIOS configuration space of 64 bytes, at the end of the EEPROM Maybe a network boot protocol? The OEFI library should be global unless booting in compatibility mode (for example, from an init.lua file) OEFI implementation must allow the OS to return Standard for passing kerne
  5. (Shoot me if this is a necropost) Zorya has been updated! It now has a new, fancy installer that may still be visually buggy. It installs Zorya fine enough though. (And I plan to use it for my OS's installer.) Zorya 1.0 adds a few new features: OEFI support A new `zorya` library General improvements over 0.1. It's a feature, trust me. https://github.com/Adorable-Catgirl/Zorya-BIOS
  6. I'm using ocvm. I mainly use it because OCEmu has some weird issues, though ocvm seems to have some strange issues too.
  7. I was thinking about component IDs. Shouldn't they be minified? Like, "68ca0f59-ac2c-49f8-ba6a-3c4c7e5f069b" turns into a string of 16 bytes: {0x68, 0xCA, 0x0F, 0x59, 0xAC, 0x2C, 0x49, 0xF8, 0xBA, 0x6A, 0x3C, 0x4C, 0x7E, 0x5F, 0x06, 0x9B} Also, OEFI implementations need to have room for custom configuration, as something like Zorya needs some EEPROM space for knowing the device that the "zorya-module" and "zorya-cfg" folders are stored on. Maybe 64 bytes or so can be dedicated to custom config? 64 bytes should be plenty of space for basic configuration, yeah? 32 bytes would be too littl
  8. Also, I plan on adding DEFLATE support for URF and support for PolarisFS (From an OS I'm working on, Tsuki) if/when I get the chance.
  9. Sorry about that, haha. Feels free to help revise it. I just haven't worked on any OC stuff in a while.
  10. Ay, so I made a Zorya module for booting Fuchas. Pastebin is 3gpLaRpq Currently, it doesn't support passing arguments. It shouldn't be hard to add that, though.
  11. Yea, no problem. I'll also probably add the option to make the zorya-modules and zorya-config folders part of the normal filesystem. Might change how Zorya stores options to specify if it should download the modules or load them from the github repo. But I'll have to test that on my PC since OCEmu locks up when I try to fetch things from HTTPS
  12. Ah, I see. I'll probably combine a few of the files together, yeah. I do want to still have it load modules from zorya-modules, just to make it simple to drop a loader in. I have some things to add and fix for Zorya 0.2 but I'll do that for the next release.
  13. Ah, I would, but I wanted to make the BIOS simple to extend (and patch).
  14. this is just a draft, feel free to suggest whatever. URF v1.1 Abstract This document describes the URF, intended to make mass file exchange easier. Rationale There are many competing methods of exchanging large amounts of files, and many are incomplete, such as TAR implementations, or proprietary, such as NeoPAKv1. With this in mind, a standard format will make file exchange less error prone. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be inte
  15. Zorya BIOS Zorya BIOS is an extendable and configurable BIOS and bootloader, capable of booting any OS with the right extensions. It's similar to GRUB. (sorry in advance for bios.lua) All you need to install the BIOS is to flash bios.lua to a blank EEPROM, insert a blank floppy, then reboot. Note: This has only been tested on Tier 3 hardware and Lua 5.3. requires an Internet card. Github repo PRs are welcome! Future plans: Ability to load from non-managed disks (like disks formatted with msdosfs, etc) Make it easier to extend Clean up code
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.