amboar

5 ms·

1.
by amboar 9mo ago
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's just a shell script w
2.
by amboar 10mo ago
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 crossover project: https://www.hille
3.
by amboar 1y ago
[keys.select."space"] q = ":reflow" has worked well for me, even if the reflow behaviour itself is sometimes frustrating
4.
by amboar 1y ago
gcc's __attribute__((tainted_args)) is pretty handy: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attribute...
5.
by amboar 1y ago
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 in the ramifications, but the outcomes may still be
6.
by amboar 2y ago
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 bisect run, not at each bisection point inside a run. The b
7.
by amboar 2y ago
A handy trick I've developed is using`git bisect` to solve otherwise intractable rebase conflicts: https://codeconstruct.com.au/docs/bisect-intractable-rebase-...
8.
by amboar 3y ago
Related, have something similar for the major grid in Australia and it's smaller counterpart in Western Australia: https://opennem.org.au/
9.
by amboar 4y ago
OpenBMC supports SoCs from Aspeed and Nuvoton, and HP were/are working to add support for their GXP (iLO) SoC.
10.
by amboar 5y ago
Ah, here's the circuit design equivalent of that story: https://twitter.com/dave_universetf/status/14734753486542684...
11.
by amboar 5y ago
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
12.
by amboar 5y ago
> 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 file it against obmc-console at https:/&
13.
by amboar 5y ago
> 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?
14.
by amboar 6y ago
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 outlined: https://github.com/amboar&#x2
15.
by amboar 6y ago
> - braindamaged linking I mean, it's simple, but brain-damaged? > - "if (!pred(x) || a <= b && y)" for "if not pred(x) or a =< b and y" I guess more parentheses would improve the clarity but you
16.
by amboar 6y ago
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!)
17.
by amboar 6y ago
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 Users? https:&#x2F
18.
by amboar 7y ago
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
19.
by amboar 8y ago
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're accessing it from the UART debug interfac
20.
by amboar 8y ago
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.
21.
by amboar 8y ago
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
22.
by amboar 8y ago
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 where the BMC might be in a separate trust domain to the ho
23.
by amboar 8y ago
Right. The experience so far is that most people find the capability surprising.
24.
by amboar 8y ago
Bear in mind the P9 chip does SMT4, so four cores gives you 16 hardware threads, and 8 cores 32 threads etc.
25.
by amboar 8y ago
> 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 OpenPOWER OpenBMC firmwares we use the ColdFire to bitba
26.
by amboar 9y ago
Yeah no worries. I'm @arj:matrix.org, or if you want to try other avenues my keybase profile is listed in my hn profile
27.
by amboar 9y ago
The big list of naughty strings is a good place to start when digging up input issues: https://github.com/minimaxir/big-list-of-naughty-strings
28.
by amboar 9y ago
I think Riot has a terrible UX with respect to key management in group chats.
29.
by amboar 9y ago
Gigabit Ethernet does not require Cat6. Cat5 is capable but Cat5e is recommended. Cat6 and Cat7 can be used but are overkill. https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-T https://www.tomsguide.c
30.
by amboar 9y ago
Right, is a different back door, but at least it's not broken crypto. Not that I'm for compromised endpoints either.

More ›