From: Rutger Hofman <rutger@cs.vu.nl>
To: Himanshu Patel <himanshup@aftek.com>
Cc: "'eCos Discuss'" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] FAT32 over NAND
Date: Wed, 21 Jan 2009 20:18:00 -0000 [thread overview]
Message-ID: <497783C5.2020301@cs.vu.nl> (raw)
In-Reply-To: <000b01c97bd1$c5603e10$5020ba30$@com>
Hmmm. I am not familiar with 'mass storage driver'. I assume that it is
a generic Windows thingy for block devices -- I know nothing about
Windows? Or do you mean USB? If you do not mean USB, how is Windows
going to access the device? Through some network? a bus? some other means?
If it goes through USB, I guess you need the uC to intermediate between
USB and the Flash chips. In that case, there are possibilities besides
FAT32.
Rutger
Himanshu Patel wrote:
> Hi,
>
> This will be raw NAND flash.
>
> There are two ways we want to access file system written on NAND flash:
> 1 Through PC
> PC will make use of the file system using mass storage driver.
> 2 Through device itself
> Device (uC) should be able to access read/write files from NAND flash.
>
> Hope I have given the answers you are looking at. If not please free to ask.
>
> Regards,
>
> Himanshu Patel
>
> -----Original Message-----
> From: Rutger Hofman [mailto:rutger@cs.vu.nl]
> Sent: Wednesday, January 21, 2009 7:33 PM
> To: Himanshu Patel
> Cc: 'eCos Discuss'
> Subject: Re: [ECOS] FAT32 over NAND
>
> Sorry to prod, but to answer you appropriately it would be helpful if
> you answer the question below:
>
> Rutger Hofman wrote:
>> Is this a NAND memory smart-card (MMC, SD, USB flash drive or whatever)?
>> These usually come with an FTL on-board, which offers a file system like
>> FAT32. You need no Flash code for that.
>>
>> Is this a raw flash? So, how is it going to be accessed from Windows if
>> the file system is completely in software?
>
> Can you please explain the type of NAND flash you want to use? Is this
> raw flash chips? Or is this a NAND memory 'card' of some type like
> listed above?
>
> Rutger
>
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-01-21 20:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:50 [ECOS] Size of eCos Himanshu Patel
2009-01-20 14:08 ` [ECOS] FAT32 over NAND Himanshu Patel
2009-01-20 14:31 ` Andrew Lunn
2009-01-20 14:40 ` Himanshu Patel
2009-01-20 14:42 ` Rutger Hofman
2009-01-20 15:11 ` Himanshu Patel
2009-01-20 15:15 ` Andrew Lunn
2009-01-20 15:17 ` Himanshu Patel
2009-01-20 18:42 ` Jonathan Larmour
2009-01-20 19:09 ` Paul D. DeRocco
2009-01-21 2:18 ` Jonathan Larmour
2009-01-21 4:26 ` Paul D. DeRocco
2009-01-20 15:14 ` Himanshu Patel
2009-01-20 15:40 ` Rutger Hofman
2009-01-20 16:30 ` Chris Zimman
2009-01-21 13:59 ` Rutger Hofman
2009-01-21 14:08 ` Himanshu Patel
2009-01-21 20:18 ` Rutger Hofman [this message]
2009-01-21 20:54 ` Paul D. DeRocco
2009-01-21 14:12 ` Himanshu Patel
2009-01-21 16:12 ` Chris Zimman
2009-01-21 14:14 ` Himanshu Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497783C5.2020301@cs.vu.nl \
--to=rutger@cs.vu.nl \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=himanshup@aftek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).