Philip Howard
Philip Howard
I had to do an emergency migration from AWS to GitHub pages a while back, and decided to stick with pages since it drastically simplifies my stack and workflow. However,...
Add an new "supported:" property to overlay pins in order to declare which Pi versions this feature is supported on.
The interface pages badly need an overhaul, they've broadly had the same text since they were originally created and it tends to waffle about devices I was playing with at...
As mentioned in #320 the pinout graphic needs some indication of how its orientation corresponds to the Raspberry Pi. Additionally it might be nice to produce a vertical version of...
I think it's clear an explicit list of included overlays is probably unmaintainable madness at this point. See: https://github.com/Gadgetoid/Pinout.xyz/blob/master/src/en/settings.yaml#L13-L140 I'd like to deprecate this explicit list in favour of simply...
In an effort to keep track of HATs, pHATs and Rasperry Pi add-ons which have not yet been documented on Pinout.xyz I'm compiling a - probably not - comprehensive list...
Overlays with translated types currently break, since they're not in the built-in allowed list of the `sanitize_types` function. EG: ``` Tutti autre moteur com. a/n htr lcd cap. e/s hepsi...
Because our (Pimoroni's) HATs are designed to allow the EEPROM to be programmed directly from a Pi (to save pain and time while testing), they tend to have an EEPROM...
After some discussion with Mike at Pi-Top, he's convinced me that there's a sound case for adding the rest of Pi-Top's lineup to Pinout.xyz. Since Pi-Top add-ons using the rail...
I've noticed when editing some definition files that there's a bit of repetition coming in for, in particular, PCM/I2S pin naming. Having to either ignore names, or individually name each...