doc: bcm283x: update documentation for Raspberry Pi ...

The old way does not seem to work for RPi 3, as the UART pins are
mapped differently and the NOOBS bootcode does not seem to read a
config.txt.

Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/imx'

Documentation: framebuffer: update documentation to current state ...

Framebuffer console support was added in 2015.

Reported-by: TobSnyder at #barebox irc
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

i.MX/DCD compiler and interpreter: logic is different ...

Reading the manual more carefully discovers a different logic for the
DCD 'check' command. They use the term "until". In order to get the
manual and the software in sync, this change switches to the term
"until" as well. Changing must happen at compiler and interpreter level
to make it work.

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

docs: add reference to libratp-barebox in the remote-control docs ...

Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/fastboot-sparse'

state: Documentation: Fix typo ...

underlaying -> underlying

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

state: Documentation: fix typo ...

Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: Bootchooser: fix typo ...

Signed-off-by: Bastian Stender <bst@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

usb: gadget: fastboot: Add sparse image support ...

Sparse images are needed for fastboot to flash images that do not
fit into memory.

Android fastboot is kind of a dumb protocol. It first sends you a
big image and afterwards it tells you where to put this image. This
of course limits fastboot to files smaller than the available memory.
To bypass this issue fastboot has so called Sparse image support. This
is a new image format that can contain holes in the data so a big image
can be written in multiple steps with holes in other areas each step.

Implementing this for UBI images is kind of tricky since ubiformat
normally expects to get a single image. Preparations to ubiformat
a device in multiple parts have been done in previous patches.
It is however, only for the first part possible to detect if it is
a UBI image. The other parts are just binary data and we cannot
know if we have to pass this data raw to the flash or use ubiformat.
For this reason this patch makes the 'u' flag in the partition
description mandatory for proper UBI image flashing on MTD devices.

fastboot passes a max_download_size variable to the host. This
variable contains the image size fastboot can take in one go.
We have to choose a good compromise here. On one hand we do not
want to risk that we actually do not have enough memory to hold the
transferred image, on the other hand we want images like bootloaders
not as sparse images, but in one go instead to make atomic exchange
of the bootloader possible. Right now we have chosen 8MiB which
should be big enough for all bootloaders. The value is configurable
via global.usbgadget.fastboot_max_download_size.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: USB gadget: Add section for partition description ...

Partition descriptions are used with both fastboot and DFU, so add
a separate section describing them and remove it from the DFU section.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/net'

Merge branch 'for-next/misc'

net: environment: update automounts ...

Instead of using "ifup ethx" use "ifup -a" which works with all
network interfaces. Also replace "$ethx.serverip" with
"$global.net.server". This makes the automount independent of
the actual network interface. Remove all board specific
/env/init/automount files which were only there to use eth1 instead
of the previously hardcoded eth0.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

net: update network docs ...

The network configuration has changed in the previous patches. Update
the documentation accordingly.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: state: mention SD/eMMC devices ...

The state framework also has support for SD/eMMC devices, so mention
them in the documentation.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: remove :numbered: from lower level toctrees ...

Only the highest level toctree may have :numbered:, otherwise
sphinxs complains loudly that the subtree is already numbered.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: defaultenv-2: Change highlight to make ...

It's a make snippet, so change highlighting accordingly.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: change default highlight language to shell ...

There are many places where sphinx complains that blocks cannot
be hilghlighted in 'c' and in fact I am not aware of any C code
snippets in the documentation, so change the default highlighting
style to shell which fits our needs much better. With this we
get rid of many warnings while building the documentation.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: socfpga: Fix numbered list ...

This is no code block, change to numbered list.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: Change many code blocks to no highlight ...

Several blocks cannot be sensibly highlighted, so change the highliting
to 'none'. Fixes many warnings in building the documentation.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: arm-qemu-vexpress: Fix too short underline ...

Fixes sphinx warning about too short underline.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: devicetree: m25p80: fix referenced filename ...

Linux changed the filename in commit 8947e396a829 ("Documentation: dt: mtd:
replace "nor-jedec" binding with "jedec, spi-nor"") and barebox imported this
change in commit 8ed978b79062 ("dts: update to v4.1-rc4").

Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

docs: add qemu vexpress ...

Add a basic command line for QEMU vexpress.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/state'

Merge branch 'for-next/misc'

efi: add iBASE MI991AF documentation. ...

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Documentation: efi: add example how to create EFI partition ...

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

docs/DS1307: fix layout ...

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

state: use the given backend storage type name ...

Change 119f92b already tried to fix it, but
forgets the 'direct' usecase.

The 'backend-storage-type' node is optional. Its default depends on the
capability of the used backend memory, which means "circular" or NULL.
The latter defaults to 'direct' in the routines.
If it is NULL, the devicetree fixup routine skips exporting a
'backend-storage-type' node to the kernel's devicetree.

But currently if the 'backend-storage-type' node is explicitly given as
'direct', it will be skipped silently and set to NULL instead. In this
case the user of the 'barebox-state' tool then ends up with the warning:

"No backend-storage-type found, using default"

which is annoying, because it was given.

Storing the given value will still use a NULL if the
'backend-storage-type' node isn't defined, but stores everything else if
it is defined. Then the 'backend-storage-type' node is present in the
kernel's devicetree as well.

Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>