[Oberon] Data transfer in large amounts

[Skulski, Wojciech]

Dear Paul:
> I did consider an SPI flash chip, which would have been a more appropriate
> size, but (micro)SD-cards are more freely available for not much
> difference in cost.

The SD cards are also more convenient for exchanging files, if there is a way to read them outside of the FPGA Oberon. It was the essence of my question.

> FWIW, I shared my own personal roadmap during Oberon Day 2011 (I've posted
> links to the talks here before), and posted here updates to what I'm doing
> and how and why some particular things were done.

Would you mind adding a pointer to your website? 

> But you are mistaken if you expect there is a team

I do not expect. I asked for a clarification. If there is some work going on, as it is obviously the case, then it is not inappropriate to ask "what work" and if there is a plan. This question does not imply that I expect anything. It only implies that the situation is less than clear.

>  And we are certainly not being secretive, rather, trying to help as much as we can with very limited resources!

Your help is duly acknowledged. All my questions can be addressed by posting a Readme file on your website with the file dates and briefly explaining what has been modified. Such a file can be considered a version control system. It would also help if a directory was available with previous versions for the record. I personally use the format Filename_date.zip. (For example ThisBoard_May_16_2015.zip.) Quite often I find it useful to go back to a past version to check some detail. It is a low cost solution which you may consider for the website. 

> previous posts on this forum

The posts are mostly devoted to ongoing discussions which are transient by their nature. By design, the discussion archive is not a source of up to date information. A Readme file would clarify the present status, if that Readme file was kept current. I do not think it is inappropriate to expect that current status is described in such a way. 

Thank you,
Wojtek