htc: disable socket driver, needs design thought before we can turn it on for real.

This commit is contained in:
Michael Scire 2021-02-24 04:05:45 -08:00 committed by SciresM
parent d8faa37de0
commit 953246a175
2 changed files with 10 additions and 2 deletions

View file

@ -38,7 +38,7 @@ namespace ams::htclow::driver {
/* Declare the memory pool. */
alignas(RequiredAlignment) constinit u8 g_driver_memory[RequiredSize];
constexpr inline const socket::SystemConfigDefault SocketConfig(g_driver_memory, RequiredSize, SocketAllocatorSize);
constexpr inline const socket::SystemConfigDefault SocketConfig(g_driver_memory, RequiredSize, SocketAllocatorSize, 2);
}

View file

@ -203,7 +203,15 @@ namespace ams::htc {
} else if (std::strstr(transport, "socket")) {
/* NOTE: Nintendo does not actually allow socket driver to be selected. */
/* Should we disallow this? Undesirable, because people will want to use docked tma. */
return htclow::impl::DriverType::Socket;
/* TODO: Right now, SocketDriver causes a hang on init. This is because */
/* the socket driver requires wi-fi, but wi-fi can't happen until the system is fully up. */
/* The system can't initialize fully until we acknowledge power state events. */
/* We can't acknowledge power state events until our driver is online. */
/* Resolving this chicken-and-egg problem without compromising design will require thought. */
//return htclow::impl::DriverType::Socket;
return DefaultHtclowDriverType;
} else {
return DefaultHtclowDriverType;
}