Add 1209:4665 ferros (Nick Spiker)

[nickspiker]

Adds:

• org/nickspiker/ — organization page
• 1209/4665/ — ferros (open-source mobile OS in Rust)

ferros is licensed under Apache-2.0, with the LICENSE file in the source repository.

PID 0x4665 is the ASCII encoding of "Fe" — the chemical symbol for iron, etymological root of the project name, and a human-readable identifier in USB descriptor hex dumps.

[cnlohr]

I really don't quite understand what this is. For a project to be eligible for a PID code, it needs to have a embodiment. For instance schematic + board files, or if a commercial board custom firmware is loaded on an actual board.

[nickspiker]

The embodiment is custom firmware on a real board. ferros is a bare-metal OS (Rust, no Android/Linux underneath) and it brings up the SoC's USB device controller itself and enumerates as a vendor-specific bulk device for its host tooling.

It's currently running on a Pixel 8 Pro (Tensor G3) today. lsusb -v from a machine it's plugged into right now:

Bus 003 Device 012: ID 1209:4665 Nick Spiker ferros
Negotiated speed: High Speed (480Mbps)
bDeviceClass 255 Vendor Specific idVendor 0x1209 idProduct 0x4665
iManufacturer "Nick Spiker" iProduct "ferros"
Interface: Vendor Specific, 2 bulk endpoints (0x01 OUT, 0x81 IN)

The USB device stack is open (Apache-2.0), in Rust — the descriptor definitions and DWC3 device-mode driver are in the repo; happy to link the exact files. So it's "commercial board + custom firmware that enumerates," per the eligibility note. Let me know if you'd like anything else like a full descriptor tree, the driver source, or a photo of the device enumerated.

[cnlohr]

To clarify I meant it needs to have a hardware embodiment. It sounds like your embodiment is a Pixel 8 Pro?

And your software is the kernel and stack for the phone?

[nickspiker]

Yes to both.

Hardware embodiment: a Google Pixel 8 Pro (Tensor G3). Bootloader unlocked, ferros flashed to the boot partition and running in place of Android, with no Linux underneath. An Apple M1 MacBook Air (booted through m1n1) is the second target, currently in bring-up.

Software: ferros is the whole stack on the phone: a bare-metal Rust kernel that owns the USB device controller directly. It initialises the Tensor G3 eUSB2 PHY, drives the Synopsys DWC3 core in device mode, builds the descriptors and services EP0 plus the two bulk endpoints itself. That is the code presenting 1209:4665:

• DWC3 device-mode driver and descriptors: https://github.com/nickspiker/ferros/blob/forge/ferros_hal/src/usb.rs
• eUSB2 PHY bring-up (in kernel_main): https://github.com/nickspiker/ferros/blob/forge/ferros_kernel/src/main.rs
• M1 DWC3 port: https://github.com/nickspiker/ferros/blob/forge/ferros_hal_m1/src/usb.rs
• Host side that matches on the ID: https://github.com/nickspiker/ferros/tree/forge/tools/ferros-bridge

On the software-only question from the howto: the PID identifies the OS itself, the same way the Cupkee and PunchBOOT entries do. Every device running ferros enumerates with it and the host tooling matches on it. End users install ferros onto a phone; they don't build a USB device, so per-user PIDs wouldn't fit.

I've updated the PID page in this PR to spell out the hardware embodiment and the USB stack. Happy to add a photo of the enumerated device or a full descriptor dump if that helps.