Viewing profile — stffrdhrn
stffrdhrn
HN member- Joined
- Wed, Oct 23, 2019, 11:22 AM UTC
- HN karma
- 11
- Public activity
- 10 items
- HN profile
- View on Hacker News ↗
About stffrdhrn
Recent public activity
-
comment
Comment #35565915
I think what is nice about this project is that it combines everything in a mono repo which is nice for setting up continuous integration and other testing workflows. This project …
-
comment
Comment #30940708
I read your site, its great. This is mine, similar vibe :): https://stffrdhrn.github.io/
-
comment
Comment #29293499
I was hoping this would be implemented by actually reading a memory location that was set to 0, when the system is hibernating/sleeping. But it always returns 1. If it was reading …
-
comment
Comment #27743666
The riscv kernel maintainer is not interested in maintaining many different configs for many different SoC. So that is one effort to avoid fragmentation. If you look at the riscv c…
-
comment
Comment #26031412
I used to live in London (8 years ago) and I did exactly this because of the Jubilee line. I had written a perl program rss.pl that I would give several URLs to generate custom RSS…
-
comment
Comment #22089477
I wrote this article. As I worked on it I discovered many good resources on Thread Local Storage (TLS), I linked to those in the Further Reading section. Even with some really good…
-
comment
Comment #21681671
Yes, for OpenRISC as there are no instructions with a 32-bit immediate so we use 2 high and low order relocations. However, on machines like x86 they have variable width instructio…
-
comment
Comment #21675415
Hello, There are 2 relocations because the series of instructions that needs to create a 32-bit memory address requires HI16 and LO_16 relocations. The 2 relocations sure 16-bit hi…
-
comment
Comment #21669371
Thanks for your feedback, it was a typo (I am pretty bad with those). I changed it to say "The addend from the relocation entry discussed above in the Listing Relocation Entries se…
-
comment
Comment #21668394
Thanks for pointing that out. As the OpenRISC maintainer of Linux/GCC etc I didn't even know about this effort. Let alone the tool. I wrote this article with openrisc examples but …