ADCs, DACs, IO extenders
These should all work without kernel drivers. For example, here’s a user space python library for ADS1*15 ADCs, or Nuvoton MS51 IO Expanders. Unless you need very specific timing or require the kernel to know about it, you shouldn’t need a kernel driver.
Idk, with I2C if it’s not something that needs a kernel level driver, there usually isn’t a problem with interacting with it from user space, for example basically all RAM RGB controllers are I2C and OpenRGB has no problem with them. I’m pretty sure I’ve only ever used an I2C device tree overlay for an RTC.
Also I2C/SMBus is present everywhere on x86, like some graphics cards expose it through their HDMI ports, even some server motherboards have a header for it; but for GPIO I’m unaware of any motherboards that expose it, so good luck researching the chipset and tracing out the pins.
If you can’t get the VPS to work, alternatively there’s Cloudflare but last I checked streaming was a little out of their free terms. With it, you should just have to set your AAAA record and make the cloud orange, that way Cloudflare will proxy it, and IPv4 will work. There’s also Cloudflare tunnels which lets you host websites without port forwarding anything.
then there’s definitely the type of water ditching where the plane angles into the water at full speed, and I don’t think that’s gonna have 80%
Pretty sure last time that happened it was still ~30%, which seems pretty impressive considering the video: https://youtu.be/w1u0D0E-Bq0 (SFW but it is a plane crashing)
Source: https://en.m.wikipedia.org/wiki/Ethiopian_Airlines_Flight_961
I believe 5.6.0 was in Debian testing for almost a month too.
While they did ‘complete’ their mission in 1989, I don’t think we ever completely lost contact with them. They did have to disable the majority of the sensors between then and now, to preserve power, but these all these communications issues were really only fairly recent events.
Idk, it looks like it’s part of the same question, so solving 19+14 is a little pointless when solving 19+45.
I might be completely wrong, but I’ve heard that a key is only a few hundred dollars, and once you’ve got it you can sign whatever you want. I think ReactOS also used to offer free driver signing for open source projects.
So I guess if ReactOS can afford one, so can most anti-cheat companies.
ZLUDA originally only supported on Intel since it was designed by an Intel employee, but AMD hired him to make it work for AMD instead. So in a way Intel is somewhat important here.
Most of a QR Code is redundant data so it’s still possible you can decode it, and the positioning marks are still there, but you’d probably have to remake the timing marks along the left, also idk how alignment marks work on a QR this big since some would be missing too (edit: actually only one and a half are gone).
He actually reminds me of Ben Doyle, who does write fairly interesting YouTube videos for Half as Interesting.
Edit: I’m sorry if you find this offensive or anything, just wanted to point it out.
Some discord servers can require a verified phone number, not any I know of, but it can be enabled.
Yeah, sorry I wrote the comment before I watched the video.
I’ve looked into getting one for my AMD laptop but I haven’t actually got one yet. Some models are locked, some are not, here’s my research:
BE200.NGWG is a CNVi module and everything except the radio itself was moved into Intel’s CPUs, for cost savings.BE200.NGWG.NV is a normal NIC and should support AMD.BE200.NGWG.NVX - same as above but with an X?BE202 sucks, avoid it.I definitely agree with automatically configured stuff, but I enjoy setting link-local static IP address with IPv6, like my home server is fe80::bad:c0de or 192.168.0.2, and my NAS is fe80::coo1:da1a or 192.168.0.3. I’ve definitely mistyped the IPv4 a few times (see your 169 typo), but the IPv6 always delivers hackerman vibes.
I have also set <prefix>::bad:c0de and have my IPv6 prefix on a keybind, but I understand that’s a bit of a stretch.
Yep that was exactly the issue I faced before giving up with NVMe.
I haven’t completed read through the tutorial, but UEFITool does exist for Linux. (I had unsuccessfully added NVMe support to an old motherboard previously)
That’s exactly why this project exists, to allow users to add ReBAR support to their old motherboards.
Excel would be emulating the silicon here
You should only need to add the IP of the last proxy before reaching Jellyfin, which would be Caddy.