[nuttx][avr] Issues while building avr (atmega) board example.

Hello, Basically I'm trying to build the moteino-mega board example and I found some issues. I have prepared a fix for all of these issues, but first of all I want your opinion on one of the issues. Seems like the linux avr-gcc does not include double_t as a type inside the compiler provided , an

Markdown READMEs?

Hi, what do you think about using Markdown for README files? I think the syntax is good for direct reading but it also has the added benefit of being supported with nice rendering in different platforms, such as GitHub itself. Maybe this can also be used to expose the READMEs in the wiki/website

Re: Markdown READMEs?

I would be huge fan of this. It makes it a lot more approachable, I had started converting the main readme in particular but I did not get very far. It's a lot of work. Did you see Adams work here https://nuttx-companion.readthedocs.io/en/latest/ I thought it would be really nice to integrate th

Re: Markdown READMEs?

On Wed, Jul 15, 2020, at 22:45, Brennan Ashton wrote: > I would be huge fan of this. It makes it a lot more approachable, I had > started converting the main readme in particular but I did not get very > far. It's a lot of work. I can help with that if you want > Did you see Adams work here > ht

Re: Markdown READMEs?

> what do you think about using Markdown for README files? Since the project was very conservative so far, I used regular expression to parse some existing files into Markdown. Although it is not completely reliable. I also think that markdown in repository would be great. Even trying to sneak in

Re: Markdown READMEs?

Zephyr uses Sphinx and ReStructured Text (RST) for their docs. I'm a fan obviously, it's great for writing hyperlinked technical documentation. Sphinx requires Python, though. The board list with pictures is a great

Re: Markdown READMEs?

Hi, You might want to look at https://asciidoctor.org It an improved markdown with a few more features and multiple outputs. Thanks, Justin