mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Daniel Schultz <d.schultz@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4] arm: boards: phytec-som-am335x: Update boot scripts
Date: Tue, 20 Jun 2017 17:37:56 +0200	[thread overview]
Message-ID: <f7fcf91d-0079-f9b0-51a3-5882e92abb6b@phytec.de> (raw)
In-Reply-To: <20170619072511.x6gmx5oa7u7eiprq@pengutronix.de>

Hi Sascha,

Am 19.06.2017 um 09:25 schrieb Sascha Hauer:
> On Tue, Jun 13, 2017 at 03:37:08PM +0200, Daniel Schultz wrote:
>> Expand the boot scripts with EMMC and add a default file source for
>> expansions.
>>
>> Removed "rw" and "rootwait" bootargs from existing boot scripts.
>> Added "rootflags='data=journal'" bootarg to SD card boot script.
>>
>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>> ---
>> +#!/bin/sh
>> +
>> +path="/mnt/tftp"
>> +
>> +global.bootm.image="${path}/${global.user}-linux-${global.hostname}"
>> +
>> +oftree="${path}/${global.user}-oftree-${global.hostname}"
>> +if [ -f "${oftree}" ]; then
>> +    global.bootm.oftree="$oftree"
>> +fi
>> +
>> +nfsroot="/nfsroot/${global.hostname}"
> 
> This assumed there is one nfsroot for all users. The intention with the
> original naming was that each user can create a link in his home
> directory to wherever the nfsroot lives, which may include some globally
> available nfsroot for all users. Why change it?
> 
Seems like this was an older script. We will switch to the Barebox 
network boot script.

>> +bootargs-ip
>> +
>> +global.linux.bootargs.dyn.root="root=/dev/nfs nfsroot=$nfsroot,vers=3,udp"
> 
> Why udp? Normally tcp is preferred, no?
> 
UDP is used as default by the nfsroot kernel system and also by tftp.
Additionally, we had troubles with booting in tcp mode.

> Sascha
> 

-- 
Mit freundlichen Grüßen,
With best regards,
   Daniel Schultz

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

      reply	other threads:[~2017-06-20 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 13:37 Daniel Schultz
2017-06-13 13:42 ` Daniel Schultz
2017-06-19  7:25 ` Sascha Hauer
2017-06-20 15:37   ` Daniel Schultz [this message]

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=f7fcf91d-0079-f9b0-51a3-5882e92abb6b@phytec.de \
    --to=d.schultz@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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