[MCMAN] different return value compared to sce modules. why? about ps2sdk HOT 2 OPEN

Are you aware that the design of MCMAN and various SDK modules may have changed between SDK versions? I guess, such a change in semantics may be the result of the SDK being of a different version.

The original PlayStation 2 boot ROM module set was roughly equivalent to 1.3.4. For backward-compatibility, no changes were made to the basic module set (i.e. rom0:MCMAN). The X, P or T modules are usually related to some other app, such as the OSD. Which may be built with a newer SDK. And as such, they reboot the IOP with an command that targets an IOPRP image containing IOPBTCONF that lists the new modules. These modules may not be of the exact same versions, between consoles.

I forgot which MCMAN module Jimmikaelkael based this MCMAN on. But you should try to refer to a module that is as similar to the one used.

from ps2sdk.

Are you aware that the design of MCMAN and various SDK modules may have changed between SDK versions? I guess, such a change in semantics may be the result of the SDK being of a different version.

The original PlayStation 2 boot ROM module set was roughly equivalent to 1.3.4. For backward-compatibility, no changes were made to the basic module set (i.e. rom0:MCMAN). The X, P or T modules are usually related to some other app, such as the OSD. Which may be built with a newer SDK. And as such, they reboot the IOP with an command that targets an IOPRP image containing IOPBTCONF that lists the new modules. These modules may not be of the exact same versions, between consoles.

I forgot which MCMAN module Jimmikaelkael based this MCMAN on. But you should try to refer to a module that is as similar to the one used.

I asked because I see the -46 value commented there. Just curiosity,

from ps2sdk.