mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/5] Add suport for tftp as a filesystem
Date: Mon, 20 Feb 2012 19:16:39 +0100	[thread overview]
Message-ID: <20120220181639.GX3852@pengutronix.de> (raw)
In-Reply-To: <20120220045437.GC27599@game.jcrosoft.org>

On Mon, Feb 20, 2012 at 05:54:37AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 18:58 Sun 19 Feb     , Sascha Hauer wrote:
> > This adds tftp filesystem support. It currently duplicates
> > significant amounts of the tftp (command) support. This is ok
> > since we can eventually drop the original tftp command later.
> > 
> > tftp is not really suitable to be handled as a filesystem. It lacks
> > support for stat, reading directories and other things. Handling
> > it as a filesystem has one big advantage though: tftp is no special
> > case for boot scripts and/or commands anymore which makes them simpler.
> > 
> > This implementation has some improvements to the original tftp command.
> > It supports blocksize negotiation which speeds up transfers if the tftp
> > server supports it. Also we can determine the filesize to transfer if
> > the remote end supports it.
> > 
> look good do you have seach patch for nfs?

No, everyone is invited to implement it ;)

NFS is a bit more complicated than tftp though. The implementation we
have lacks readdir support, so we have to figure out how to do this
first.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-02-20 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 17:58 tftp filesystem support Sascha Hauer
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 [this message]
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=20120220181639.GX3852@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=plagnioj@jcrosoft.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