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

321–330 of 382 posts

Re: Open-Sourcing our Firmware

#321

Post by alar44 »

CamperBob2 wrote: post #282
alar44 wrote: post #269

Earlier quoted context omitted.

You'd have to have two intervals though, one for on, one for off. It bounces both ways. Hardware is more elegant but obviously the tradeoffs depend on what you're implementing.

It bounces both ways but as long as you don't accept another keypress action (up or down) immediately after the first, you're fine.

You're fine either way. You either have to poll, or use interrupts. If you are polling, you don't need to debounce the circuit. If you use interrupts, you're going to have a very bad time if you don't. Interrupts are much more efficient. Polling is wasteful.

Re: Open-Sourcing our Firmware

#322

Post by alar44 »

spookthesunset wrote: post #303
baybal2 wrote: post #287

Earlier quoted context omitted.

I had clients who were going to bargain for less than a penny

For ten million units, a penny is $100,000. You could give an engineer an entire quarter to come up with a software debounce for less than that. That shit adds up. BOM costs are everything for consumer goods.

And if you make $10 on each of those that's .1%. Or even if it's only $1 that's 1%. So be it!

I don't want to encourage shitty design for pennies at any level.

Stop making shitty shit.

Re: Open-Sourcing our Firmware

#323

Post by culi »

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…

I agree with not adding unnecessary e-waste to the current crisis. But perhaps you have someone in your life that could really use a laptop? You could get them a gift if they're interested in the laptop

Re: Open-Sourcing our Firmware

#325

Post by orthecreedence »

dsego wrote: post #141
tomtheelder wrote: post #74

Earlier quoted context omitted.

I suspect majority of users never touch Pg Up/Pg Dn/Home/End and all those other keys over there. For arrow keys, the compacted layout is helpful when designing a space constrained keyboard, and it's totally usable.

fn+arrow combo is imho equally as usable

I hate fn+arrow as an alternative to having real home/end/pgup/pgdown keys. It's probably the thing I hate most about my blade laptop.

Re: Open-Sourcing our Firmware

#326

Post by [deleted] »

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.…

[deleted]

Re: Open-Sourcing our Firmware

#327

Post by typ »

marcodiego wrote: post #19

What is the reason behind closed firmware? I understand that wifi devices may operate out of the certification depending on what the firmware does, but other devices... why do they have closed firmwares?

Hardware defects are often worked around by firmware. It can be things like adjusting current drive or lowering the clocks conditionally to mitigate EMI. It can even check the serial numbers of the hardware to determine what to do for the pieces with inferior quality in order to pass QA and increase yields. If customers get to find out what kind of defects or which batches are inferior, that would imply costly consequences for business.

Re: Open-Sourcing our Firmware

#329

Post by toastal »

gorjusborg wrote: post #159
jonaustin wrote: post #139

Earlier quoted context omitted.

This 'low-res' comment makes no sense, I'll never go back to 1080p, but 2256x1504 is plenty IMO for text (I live in a CLI all day pretty much).

Especially on a 13" screen. I have an XPS 13 with a 4k screen and I never use it at native resolution undocked because I'd need a magnifying glass to read anything on it.

That's been the unfortunate part: "do you want 4K or 1080?" has been the question for the longest part without consideration that many people want something in between--hiDPI without going into sizing where you can't tell the different. I have only had 4K screens (15", 14", & 13") since 2015 and can't handle 1080, but I don't want the wasted battery from 4K on smaller sizes.

Re: Open-Sourcing our Firmware

#330

Post by toastal »

ayushnix wrote: post #307
hailvectron wrote: post #295

Things I'm hoping to see in time for a Framework machine to become my next laptop: - AMD processor options - Keyboards with a trackpoint - decades of ThinkPaddery have conditioned me; I regularly use a Dell touchpad-equipped laptop & contemporary Mac laptop and still pine for a trackpoint. Very personal preference, I know, but hopefully the Framework Marketplace comes to provide this. - Proper 14" HiDPI screen - Long…

> - Proper 14" HiDPI screen I can't stress this enough. The display on the Framework can't do integer scaling and so almost everyone who intends to use an external monitor with the Framework can't do that on Linux without extremely annoying issues such as significantly higher input latency, GUI apps behaving abnormally, and not being able to use an external monitor and the laptop screen simultaneously. I don't care i…

"Proper" should also include at least 100% DCI-P3 coverage instead of sRGB
Post reply on HN