stffrdhrn

6 ms·

1. 1.▲
   by stffrdhrn 3y ago

   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 can be used to build toolchains for newlib (bare metal), mu
2. 2.▲
   by stffrdhrn 5y ago

   I read your site, its great. This is mine, similar vibe :): https://stffrdhrn.github.io/
3. 3.▲
   by stffrdhrn 5y ago

   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 a flag from memory it would be useful when examining
4. 4.▲
   by stffrdhrn 5y ago

   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 config tree we can see about 5 configs: https://g
5. 5.▲
   by stffrdhrn 6y ago

   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 feeds for those websites that provided poor, summary only,
6. 6.▲
   by stffrdhrn 7y ago

   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 documents it was still hard for me to see the big picture
7. 7.▲
   by stffrdhrn 7y ago

   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 instructions and support 32-bit relocations, they can get by with a s
8. 8.▲
   by stffrdhrn 7y ago

   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 high and low bitfields to compose the 32-bit address. For a fu
9. 9.▲
   by stffrdhrn 7y ago

   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 section". Addend is actually usually 0 and importan
10. 10.▲
    by stffrdhrn 7y ago

    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 it is meant to be easy to transfer to other archi