Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Open-Sourcing our Firmware

frame.work

Post reply on HN
Print view View original

231–240 of 382 posts

Re: Open-Sourcing our Firmware

#231

Post by lillecarl »

Ericson2314 wrote: post #190
lillecarl wrote: post #100

Earlier quoted context omitted.

Having come from Debian, Ubuntu, and Manjaro I settled on what feels like the last distro I will use on my own systems: NixOS. It's not so much better, it's so much different. Every(ish) single package, every single line of configuration(ish) is under version control in a(couple) nix files. I share (most) of it between my systems. With flakes (and it's lockfile) it's a 100%(ish) deterministic system. Downside: The la…

> I also don't use home-manager, but chezmoi for my dotfiles. Since I want my home configuration to work on MacOS and other distros I might SSH. FYI, home manager works on MacOS just fine. I usually tell people to start with Home Manager as I think it's the best gateway drug to Nix stuff at the moment.

Yes indeed, I should've expanded to requiring user namespaces and other kernel magic I can't expect from any random box i wanna work on.

I'm looking forward to checking Darwin nix stuff out.

Re: Open-Sourcing our Firmware

#232

Post by Teknoman117 »

ad8e wrote: post #165

I checked the keyboard debouncing logic [0] and it was fine. Some keyboards from other manufacturers, notably Lenovo Thinkpads, have absurd debouncing algorithms that scramble keys or add delays, so it's good to see Framework has a correct solution. [0]: https://github.com/FrameworkComputer/EmbeddedController/blob...

Out of curiosity, is there anything in particular that you're looking for? On a cursory glance, whenever a key state is sampled as different to the previously reported state, it immediately reports a state change and locks out any further reports for a specified amount of time. So, the report goes out the moment the state changes, so long as you can't perceive the debounce time, which I presume would be a few dozen microseconds. (Rather than some debouncers I've seen which wait for the debounce period to end before sending the initial report)

Re: Open-Sourcing our Firmware

#233

Post by alar44 »

ad8e wrote: post #207
ohazi wrote: post #197

Earlier quoted context omitted.

I've noticed that I seem to miskey my unlock password immediately after resuming from sleep way more often than when I use that password at other times, or when using an external keyboard (Lenovo T480). I always suspected that something was wonky, but a weird debounce bug would totally explain it, especially as I tend to type that password very quickly.

The scrambling is easy to see once you know it's happening: press k and l simultaneously on your Thinkpad keyboard. It'll always come out "lk" unless you deliberately separate them. Testing was done [0], but it's not written in an easy-to-understand way. As a summary, Thinkpad keys are scrambled within 15-23 ms. Usually, humans ascribe scrambled letters to their own mistakes, but this time it's the keyboard's fault.…

Wow. I'm surprised they don't do this on the component level. When I was working in embedded, I considered software debouncing a lazy hack. I'd rather sanitize the data before it hits software.

Re: Open-Sourcing our Firmware

#234

Post by ziml77 »

ohazi wrote: post #124

I've been so happy to see what Framework has been doing lately, and really want to support them, but I already have a desktop as my primary computer and two Thinkpads that are already set up nicely, but that I rarely use. I moved from 15" laptops to 14" when Lenovo added the numpad on the larger variant, and 14" is about as small as I want to go. I kind of want to buy a framework though, just to support them? But I h…

Hopefully they are able to expand their lineup to include a 15" model. I tried to work on a 14" MacBook Pro and ended up returning it because it felt too small. Though I probably still wouldn't exchange my 16" M1 MBP for a 15" Framework laptop unless Framework manages to even come close to competing with M1's power efficiency. That really depends on a chip designer making something competitive though. Not much Framework can do other than find ways to improve Linux's power management.

Re: Open-Sourcing our Firmware

#235

Post by freeopinion »

NaturalPhallacy wrote: post #219
staindk wrote: post #146

Earlier quoted context omitted.

FWIW I don't think you should buy a laptop from them just to support them. Just adding to e-waste down the line, and I'm sure they are selling enough units. In the future when you do actually need/want a new laptop of course it would be great to support them then. And advocate for them when a friend asks about what laptop to buy.

Could buy one and donate it to someone else, or a library.

I can supply a mailing address.

Re: Open-Sourcing our Firmware

#237

Post by sydthrowaway »

CamperBob2 wrote: post #227
poyu wrote: post #177

Earlier quoted context omitted.

Debounce is an interesting topic[0], I tend to use hardware debounce whenever possible on my own projects. [0]: https://hackaday.com/2010/11/09/debounce-code-one-post-to-ru...

Don't accept a keypress if the same key was previously pressed less than x milliseconds ago. What else is there to know about debouncing?

What is x? Is it related to human capability?

Re: Open-Sourcing our Firmware

#238

Post by mplanchard »

lillecarl wrote: post #100
_zooted wrote: post #86

Earlier quoted context omitted.

Having come from elementaryOS I can say that Fedora 35 is awesome. So much better!

Having come from Debian, Ubuntu, and Manjaro I settled on what feels like the last distro I will use on my own systems: NixOS. It's not so much better, it's so much different. Every(ish) single package, every single line of configuration(ish) is under version control in a(couple) nix files. I share (most) of it between my systems. With flakes (and it's lockfile) it's a 100%(ish) deterministic system. Downside: The la…

Just wanted to echo all of this. I started with home-manager and then moved to NixOS over the holiday. It’s really been great: easy to set up, relatively easy to configure most things, and it’s so lovely to know that the changes I make are checked into version control for easy use across machines.

Re: Open-Sourcing our Firmware

#239

Post by nonameiguess »

franga2000 wrote: post #184
bbojan wrote: post #130

Earlier quoted context omitted.

Because I'm down the rabbit hole of highly customized keyboards, at one point I did a frequency analysis of the keys I use the most. Guess what was the most frequently used key? Cursor down followed by cursor up. For example, cursor down was pressed ~2.5x more times than space, or ~4 times more than letter E, which is was the most frequently used letter. Guess what are the smallest keys on a Mac-type keyboard (the la…

Keep in mind this is likely unique to CLI users. The vast majority of users have little use for arrow keys - nudging the text cursor a few chars left/right and making tiny moves in graphics software are about the only two I can think of.

Not just CLI but also browsers when you don't want to get bitten by infinite scroll adjustments moving your scrollbar cursor placement and then pressing down before noticing and accidentally scrolling past 50% of the page you were just trying to read.
Post reply on HN