From: Sergei Shtylyov <sshtylyov@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] FAT: Add FAT write feature
Date: Tue, 16 Aug 2011 15:33:51 +0400 [thread overview]
Message-ID: <4E4A559F.9090308@mvista.com> (raw)
In-Reply-To: <1313490166-27223-1-git-send-email-dg77.kim@samsung.com>
Hello.
On 16-08-2011 14:22, Donggeun Kim wrote:
> In some cases, saving data in RAM as a file with FAT format is required.
> This patch allows the file to be written in FAT formatted partition.
>
> The usage is similar with reading a file.
> First, fat_register_device function is called before file_fat_write function
> in order to set target partition.
> Then, file_fat_write function is invoked with desired file name,
> start ram address for writing data, and file size.
>
> Signed-off-by: Donggeun Kim<dg77.kim@samsung.com>
> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
I have recently submitted the patch fixing FAt code crash with sector
sizes > 512 bytes [1]. You probably should take it into account.
[1] http://marc.info/?l=u-boot&m=131283284822789
WBR, Sergei
next prev parent reply other threads:[~2011-08-16 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 10:22 [U-Boot] [PATCH] FAT: Add FAT write feature Donggeun Kim
2011-08-16 11:33 ` Sergei Shtylyov [this message]
2011-10-06 21:54 ` Wolfgang Denk
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=4E4A559F.9090308@mvista.com \
--to=sshtylyov@mvista.com \
--cc=u-boot@lists.denx.de \
/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