Viewing profile — amboar
amboar
HN member- Joined
- Wed, Aug 31, 2011, 11:17 PM UTC
- HN karma
- 577
- Public activity
- 144 items
- HN profile
- View on Hacker News ↗
About amboar
No profile information was provided.
Recent public activity
-
comment
Comment #46309302
I've become pretty enthusiastic about checklists. In case it helps anyone else, I wrote a small tool that helps maintain and execute them: https://github.com/amboar/checklists/ It'…
-
comment
Comment #45850924
As I haven't seen a link to it in the comments yet: A while back Hillel Wayne put some effort into resolving the question of "Is Software Engineering Real Engineering?" with the cr…
-
comment
Comment #45221057
[keys.select."space"] q = ":reflow" has worked well for me, even if the reflow behaviour itself is sometimes frustrating
-
comment
Comment #44755556
gcc's __attribute__((tainted_args)) is pretty handy: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attribute...
-
comment
Comment #43794268
Section J.1 _Unspecified_ behavior says > (11) The values of bytes that correspond to union members other than the one last stored into (6.2.6.1). So it's a little more constrained…
-
comment
Comment #39881430
Yeah, I have rerere turned on However, it's not directly beneficial for the process outlined. With what I wrote about you only solve a given conflict at the end of a complete bisec…
-
comment
Comment #39879097
A handy trick I've developed is using`git bisect` to solve otherwise intractable rebase conflicts: https://codeconstruct.com.au/docs/bisect-intractable-rebase-...
-
comment
Comment #38670934
Related, have something similar for the major grid in Australia and it's smaller counterpart in Western Australia: https://opennem.org.au/
-
comment
Comment #32399037
OpenBMC supports SoCs from Aspeed and Nuvoton, and HP were/are working to add support for their GXP (iLO) SoC.
-
comment
Comment #29890319
Ah, here's the circuit design equivalent of that story: https://twitter.com/dave_universetf/status/14734753486542684...
-
comment
Comment #29316070
One of my favourite talks is Decapping Chips the Hard Way by Adam Laurie and Zac Franken: https://youtu.be/0Z4aF-qiziM That was 8 years ago
-
comment
Comment #27116079
> It was eating characters, which is the second worst thing it could do. Okay, that's interesting. Did you file a bug with your system's firmware provider or with upstream? You can…
-
comment
Comment #27114379
> there is a lot about it that I won't miss, especially the way it handles serial communication Out of curiosity, what were the issues you had with OpenBMC's serial communication?
-
comment
Comment #26444464
I realise your post is an argument in favour of Rust over C for these things, but regardless, you might be interested in a WIP library I've started to solve most of the issues you …
-
comment
Comment #25505726
> - braindamaged linking I mean, it's simple, but brain-damaged? > - "if (!pred(x) || a I guess more parentheses would improve the clarity but your English translation suffers the …
-
comment
Comment #25226093
As others have said, hacking it, certainly. But if you're not up for that and would like something more passive, read LWN.net (and possibly subscribe!)
-
comment
Comment #24390751
Rusty's API scale captures this approach really well: How Do I Make This Hard to Misuse? https://ozlabs.org/~rusty/index.cgi/tech/2008-03-30.html What If I Don't Actually Like My U…
-
comment
Comment #19767550
Use a packed struct (e.g. __attribute__((packed))). You may take a performance hit due to lack of alignment, but that's the judgement call
-
comment
Comment #19026084
Right; then it comes down to platform design and whether you can reboot the soc in a mode that both reopens the bridges and doesn't kill the host, though that's not relevant if you…
-
comment
Comment #18976352
Something important to note is that this is largely a BMC firmware problem - the hardware can be securely configured to maintain CIA against the host, just sometimes it is not.
-
comment
Comment #18976254
Please upstream your changes! I remember you were playing around with getting OpenBMC running on a Supermicro X11, would be good to expand the x86-64 support
-
comment
Comment #18975965
The description looks bad on the surface, but as always reality is more nuanced. These issues are only problematic in specific circumstances, particularly, bare-metal cloud hosting…
-
comment
Comment #18975918
Right. The experience so far is that most people find the capability surprising.
-
comment
Comment #18532325
Bear in mind the P9 chip does SMT4, so four cores gives you 16 hardware threads, and 8 cores 32 threads etc.
-
comment
Comment #18420527
> The BMC (IPMI) is also a self sufficient ARM computer ASPEED BMC SoCs (popular BMC SoCs also used in OpenPOWER systems) have a ColdFire (m68k) co-processor buried inside them. In…