Talk:IOS

From WiiBrew
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Descriptions

I think that we should add something about how the Broadway code interacts with the IOS on this page, like describing the basic methods of communication and so on.--henke37 04:15, 17 February 2008 (PST)

Useful info

I find a huge lack of usable information here. So what if there is a IOS_FOOBAR function? We don't know what it does or how to properly use it. I only request that any further edits to the related pages tries to at the very minimum list these things:

  • Name of the call
  • What it does
  • Indata
    • Format
    • Use
  • Outdata
    • Format
    • Use
  • Usage rules, like things that may not be done

Yes, I do know that not everything is known, but seriously, the information that I list is known for some things, just not on the wiki. I sugest that we move the information from the wiki into an application designed to track APIs, in order to make these things easier to be done right. --henke37 11:43, 16 March 2008 (PDT)

  • I think the basic idea behind pages like this is that if you're one of the developers who are going to be working with/improving these functions, you'll already understand them, and just need these references. These IOS functions are not final, it seems, and many of them won't necessarily be interacted with by the average developer once libogc is completed for Wii. If libogc and functions like these weren't being so actively updated and developed, it might make sense for these guys to stop and document them more, but these are really just being assimilated into better libogc/devkitpro code, which is what is really going to need documenting in the end, and I'm not sure Wiibrew is the place for that information. ProdigySim 20:13, 16 March 2008 (PDT)
Pretty much. Reverse-engineering IOS is a year-long project; we're using Wiibrew as a place to take notes. Bushing 10:54, 16 June 2008 (CEST)

All the numbers

Where do the numbers come from? What does the 254 in IOS254 mean? —Preceding unsigned comment added by Mpg187 (talkcontribs) 03:38, 1 December 2010 (UTC)

It means the IOS is installed to slot 254. There are 255 IOS "slots", because 255 = 0xFF in Hex (the highest two digit number in Hex). An IOS can be installed to any of these "slots". --SifJar 12:44, 1 January 2010 (UTC)

Standby mode

Does IOS launch boot2 after exiting standby, or does it completely reboot? BootMii still loads for me when I press the power button in standby mode. Hallowizer (talk) 19:07, 26 May 2021 (CEST)

IPC

What are async1, async2, and relaunch? Hallowizer (talk) 01:41, 27 May 2021 (CEST)

i don't know about async1 & 2 (can't find anything about them atm), but afaik the relaunch parameters is to tell ios how to launch the title you want to launch. for example, background is used for (re)loading ios, foreground is for launching titles like channels. you can do more than that afaik, but thats the most obvious difference. DacoTaco (talk) 07:04, 27 May 2021 (CEST)

Viper

According to HackMii, older IOSes have “Viper” in their build tags. Bushing seems to think Viper means Starlet, but I think it might actually mean IOS, since boot2 and MIOS are also considered IOSes internally, but have no signs or Viper. Hallowizer (talk) 04:53, 8 August 2021 (CEST)

I'm only guessing as much as the rest, but since the build tag says 'fw.RVL.12.0.6.viper.0611041415' etc etc , i also assume viper is the starlet as that build tag says firmware revolution 12.0.6 (viper) (and i assumed it was build on 6/11/2004 @ 14:15 ). however, the question is indeed if viper here means 'firmware for the viper cpu' or 'firmware for the viper subsystem'. my money is on viper being the cpu, but it was probably renamed afterwards, as later updates & versions have dropped the whole 'revolution' bit all together. maybe Pokechu22 knows something? DacoTaco (talk) 11:58, 8 August 2021 (CEST)