From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: tftp filesystem support
Date: Sun, 19 Feb 2012 18:58:03 +0100 [thread overview]
Message-ID: <1329674288-25583-1-git-send-email-s.hauer@pengutronix.de> (raw)
Handling tftp files has been special in barebox since it needs a special
tftp command. This series implements tftp as a regular filesystem, so no
special handling for tftp anymore.
Unfortunately there is no directory read support in tftp, so a mounted
tftp directory will only show an empty directory, but despite what 'ls'
says the files are really there and can (mostly) be accessed like every
other file. The exception to this is that lseek is not possible on tftp
files which means that bootm needs a quirk.
Sascha
Sascha Hauer (5):
Add suport for tftp as a filesystem
make uimages work on tftpfs
net: let net_udp_get_payload return void *
add string for -ETIMEDOUT
copy_file: limit progress bar to sensible limits
common/misc.c | 2 +-
common/uimage.c | 25 +++
fs/Kconfig | 4 +
fs/Makefile | 1 +
fs/tftp.c | 644 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/net.h | 2 +-
lib/copy_file.c | 5 +-
7 files changed, 678 insertions(+), 5 deletions(-)
create mode 100644 fs/tftp.c
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-02-19 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 17:58 Sascha Hauer [this message]
2012-02-19 17:58 ` [PATCH 1/5] Add suport for tftp as a filesystem Sascha Hauer
2012-02-20 4:54 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-20 18:16 ` Sascha Hauer
2012-02-19 17:58 ` [PATCH 2/5] make uimages work on tftpfs Sascha Hauer
2012-02-19 17:58 ` [PATCH 3/5] net: let net_udp_get_payload return void * Sascha Hauer
2012-02-19 17:58 ` [PATCH 4/5] add string for -ETIMEDOUT Sascha Hauer
2012-02-19 17:58 ` [PATCH 5/5] copy_file: limit progress bar to sensible limits Sascha Hauer
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=1329674288-25583-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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