> I was in a situation where I missed "strings".
> So here it is
> I started out with cat.c - but ended up re-writing everything.
>
> It has seen light testing on my x86 box.
> Ran it through checkpatch for good measure - fixed a few things.
>
> The location in Makefile seems random, so I jus
On Thu, Sep 15, 2016 at 08:03:26AM +0200, Michael Olbrich wrote:
> address-cells/size-cells can either be set to 1 or 2 for 32 or 63 bit
s/63/64/ ?
Uwe
> addresses respectively. Barebox currently writes 32 bit addresses.
--
Pengutronix e.K. | Uwe Kleine-König
This adds the linux.bootarg device parameter from the network device of
the current nfs connection and adds it to the nfs bootargs line.
This allows booting from nfs without manually setting a ip=dhcp or
ip= option.
Signed-off-by: Enrico Jorns
---
fs/nfs.c | 8
1 file changed, 8 insert
This patches allow booting from nfs without the need to additionally provide an
extra ip= option, such as ip=dhcp to the kernel commandline.
This is solved by adding a bootargs property to the network device of the
connection used for the NFS boot and appending this to the nfs bootarg string.
Not
This sets a `ip=dhcp` or
`ip=::` bootarg for
the network device upon execution of 'ifup'. This is the only point
where we can distinguish between a static ip and a dhcp-based network
setup and thus set a valid bootarg options as it will be required for
nfs boot, for example.
Signed-off-by: Enr
On Mon, Sep 19, 2016 at 06:03:49PM +0200, Enrico Jorns wrote:
> This adds the linux.bootarg device parameter from the network device of
s/bootarg/bootargs/
> the current nfs connection and adds it to the nfs bootargs line.
s/and adds it//
> This allows booting from nfs without manually setting a
