NetBSD - Revision history

Techflash: Linux doesn't do sw color conversion anymore

2026-10-18T00:00:54Z

Linux doesn't do sw color conversion anymore

← Older revision		Revision as of 00:00, 18 October 2026
Line 13:		Line 13:
	* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.		* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.

	* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX\|GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux ~~does~~ this via software math. ~~Both~~ approaches have similar performance.		* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX\|GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux previously did this via software math. Those 2 approaches have similar performance. Modern Linux versions, however, do this by exposing the RGB linear framebuffer as GX tiled texture, then using an indirect texture to remap the output to appear correct after rendering into the EFB, and thus appearing correct on the display after copying out to the XFB (also using GX).
	* Wii-Linux has more complete hardware support in some areas:		* Wii-Linux has more complete hardware support in some areas:
	** Recent versions of Wii-Linux present the EXI bus as SPI, allowing the use of SPI drivers (most notably using the mmc-spi driver for SD Gecko support). NetBSD has a bespoke SPI stack, with driver support limited to the RTC and the USB Gecko.		** Recent versions of Wii-Linux present the EXI bus as SPI, allowing the use of SPI drivers (most notably using the mmc-spi driver for SD Gecko support). NetBSD has a bespoke SPI stack, with driver support limited to the RTC and the USB Gecko.

Techflash: correct memory claim

2026-10-17T23:57:43Z

correct memory claim

← Older revision		Revision as of 23:57, 17 October 2026
Line 6:		Line 6:
	* [[Wii-Linux]] is launched from [[BootMii]] via [[Gumboot]] or [[NPLL]]. NetBSD is started from the [[Homebrew Channel]], or, as of NetBSD 11.0, from BootMii via a NetBSD-specific bootloader.		* [[Wii-Linux]] is launched from [[BootMii]] via [[Gumboot]] or [[NPLL]]. NetBSD is started from the [[Homebrew Channel]], or, as of NetBSD 11.0, from BootMii via a NetBSD-specific bootloader.

	* When NetBSD starts from the Homebrew Channel, it can only use MEM2. Wii-Linux is able to use ~~part~~ of ~~MEM1 as system RAM~~, as can NetBSD if started from BootMii.		* When NetBSD starts from the Homebrew Channel, it can only use MEM1 and part of MEM2, since IOS reserves the upper 12MB. Wii-Linux is able to use all of MEM2, as can NetBSD if started from BootMii.
	* NetBSD's init system is ''much'' simpler and lighter than systemd.		* NetBSD's init system is ''much'' simpler and lighter than systemd.

Waterpear: update for 11.0; more detailed hardware support comparison

2026-10-17T23:23:43Z

update for 11.0; more detailed hardware support comparison

← Older revision		Revision as of 23:23, 17 October 2026
Line 1:		Line 1:
	{{seealso\|[https://netbsd.org/ Official NetBSD Website]}}		{{seealso\|[https://netbsd.org/ Official NetBSD Website]}}

	'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.		'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform, with further enhancements to hardware support added in version 11.0.

	=== Comparison with Wii-Linux ===		=== Comparison with Wii-Linux ===
			* [[Wii-Linux]] is launched from [[BootMii]] via [[Gumboot]] or [[NPLL]]. NetBSD is started from the [[Homebrew Channel]], or, as of NetBSD 11.0, from BootMii via a NetBSD-specific bootloader.

	* ~~[[Wii-Linux]] is launched~~ from ~~boot2 via [[Gumboot]] or [[NPLL]]. While NetBSD has boot2 support in the current branch, as of May 2025, release builds are started via~~ the Homebrew Channel.		* When NetBSD starts from the Homebrew Channel, it can only use MEM2. Wii-Linux is able to use part of MEM1 as system RAM, as can NetBSD if started from BootMii.
			* NetBSD's init system is ''much'' simpler and lighter than systemd.
	* Wii-Linux is able to use part of MEM1 as system RAM, ~~while~~ NetBSD ~~only seems to use MEM2~~. ~~Hence, a Wii-Linux system has access to more RAM. (This is somewhat mitigated by the~~ NetBSD init system ~~being~~ ''much'' simpler than systemd.)

	* The Wii-Linux [[ArchPOWER]] image has better menu-driven configuration tools. While NetBSD's <code>sysinst</code> can be used for tasks like network configuration, it is not as easy to use as tools like <code>nmtui</code> or [[ConfigMii]].		* The Wii-Linux [[ArchPOWER]] image has better menu-driven configuration tools. While NetBSD's <code>sysinst</code> can be used for tasks like network configuration, it is not as easy to use as tools like <code>nmtui</code> or [[ConfigMii]].

	* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.		* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.

	* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.

	* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX\|GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.		* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX\|GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.
			* Wii-Linux has more complete hardware support in some areas:
	* As of ~~May 2025~~, ~~NetBSD doesn't have~~ drivers for [[GameCube Controller]] ~~or the~~ [[~~USB Gecko~~]], ~~and the~~ driver for the ~~internal~~ Wi-Fi ~~adapter~~ is not ~~yet available in release builds~~.		** Recent versions of Wii-Linux present the EXI bus as SPI, allowing the use of SPI drivers (most notably using the mmc-spi driver for SD Gecko support). NetBSD has a bespoke SPI stack, with driver support limited to the RTC and the USB Gecko.
			** Because NetBSD has no general "game pad" or "joystick" input abstraction, the [[Hardware/Serial Interface\|SI]] driver simulates a USB hub and presents [[GameCube Controller\|GameCube controllers]] as USB game controllers.
			** NetBSD has no [[GameCube]] support whatsoever.
			* NetBSD has superior hardware support in other areas:
			** There seems to be a wider array of USB drivers enabled in NetBSD, so many devices will work on NetBSD but not Linux.
			** The NetBSD driver for the Wii's [[Wii Hardware/BCM4318\|BCM4318]] Wi-Fi has been reported to be faster and more stable than Linux's driver (although performance is still not good.)
			** NetBSD has support for Hollywood's AES engine. Allegedly, this is used for accelerating WPA as well as disk encryption.

Techflash: update seealso usage

2026-07-29T22:53:16Z

update seealso usage

← Older revision		Revision as of 22:53, 29 July 2026
Line 1:		Line 1:
	{{seealso\|https://netbsd.org/ Official NetBSD Website}}		{{seealso\|[https://netbsd.org/ Official NetBSD Website]}}

	'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.		'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.

Tech64DD: add link to official website

2026-07-15T13:53:11Z

add link to official website

← Older revision		Revision as of 13:53, 15 July 2026
Line 1:		Line 1:
			{{seealso\|https://netbsd.org/ Official NetBSD Website}}

	'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.		'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.

Techflash: dang formatting, grrr

2026-07-15T13:30:11Z

dang formatting, grrr

← Older revision		Revision as of 13:30, 15 July 2026
Line 13:		Line 13:
	* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.		* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.

	* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.		* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX\|GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.

	* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.		* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.

Techflash: fix GX link (oops)

2026-07-15T13:29:35Z

fix GX link (oops)

← Older revision		Revision as of 13:29, 15 July 2026
Line 13:		Line 13:
	* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.		* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.

	* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.		* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[Hardware/GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.

	* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.		* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.

Techflash: Links, note the GX color conversion, note that mainline Wii-Linux has about-as-good USB

2026-07-15T13:26:22Z

Links, note the GX color conversion, note that mainline Wii-Linux has about-as-good USB

← Older revision		Revision as of 13:26, 15 July 2026
Line 1:		Line 1:
	'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the Wii as a first class platform.		'''NetBSD''' is one of the BSD operating systems, descended from the Berkeley System Distribution. Starting with version 10.0, NetBSD supports the [[Wii]] as a first class platform.

	=== Comparison with Wii-Linux ===		=== Comparison with Wii-Linux ===

	* Wii-Linux is launched from boot2 via Gumboot. While NetBSD has boot2 support in the current branch, as of May 2025, release builds are started via the Homebrew Channel.		* [[Wii-Linux]] is launched from boot2 via [[Gumboot]] or [[NPLL]]. While NetBSD has boot2 support in the current branch, as of May 2025, release builds are started via the Homebrew Channel.

	* Wii-Linux is able to use part of MEM1 as system RAM, while NetBSD only seems to use MEM2. Hence, a Wii-Linux system has access to more RAM. (This is somewhat mitigated by the NetBSD init system being ''much'' simpler than systemd.)		* Wii-Linux is able to use part of MEM1 as system RAM, while NetBSD only seems to use MEM2. Hence, a Wii-Linux system has access to more RAM. (This is somewhat mitigated by the NetBSD init system being ''much'' simpler than systemd.)

	* The Wii-Linux ArchPOWER image has better menu-driven configuration tools. While NetBSD's <code>sysinst</code> can be used for tasks like network configuration, it is not as easy to use as tools like <code>nmtui</code> or [[ConfigMii]].		* The Wii-Linux [[ArchPOWER]] image has better menu-driven configuration tools. While NetBSD's <code>sysinst</code> can be used for tasks like network configuration, it is not as easy to use as tools like <code>nmtui</code> or [[ConfigMii]].

	* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.		* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.

	* USB ~~support~~ in NetBSD ~~seems~~ to ~~be more complete and less buggy. Many common USB networking devices that aren't supported or don't work with~~ the Wii-Linux kernel ~~will operate just fine in~~ NetBSD.		* USB used to be more stable in NetBSD compared to Wii-Linux, but as of the mainline Wii-Linux kernel's release, USB should be about as stable as NetBSD.

	* The framebuffer driver in Wii-Linux emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's ~~YUV~~ framebuffer. NetBSD's driver does ~~not~~, ~~preferring to perform the color transformation~~ in ~~the X.org server.~~		* The framebuffer driver in both Wii-Linux and NetBSD emulates RGB colors, so graphical software doesn't have to be rewritten for the Wii's YUYV framebuffer. NetBSD's driver does this via the [[GX]] GPU, using a scratch framebuffer in memory, copying into the EFB (via the CPU) every frame, and then using GX to do the conversion + copy back to the XFB. Linux does this via software math. Both approaches have similar performance.
	** As a consequence, the ~~color palette for~~ the ~~text-mode console has many incorrect colors~~, ~~which makes a lot of text-mode screens hard~~ to ~~read~~.

	* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.		* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.

Techflash: proper formatting for commands

2025-05-05T16:10:45Z

proper formatting for commands

← Older revision		Revision as of 16:10, 5 May 2025
Line 7:		Line 7:
	* Wii-Linux is able to use part of MEM1 as system RAM, while NetBSD only seems to use MEM2. Hence, a Wii-Linux system has access to more RAM. (This is somewhat mitigated by the NetBSD init system being ''much'' simpler than systemd.)		* Wii-Linux is able to use part of MEM1 as system RAM, while NetBSD only seems to use MEM2. Hence, a Wii-Linux system has access to more RAM. (This is somewhat mitigated by the NetBSD init system being ''much'' simpler than systemd.)

	* The Wii-Linux ArchPOWER image has better menu-driven configuration tools. While NetBSD's `sysinst` can be used for tasks like network configuration, it is not as easy to use as tools like `nmtui` or [[ConfigMii]].		* The Wii-Linux ArchPOWER image has better menu-driven configuration tools. While NetBSD's <code>sysinst</code> can be used for tasks like network configuration, it is not as easy to use as tools like <code>nmtui</code> or [[ConfigMii]].

	* NetBSD's package manager is not included as part of the base system, and has to be installed using `sysinst`.		* NetBSD's package manager is not included as part of the base system, and has to be installed using <code>sysinst</code>.

	* USB support in NetBSD seems to be more complete and less buggy. Many common USB networking devices that aren't supported or don't work with the Wii-Linux kernel will operate just fine in NetBSD.		* USB support in NetBSD seems to be more complete and less buggy. Many common USB networking devices that aren't supported or don't work with the Wii-Linux kernel will operate just fine in NetBSD.

Waterpear: GaMeCuBe

2025-05-05T16:09:08Z

GaMeCuBe

← Older revision		Revision as of 16:09, 5 May 2025
Line 16:		Line 16:
	** As a consequence, the color palette for the text-mode console has many incorrect colors, which makes a lot of text-mode screens hard to read.		** As a consequence, the color palette for the text-mode console has many incorrect colors, which makes a lot of text-mode screens hard to read.

	* As of May 2025, NetBSD doesn't have drivers for [[~~Gamecube~~ Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.		* As of May 2025, NetBSD doesn't have drivers for [[GameCube Controller]] or the [[USB Gecko]], and the driver for the internal Wi-Fi adapter is not yet available in release builds.