Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
monocasa
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
41 ms
·
811.
▲
by
monocasa
2y ago
I wonder how much help they had by asahi doing a lot of the kernel and ecosystem work anablibg 16k pages. RISC-V being fixed to 4k pages seems to be a bit of an oversight as well.
812.
▲
by
monocasa
2y ago
0xDD - I feel like that's pretty decent these days.
813.
▲
by
monocasa
2y ago
I would be shocked if a judge interpreted that to include essentially willful perjury (or at least false statements) to a national security agency.
814.
▲
by
monocasa
2y ago
You don't need that as much on modern protocols. The point of 8b/10b or 64b/66b is that it guarantees enough edges to allow receivers to be self clocking from the incoming bits being more or less thrown directly into a PLL.
815.
▲
by
monocasa
2y ago
In the cases where I do this, it's when I try really hard not to actually expose the state machine to tests anyway because there's a better way to hit them in tests with their expected inputs and outputs rather than an implementat
816.
▲
by
monocasa
2y ago
I imagine that more people applying to MIT than they can accept have maxed out all of the opportunities they've been given.
817.
▲
by
monocasa
2y ago
I have used function local enums for the states of a function local state machine pretty successfully.
818.
▲
by
monocasa
2y ago
Just going to through out there that you don't need a custom kernel driver to do this on Android. There's a userspace gadget API; you only need a rooted phone to have the permissions to access the relevant device and config files
819.
▲
by
monocasa
2y ago
A rooted android can. https://github.com/tejado/android-usb-gadget
820.
▲
by
monocasa
2y ago
I don't think that SoC makes sense. Because of how the pad frame would work for the ddr and and pcie, you'd have a bunch of empty silicon if you only stuck a couple A73s and a simple GPU in it (and at this scale, the Ethernet is
821.
▲
by
monocasa
2y ago
Depends on the team. I almost prefer juniors to make some mistakes and spend some time trying to figure it out on their own. There's a good chance they won't figure it out, but the journey they go on is a lot of time worth it.
822.
▲
by
monocasa
2y ago
They shipped the 128k model as the first model.
823.
▲
by
monocasa
2y ago
Because August was historically Vegas's off-season, being a bajillion and a half degrees outside, and they could get a good deal on conference space.
824.
▲
by
monocasa
2y ago
It's not BCD style magic, but just a choice of units. Say instead of in meters, if the unit is 1/65536 of a meter, than you can describe those integers as 16.16 fixed point meters.
825.
▲
by
monocasa
2y ago
I'm not sure if it's useful in this incarnation, but I am reminded of the localizers in A Deepness in the Sky, an early description of smartdust which were relatively omnipresent and capable of communicating and being reprogrammed
826.
▲
by
monocasa
2y ago
This dockerfile explicitly enables kvm in a way that will cause qemu to fail if it's not present.
827.
▲
by
monocasa
2y ago
This requires kvm exposed in the container. Does docker on mac support kvm?
828.
▲
by
monocasa
2y ago
That's just the architecture and driver independent part of the kernel. The kernel source tree is 15M lines or so.
829.
▲
by
monocasa
2y ago
The oxidation is. The choice of voltage scaling is not.
830.
▲
by
monocasa
2y ago
I didn't imply that the code remains and it's only data that is swapped out. The thread jumps to another complete address space. It's like a system call instruction that instead of jumping into the kernel, jumps into another
831.
▲
by
monocasa
2y ago
Writing a top level comment here to hopefully address some of the misconceptions present across this comment section. Doors at the end of the day aren't message passing based RPC. There is no door_recv(2) syscall or equivalent nor any
832.
▲
by
monocasa
2y ago
Not quite. There isn't a door_recv(2) systemcall or equivalent. Doors truly don't transfer messages, they transfer the thread itself. As in the thread that made a door call is now just directly executing in the address space of t
833.
▲
by
monocasa
2y ago
It's a remote console to the management engine for "lights out management" or remotely being able to to what a hardware tech would generally need physical access for like accessing the preboot environment. It's bad if yo
834.
▲
by
monocasa
2y ago
At this point I'm a bit surprised that nobody has created a netlist of the board and simply reinstalled the relevant chips on it. There has to be more density that can be eked out for easier that way than carefully taking a Dremel to
835.
▲
by
monocasa
2y ago
> If you wanted cheap above all, you could have gone for a plain 6502 or a cut-down variant (like the 6507 in the Atari VCS), but they also didn't do that -- the Ricoh 2A03 is a custom part that includes custom sound hardware. The h
836.
▲
by
monocasa
2y ago
Thanks for catching that.
837.
▲
by
monocasa
2y ago
When you can't verify an update, rolling back atomically to the previous state is generally considered the safest option. Best run what you can verify was a complete package from whoever you trust.
838.
▲
by
monocasa
2y ago
Kernel driver bug that essentially defaults, then on reboot loads the same driver early on segfaults and reboots again, ad nauseum.
839.
▲
by
monocasa
2y ago
Nothing like that, basically what sitharus said above you. Extra network level, zero trust to minimize lateral movement and giving the pen testers a leg up by letting them start already within the corporate network.
840.
▲
by
monocasa
2y ago
The contracts are rarely specifying stuff like antivirus explicitly, but instead compliance with one or more of the security standards like PCI DSS. Those say you have to use antivirus, but they all have an escape hatch called a "comp
More ›