DSPRelated.com
Forums

FAT file system for DSP/BIOS?

Started by Randy Yates May 15, 2010
I've googled and found very little info. If someone could point me in 
the right direction, I'd appreciate it. It would be nice to find, e.g.,
and IOM mini-driver that would allow concurrent files to be
read/written, but maybe I'm dreaming...
-- 
Randy Yates                      % "Though you ride on the wheels of tomorrow,
Digital Signal Labs              %  you still wander the fields of your
mailto://yates@ieee.org          %  sorrow."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO
Randy Yates wrote:
> I've googled and found very little info. If someone could point me in > the right direction, I'd appreciate it. It would be nice to find, e.g., > and IOM mini-driver that would allow concurrent files to be > read/written, but maybe I'm dreaming...
http://www.larwe.com I'm too lazy to see if he still has his code posted, or even if his site is still up -- so you can report. Ask over on comp.arch.embedded -- lots -o- knowledge there. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com

Randy Yates wrote:

> I've googled and found very little info. If someone could point me in > the right direction, I'd appreciate it. It would be nice to find, e.g., > and IOM mini-driver that would allow concurrent files to be > read/written, but maybe I'm dreaming...
I was looking for a decent implementation of FAT couple of years ago. There is a lot of opensource junk; nobody gives up good stuff for free. From commercial implementations, several people recommended FAT which comes with mucos-II. We ended up rolling our own multithreaded FAT with POSIX API. It is in plain C with OS porting layer. If you are interested, we may discuss that. Vladimir Vassilevsky DSP and Mixed Signal Design Consultant http://www.abvolt.com
Vladimir Vassilevsky wrote:
> > > Randy Yates wrote: > >> I've googled and found very little info. If someone could point me in >> the right direction, I'd appreciate it. It would be nice to find, e.g., >> and IOM mini-driver that would allow concurrent files to be >> read/written, but maybe I'm dreaming... > > I was looking for a decent implementation of FAT couple of years ago. > There is a lot of opensource junk; nobody gives up good stuff for free. > From commercial implementations, several people recommended FAT which > comes with mucos-II. > We ended up rolling our own multithreaded FAT with POSIX API. It is in > plain C with OS porting layer. If you are interested, we may discuss that.
I wonder how well the dual license software works from a business perspective. "Dual license" in this case means the full "poison pill" GPL if you don't pay money, and some $$ royalty scheme if you want to use it without publishing the rest of your code. It seems like a good way to advertise your product for free, then harvest some money if someone actually uses it. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com
Tim Wescott <tim@seemywebsite.now> writes:

> Vladimir Vassilevsky wrote: >> >> >> Randy Yates wrote: >> >>> I've googled and found very little info. If someone could point me >>> in the right direction, I'd appreciate it. It would be nice to >>> find, e.g., >>> and IOM mini-driver that would allow concurrent files to be >>> read/written, but maybe I'm dreaming... >> >> I was looking for a decent implementation of FAT couple of years >> ago. There is a lot of opensource junk; nobody gives up good stuff >> for free. From commercial implementations, several people >> recommended FAT which comes with mucos-II. >> We ended up rolling our own multithreaded FAT with POSIX API. It is >> in plain C with OS porting layer. If you are interested, we may >> discuss that. > > I wonder how well the dual license software works from a business > perspective. "Dual license" in this case means the full "poison pill" > GPL if you don't pay money, and some $$ royalty scheme if you want to > use it without publishing the rest of your code.
A great summary of GPL in one sentence! -- Randy Yates % "My Shangri-la has gone away, fading like Digital Signal Labs % the Beatles on 'Hey Jude'" mailto://yates@ieee.org % http://www.digitalsignallabs.com % 'Shangri-La', *A New World Record*, ELO
Randy Yates wrote:
> Tim Wescott <tim@seemywebsite.now> writes: > >> Vladimir Vassilevsky wrote: >>> >>> Randy Yates wrote: >>> >>>> I've googled and found very little info. If someone could point me >>>> in the right direction, I'd appreciate it. It would be nice to >>>> find, e.g., >>>> and IOM mini-driver that would allow concurrent files to be >>>> read/written, but maybe I'm dreaming... >>> I was looking for a decent implementation of FAT couple of years >>> ago. There is a lot of opensource junk; nobody gives up good stuff >>> for free. From commercial implementations, several people >>> recommended FAT which comes with mucos-II. >>> We ended up rolling our own multithreaded FAT with POSIX API. It is >>> in plain C with OS porting layer. If you are interested, we may >>> discuss that. >> I wonder how well the dual license software works from a business >> perspective. "Dual license" in this case means the full "poison pill" >> GPL if you don't pay money, and some $$ royalty scheme if you want to >> use it without publishing the rest of your code. > > A great summary of GPL in one sentence!
And the reason for the LGPL. IIRC, Ecos from Redhat is an LGPL variant -- you don't have to publish anything to link against Ecos, you only have to publish stuff that modifies Ecos itself. Ditto an embedded Linux in a product -- you only have to publish the embedded Linux parts, not any applications that sit on top of it. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com