Maja changed the topic of ##bash-crimes to: we bash back | club of folks preoccupied in whether they could, not whether they should | logs https://libera.irclog.whitequark.org/~h~bash-crimes
\dev\ice has quit [Ping timeout: 252 seconds]
qsx has quit [Ping timeout: 244 seconds]
qsx has joined ##bash-crimes
\dev\ice has joined ##bash-crimes
\dev\ice has quit [Changing host]
\dev\ice has joined ##bash-crimes
whitequark[cis] has joined ##bash-crimes
<whitequark[cis]> manipulating pci express registers with bash feels so dirty
<whitequark[cis]> `setpci -s 3a:00.0 82.w=$(printf "%x" $((0x$(setpci -s 3a:00.0 82.w) & ~0xf | 0x3)))`
<whitequark[cis]> * `dev=3a:00.0 ; setpci -s $dev 82.w=$(printf "%x" $((0x$(setpci -s $dev 82.w) & ~0xf | 0x3)))`
<whitequark[cis]> this is how you drop the specific device to 8 GT/s
<cve> whitequark[cis]: sorry if I am disturbing here, but are you the smoltcp whitequark? :D
<whitequark[cis]> i am!
<whitequark[cis]> *bows*
<cve> woah, very nice :)
<cve> i've been working with it on a daily basis now :)
<whitequark[cis]> aw! how is it?
<cve> amazing! its api is very clearly documented and offers not just a functional stack, but also a reviewable one in case I want to know things more in depth :)
<cve> on a side note: do you happen to know out of your mind if smoltcp accepts packets that have the loopback as the dst IP but an arbitrary src?
<cve> currently an issue I am facing and I do not know at which layer on the stack it fails :D
<whitequark[cis]> aw, i'm really glad you like the API and implementation
<whitequark[cis]> i do not happen to know that. the bulk of my involvement was quite a while ago
<whitequark[cis]> smoltcp was intended from the beginning to be comprehensible, not quite to the point of a guide to TCP/IP but somewhat approaching it
<whitequark[cis]> that means I've succeeded :D