Hi,
after reading all responses I would propose to:
1. use Markdown for all READMEs: the syntax is simple and perfectly readable in
pure text
2. start a doc-specific repo using RST format (has nice support for writing API
descriptions, among other things useful for technical docs) which would
Matias,
I think this sounds reasonable and I am happy to help. I'm a little
conflicted about having two different markdown formats one for readmes
and one for true documentation, but we already have that to some
extent with the html docs, and sphinx can bridge the gap a little
anyway allowing embe
On Mon, Jul 20, 2020, at 00:59, Brennan Ashton wrote:
> Matias,
> I think this sounds reasonable and I am happy to help. I'm a little
> conflicted about having two different markdown formats one for readmes
> and one for true documentation, but we already have that to some
> extent with the html d
On Sun, Jul 19, 2020 at 9:27 PM Matias N. wrote:
>
> > An example readme conversion might also
> > be helpful to outline what this looks like for people who are
> > concerned about it remaining plaintext (I agree that it is)
>
> That was also a reason why I proposed starting with just the main REA
> I was not aware of the limitation of TFIS only working for RX -> TX.
Where is that documented?
There is "Figure 117: IFS timing detail" in the NRF52840 manual which shows
only RX->TX and I followed this.
I don't see any description of how RADIO behaves on TX->RX when TIFS is
enabled.
So we prob
