this post was submitted on 26 Mar 2024
638 points (96.4% liked)

linuxmemes

19717 readers
328 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith
Linuxmemed
Geert
638
What is the most difficult problem that you have fixed in linux? (lemmy.world)
submitted 3 months ago by Waffelson to c/linuxmemes
166 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] poopsmith 8 points 3 months ago* (last edited 3 months ago)

Learned how drivers worked and fixed a driver for an USB to I2C chip. It's still buggy but at least it sorta works now.

Some more details: I was using a CH347 (USB to UART/SPI/I2C) and there was an open source driver that used a previous chip version. The original dev had hardcoded the bulk IO endpoints indices. The only change I had to do was just iterate over the endpoints and search for the correct ones. But at first, I didn't understand anything about how the USB subsystem worked and how drivers were loaded. All I could tell was the USB device was correctly detected but the I2C driver wasn't being loaded, despite proper udev rules, correct vendor/product IDs, etc.