Meh... Where are the remote jobs? I bet if you open an office in Oregon (where there's tons of Intel Open Source people) you'll find a lot of candidates. Or, you know, act like the old times of 2020 and hire remote employees?
Meh... Where are the remote jobs? I bet if you open an office in Oregon (where there's tons of Intel Open Source people) you'll find a lot of candidates. Or, you know, act like the old times of 2020 and hire remote employees?
Or just how often development hardware self-bricks and needs to be recovered.
Doing hardware work remotely is a lot slower. Possible, but slower.
Edit: Or how there is that one person who is really good at assembly and if you can walk down and ask them a question it'll save you a couple hours (days) of debugging.
And then there is that one person who is really good with an oscilloscope and while in theory you shouldn't need to have decode messages by sight from waveforms, well, this one person can and it sure is useful time to time....
Sure, but minor fixes soldered in place aren't uncommon.
My experience is with firmware for embedded and consumer electronics, maybe video cards are sufficiently complex that none of the things I saw are even possible!
Lots of issues resolving power states, clock trees, monitoring buses, docs from suppliers were always subtly wrong, power management chips never quite worked how they were supposed to, things like that.
would guess since this is AMD and low level Linux, there may be a good deal of interfacing with physical hardware, in addition to any other preferences they might have