Documentation. Add FreeRTOS porting notes

@aggarg
In a replay of Race in xTaskGenericNotifyWait() when cache enabled - #32 by aggarg

Have tried to add a page here (not finished yet) add a page for porting notes. Take a look, please.
When ready, I will submit a PR.

I’m not quite familiar with web and markdown, so not sure my link in FreeRTOS porting guide will work. Also I’m not native speaking English. I’m in doubts with serialize vs serialise, realise vs realize. My son told me the “se” variant more British and is equally correct but… Why you renamed a lot of functions somewhere at version 10? It was a pain…

Instead of creating a new page, I’d suggest to add a page section in the porting guide itself as you suggested before. Do not worry too much about the wording as we can fix that during review.

Thank you for your contribution!

I’m sorry, I have no exact idea how to add a page. This is the page with proposed content.
At this page I’ve trying to place a link (look for Implementing the stubs paragraph in my fork on this link).
I don’t know how to effectively place a link to a page, how to “design” the link - this is unfamiliar to me. May I commit the page (first link in this message) as is to let other person to design a link? I have no pretensions for a design, nor a makeup. I will be not harmed if someone will correct my spelling errors etc. Just have no spare time to learn web design.

Just realized what I meant was section and not page. Raise a PR with whatever you have and we will take it from there.

While I’m using the FreeRTOS in my projects, I could add some more notices. The next one I’m holding in mind - about nested interrupts and FreeRTOS configuration and stubs related. So I see it need to be separated page.
Submitted a PR: FreeRTOS porting notes are introduced with first note provided by Nikolay-Po · Pull Request #1 · FreeRTOS/FreeRTOS-Website-Content · GitHub

Try Asciidoctor. The document format behind it (Asciidoc) is like MarkDown 2.0, and easier to use. The program can translate your documents into HTML directly (and PDF indirectly through some flags):