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.

Google does too, although I only know of it being used for domains.google, which got killed.

They were expecting it to not be Android, but something more custom. Like I feel even just bare bones Linux would’ve been more acceptable.

I can’t wait for it to be added to activate-linux!

Ampere CPUs use normal DIMMs, and don’t have integrated storage, like any other CPU. So you can have the best of both worlds (although idk about power conservation, they are efficient though).

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.

IEEE Spectrum says this:

Currently, he says, the new discs have a writing speed of about 100 milliseconds and an energy consumption of microjoules to millijoules.

Idk if that means the full 200TB in 100ms, or a bit per 100ms, but there is a number out there I suppose.

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:

• The common BE200.NGWG is a CNVi module and everything except the radio itself was moved into Intel’s CPUs, for cost savings.
• The BE200.NGWG.NV is a normal NIC and should support AMD.
• The BE200.NGWG.NVX - same as above but with an X?
• Anything starting with 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

Here’s the actual HACS add-on: https://github.com/richardzone/homeassistant-dht

The one linked before looks to just be a GPIO one, not a DHT one.

That’s what he did, but with a home assistant yellow as the gateway.

The video is about smart devices that are poorly designed and/or rely on cloud infrastructure being dumb. Jeff also wants smart devices that will literally only talk to home assistant, and will still work fine if home assistant is offline (like a light switch will still work if the server is down).

my vacuum is defying discovery because of UDP crossing the subnets.

This is likely more to do with broadcast addresses. The vacuum would be broadcasting it’s presence on its own subnet’s broadcast address (x.x.151.255), but homeassistant is only listening on it’s subnet broadcast address (x.x.150.255). As routers don’t usually let broadcasts cross subnets, I don’t think there’s a way for the host or VM to listen for them like this.

You could setup vlans and hopefully VirtualBox supports passing through vlans, so that homeassistant would have multiple interfaces. Or like other people have said, just increase the size of the home assistant subnet so that it’ll overlap with the IoT subnet and the broadcast address would be the same, but some devices might not like responding to a device that’s on a different subnet to them, without a router.

Idk, I kinda preferred lunar lobster’s.