From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum
Date: Mon, 01 Oct 2018 15:08:00 +0200 [thread overview]
Message-ID: <20181001130800.C563C240043@gemini.denx.de> (raw)
In-Reply-To: <20181001094646.11539-1-christian.gmeiner@gmail.com>
Dear Christian,
In message <20181001094646.11539-1-christian.gmeiner@gmail.com> you wrote:
> From: Thomas RIENOESSL <thomas.rienoessl@bachmann.info>
>
> Prep. work to support nfs v1.
Hm... as you are putting efforts into NFS support...
Here comes a more general question:
I wonder if it's worth the work on NFS at all, or if we should
remove NFS support from U-Boot alltogether?
1) We support only NFS v2 (and v3) in U-Boot, and most standard Linux
distros support only v4 in their default configurations.
2) We support only UDP, but most standard Linux distros support only
TCP in their default configurations (see [1])
[1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=fbd7623dd8d5e418e7cb369d4026d5368f7c46a6
Try a NFS download from any recent Linux distro (i. e. one including
nfs-utils 2.3.1 or later)...
I feel a half-way solution is unsatisfactory, but the way for the
Real Thing (TM) is a pretty long one...
The fact that nobody compained yet that NFS stopped working fo him
suggests that there are only very, very few users of NFS at all.
If one of these is willing to step up and fix this for real, he is
of course more than welcome. But if not - should we not remove the
more or less obsolete code?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Microsoft Multitasking:
several applications can crash at the same time.
next prev parent reply other threads:[~2018-10-01 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 9:46 [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum Christian Gmeiner
2018-10-01 9:46 ` [U-Boot] [PATCH 2/4] nfs: factor out generic reply error handling Christian Gmeiner
2018-10-01 9:46 ` [U-Boot] [PATCH 3/4] nfs: handle rpc errors for mount calls Christian Gmeiner
2018-10-01 9:46 ` [U-Boot] [PATCH 4/4] net: add NFSv1 support Christian Gmeiner
2018-10-01 13:08 ` Wolfgang Denk [this message]
2018-10-01 13:56 ` [U-Boot] [PATCH 1/4] nfs: convert supported_nfs_versions bitfield to an enum Christian Gmeiner
2018-10-22 18:53 ` Joe Hershberger
2018-10-22 19:39 ` Simon Goldschmidt
2018-10-29 20:05 ` Joe Hershberger
2018-10-29 22:13 ` Tom Rini
2018-10-30 8:46 ` Wolfgang Denk
2018-10-30 8:53 ` Simon Goldschmidt
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=20181001130800.C563C240043@gemini.denx.de \
--to=wd@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.