- Contentless support and populated content paths are not mutually exclusive in practice - It just looked that way because most cores that support contentless mode to date don't use softpatching very much
This commit is contained in:
parent
0f4166a59f
commit
1b03e388f8
|
@ -4256,12 +4256,9 @@ static bool event_init_content(
|
||||||
|
|
||||||
content_set_subsystem_info();
|
content_set_subsystem_info();
|
||||||
|
|
||||||
/* If core is contentless, just initialise SRAM
|
|
||||||
* interface, otherwise fill all content-related
|
|
||||||
* paths */
|
|
||||||
if (flags & CONTENT_ST_FLAG_CORE_DOES_NOT_NEED_CONTENT)
|
if (flags & CONTENT_ST_FLAG_CORE_DOES_NOT_NEED_CONTENT)
|
||||||
runloop_path_init_savefile_internal(runloop_st);
|
runloop_path_init_savefile_internal(runloop_st);
|
||||||
else
|
|
||||||
runloop_path_fill_names();
|
runloop_path_fill_names();
|
||||||
|
|
||||||
if (!content_init())
|
if (!content_init())
|
||||||
|
|
Loading…
Reference in New Issue