Void Linux on Raspberry Pi Zero
https://forums.raspberrypi.com/viewto...
I extracted the img.xz and installed it With Raspi OS Imager
void-rpi-armv6l-20221001.img.xz 73030612
void-rpi-armv6l-PLATFORMFS-20221001.tar.xz 70653788
I haven't tried musl
void-rpi-armv6l-musl-20221001.img.xz 61741128
void-rpi-armv6l-musl-PLATFORMFS-20221001.tar.xz 60669816
https://alpha.de.repo.voidlinux.org/l...
https://www.linuxquestions.org/questi...
From a 2004 mailing list:
https://www.spinics.net/lists/usb/msg... this seems to cause my issue with Rpi Zero USB OTG and Belkin hub
"The "old scheme" is the way Linux worked before 2.6.10. When a new device is plugged in, the system first assigns it an address, then reads the
initial 8 bytes of the device descriptor, then reads the entire 18-byte
device descriptor.
The "new scheme" is basically the way Windows works. (Not surprisingly,
some devices won't work any other way.) When a new device is plugged in, the system first issues a 64-byte read request for the device descriptor,
then resets the device, then assigns it an address, and then reads the
actual 18-byte device descriptor.
The reason for these shenanigans is that with a full-speed device, the
maximum packet size for endpoint 0 (ep0maxpacket) isn't known beforehand.
It could be 8, 16, 32, or 64 bytes. (Low-speed devices must use 8, and
high-speed devices must use 64.) The ep0maxpacket value is stored in the initial 8 bytes of the device descriptor, but to read the device
descriptor you have to use endpoint 0!
The two schemes above are the two common solutions to this chicken-and-egg problem. The old scheme is the one recommended by the USB Implementors Forum (which makes it the "Standard"); the new scheme is the one used by Microsoft (which makes it another kind of "Standard"!). A well-designed standards-compliant device will work okay with either scheme.
Unfortunately it seems that no matter which scheme you pick, some
badly-designed non-compliant devices won't work. There's an additional
usbcore.ko module parameter people can use in especially bad cases:
use_both_schemes=y
This will cause the system to try one of the schemes, and if it fails then
try the other scheme. (Maybe that should always be the default...)"