[Oberon] Data transfer in large amounts

[Joerg]

I never actually deep-dived in the FS algorithms.
Perhaps yes. Perhaps there is a problem that some algorithms have other restrictions (calculation overflows or so…)
And changing something in the four modules of the inner core (Kernel, Fles, FileDir, Modules) is not as easy as just compiling and off you go. You have to link those files…

Jörg 

> Am 13.07.2016 um 08:33 schrieb Skulski, Wojciech <skulski at pas.rochester.edu>:
> 
> OK. Are you saying that Kernel.Mod can handle an 8 gigabyte SD card after changing the constant? It would be great.
> ________________________________________
> From: Oberon [oberon-bounces at lists.inf.ethz.ch <mailto:oberon-bounces at lists.inf.ethz.ch>] on behalf of Jörg Straube [joerg.straube at iaeth.ch <mailto:joerg.straube at iaeth.ch>]
> Sent: Wednesday, July 13, 2016 2:21 AM
> To: ETH Oberon and related systems
> Cc: paulreed at paddedcell.com <mailto:paulreed at paddedcell.com>
> Subject: Re: [Oberon] Data transfer in large amounts
> 
> Wojtek
> 64 MB is the limit of the OberonFS (variable "sectormap" in Kernel.Mod)
> Jörg
> 
> 
>> Am 13.07.2016 um 08:02 schrieb Skulski, Wojciech <skulski at pas.rochester.edu>:
>> 
>> Paul:
>> 
>> thank you for the comment. You wrote:
>> 
>>> a 64MB filesystem
>> 
>> This size fits well in a NOR flash chip whose size is limited to 64 MB. The SD cards are 4 GB and up. I do not think that my question concerning gigabytes was unreasonable.
>> 
>>> it's quite outside the scope of what we are doing
>> 
>> I take "we" as an indication that there is a team. Also, "scope" and "doing" is indicative of some sort of a plan. Would you mind sharing your plan, a roadmap, and the future of FPGA Oberon?
>> 
>> I am asking because someone here wrote that there are new releases on your website. According to that e-mail, the most recent release was July/04/2016. It is an indication that some work is going on. However, there are no announcements to this list when something is updated. There are no dates on the website https://urldefense.proofpoint.com/v2/url?u=http-3A__www.projectoberon.com_&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=Ym3kzaZSTg559P_LBAJYLiJeI2yirTbLqYONG7HAQ6A&e= <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.projectoberon.com_&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=Ym3kzaZSTg559P_LBAJYLiJeI2yirTbLqYONG7HAQ6A&e=> , other than 27.10.2015 in the top line. So I cannot check whether that information was true, or was it a mistake. Would you mind writing the release dates next to the files?
>> 
>> Would you mind explaining, what is going on? Are there any plans concerning FPGA Oberon?
>> 
>>> Oberon presents far fewer barriers to "doing it yourself", with absolute control, than other more mainstream systems.
>> 
>> One of the reasons I am a bit hesitant to put effort into FPGA Oberon is lack of information concerning its support, its future, and its stability. Lack of this basic information is the opposite to being in control. Uncertainty what is going on is discouraging from putting effort into FPGA Oberon. It would feel like building a house on a moving sand.
>> 
>> Perhaps being a bit less secretive could provide some sense of stability which is needed for any serious planning.
>> 
>> W.
>> 
>> 
>> 
>> 
>> --
>> Oberon at lists.inf.ethz.ch <mailto:Oberon at lists.inf.ethz.ch> mailing list for ETH Oberon and related systems
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=5UMEnQMNb2kr8uzhGqO3ZwosYNRhEq_rTdnhJGTer5s&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=5UMEnQMNb2kr8uzhGqO3ZwosYNRhEq_rTdnhJGTer5s&e=>
> 
> --
> Oberon at lists.inf.ethz.ch <mailto:Oberon at lists.inf.ethz.ch> mailing list for ETH Oberon and related systems
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=5UMEnQMNb2kr8uzhGqO3ZwosYNRhEq_rTdnhJGTer5s&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=CwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=Rfdo3GkjLO8geXJys3K2_ypwKPZcubrw90Hj4VIQGM4&s=5UMEnQMNb2kr8uzhGqO3ZwosYNRhEq_rTdnhJGTer5s&e=>
> --
> Oberon at lists.inf.ethz.ch <mailto:Oberon at lists.inf.ethz.ch> mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon <https://lists.inf.ethz.ch/mailman/listinfo/oberon>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20160713/6ab2296c/attachment.html>