Hi Matt, guys, Matt, I read in comments your FAT32 lib doesn't support fragmented files. Do you actually try to implement this feature, and did you give up because not enough resource ? I'm asking because, while implementing Minix FS, I'm slowly running out of resource. My current sample, which is big in term of features, requires 32K memory, 1800 RAM and 13 stack levels ! This sample implements a kind of shell where you can:
minix> fsck # print super block details minix> cd directory minix> ls # list dir content minix> ls file1 # show inode/file details minix> cat file1 # print file's content minix> dcat file1 # dev cat, show content with addresses etc... minix> open file1 # open file minix> read # print one byte minix> read 10 # print 10 bytes minix> seek 100 # goto 100th byte minix> write SEB # write content within file minix> close # flush changes, close inode minix> reboot # asm goto 0 ;) This is a nice tool to play with Minix and understand how it works. I hope to find time to write a tutorial. I think I'll be able to provide fragmented file feature but now have concerns about being able to fully implemented remaining features... I sure have to optimize my code, but I think I'll have to provide a restricted version, as you did with fat32_small.jal. Code duplication will be an issue I guess. I'll create more samples showing different minimal usage (open, read, write) in order to have a better overview of requirements (and then track how they evolve). PS: -const-detect saves 300 program mem bytes. I can't compile without -no-variable-reuse, I tried to manually reuse variables within my code... Cheers, Seb 2011/4/28 Joep Suijs <[email protected]> > Hi Seb, > > > > > > I'm not sure about you mean > . > > And storing them within an array really costs a > > lot of resources when accessing them. > This is what I mean. So it could work if it wasn't for the overhead... > > > Joep > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
