Posts by 23n27@dgc.social
 (DIR) Post #B4KRgIasnlFBMIlZ1E by 23n27@dgc.social
       2 likes, 0 repeats
       
       @domi https://isaacfreund.com/blog/river-window-management/ was making the rounds recently and I'm so glad somebody is finally fixing this
       
 (DIR) Post #B5Z2SDsXzxtezy8NkW by 23n27@dgc.social
       0 likes, 0 repeats
       
       @mntmn The closest thing I know is https://github.com/adamgreen/mri, but that's a GDB stub, not interactive
       
 (DIR) Post #B6GDAcP5WxYT8pRKnw by 23n27@dgc.social
       0 likes, 0 repeats
       
       @azonenberg @gsuberland We're specing out a new embedded Linux design at work and it's painful.
       
 (DIR) Post #B6GDwMsAZrb6sBoM5I by 23n27@dgc.social
       0 likes, 0 repeats
       
       @azonenberg @gsuberland We're just barely below that point (we "only" need 4-8 GBit), but it's still a huge contribution to the BoM. Also size is a bit of a concern.
       
 (DIR) Post #B7gnZDX0cR0TY7Rdmi by 23n27@dgc.social
       0 likes, 0 repeats
       
       @mntmn Sorry to hijack this thread. I love the FUS302 but I have had problems with when trying to talk to PD3.0 peers in the past. Have you seen similar problems or am I just holding it wrong after all?(Screenshot from the commit message of my patch for working around this on Linux by disabling PD3.0 support)
       
 (DIR) Post #B7hk0Fn47fsRiQYFzk by 23n27@dgc.social
       0 likes, 0 repeats
       
       @mntmn I checked this with an USB-PD analyzer but didn't really chart the exact shape of the problem because throwing in this workaround (simply nuking PD3 support in the kernel) was good enough back then.At some point I should look into this and maybe add a quirk to the upstream driver.