scripts: imx imx-usb-loader: Fix last transfer error message ...

When doing memory read transfers there will always be 64 bytes
transferred, even when less bytes are requested. This is expected
and there is a test skipping the error message in this case. The
test is wrong though since cnt is not decremented and will never
be equal to rem. Fix the test so that verifying memory does
not give a bogus error message.

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

scripts: imx imx-usb-loader: Add support for i.MX6ull ...

Same as other i.MX6 variants, just add the product id.

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

regsubst.pl: fix typo in help text ...

It seems I did too much assembler stuff ...

Fixes: e7fed4338441 ("scripts: Provide script that helps using cpp defines in dcd tables")
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

scripts/imx: fix out-of-bounds access for big DCD tables ...

add_header_v2 might need a buffer that is bigger than HEADER_LEN
(0x1000) as MAX_DCD * sizeof(u32) (i.e. the maximal size of the dcd
table alone) is already 0x1000. Additionally add_header_v2 adds padding
(usually 0x400) and a struct imx_flash_header_v2 (48). So expand the
buffer size accordingly for v2.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

Merge branch 'for-next/socfpga'

scripts: Provide script that helps using cpp defines in dcd tables ...

This script was used to help create commit 8f426992c562 ("ARM: imx: use
register defines in imxcfg files instead of plain numbers").

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

scripts: socfpga_get_sequencer: update importer ...

Adjust two header files that where renamed in the meantime.
While at it, also remove trailing whitespace and cleanup the
script a little.

Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>

Merge branch 'for-next/ratp'

Merge branch 'for-next/mvebu'

Merge branch 'for-next/misc'

enable LFS support for host programs ...

This fixes building on an XFS partition on a 32 bit machine:

	$ armmake -C ~/gsrc/barebox O=$PWD imx_defconfig
	  HOSTCC  scripts/basic/fixdep
	fixdep: error fstat'ing depfile: scripts/basic/.fixdep.d: Value too large for defined data type

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

scripts/kwboot: document -n option ...

This was forgotten in the commit that added support for that option

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ratp: user close may happen in SYN-RECEIVED state ...

The reference says:

     5.2.3. SYN-RECEIVED
     ...
     Departures
       - A CLOSE request is made by the user.  Create a packet with
         FIN set.  Send it and go to the FIN-WAIT state.

Add this missing step.

Probably not a real usecase for barebox anyway as there is no user
triggered close.

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

ratp: don't ignore data that may arrive in behaviour H1 ...

If an input packet arrives H1 that has data in it, we need to:
  * track sn_received
  * if we have data pending, send it
  * if we don't have data pending, send a plain ACK

This process, as noted in RFC916, is the same as the I1 procedure, so
go and run it:

     Go to the ESTABLISHED state and execute procedure I1 to process
     any data which might be in this packet.

This fix allows the peer to queue data in the last packet doing the
connection establishment. It doesn't apply to the barebox<->bbremote
interaction because bbremote won't queue data until the connection is
completely established, but it allows third party ratp implementations
to do that.

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

ratp: remove FIXME comment: FIN always requires ACK ...

Section 3.4 in the RFC916 shows a packet flow for the connection close
where the initial packet sent by the endpoint starting the close has
just the FIN flag set, without an ACK:

          -->     <SN=0><AN=1><CTL=FIN>
                <SN=1><AN=1><CTL=FIN,ACK>  <--
          -->     <SN=1><AN=0><CTL=ACK>

This may lead to think that it is actually allowed to send the initial
packet with just FIN set, without ACK-ing any other packet from the
peer.

But, this is actually not possible, the packet MUST be ACK-ing a
previous packet from the peer, even if this is just a duplicated ACK,
because otherwise the packet with the FIN wouldn't get processed in
the H2 behavior (FIN processing) of the peer, as the F2 behavior (ACK
processing) would filter it out.

This is actually the same reasoning why data packets always have ACK
set, even if the same ACK has already been sent previously (e.g. with
a simple ACK packet without data); if they didn't have it, they would
be filtered out in the F2 behavior, never arriving the I1 behavior,
which is where the received data is processed.

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

ratp: remove bogus data checks in behavior C2 ...

The SN validation was being completely ignored if the packet had no
data (e.g. for RST, FIN or SYN or plain ACKs). This condition is now
removed so that the SN check is done.

The second check removed was actually never being used, as it was
already being tested for not having data in the first one.

These two fixes are a cleanup to follow the protocol correctly.

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

ratp: fix data presence check ...

Looking at the "data length" and SO flag isn't enough to declare a
packet with or without data, because SYN flagged packets will also use
the "data length" field to define MDL.

So, improve the check to match against SYN|RST|FIN flagged packets,
which can never have data.

This commit fixed a segfault in barebox when an unexpected SYN packet
was sent in the middle of a connection; barebox thought the packet had
data because the "data length" in the SYN packet was different than 0.

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

scripts/kwbimage: support empty binary.0 files ...

While it doesn't make sense to use empty binary headers on a machine for
first stage, it is convenient to support this for build testing.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/misc'

new make helper to decode binaries using base64 ...

This is helpful to provide mvebu binary.0 images with a patch. When
added directly a binary patch is needed which isn't understood by
patch(1).

As it's (at least) unclear if these images are distributable in general
I don't provide a patch making use of this, but the pattern is as
follows: Add

	$(obj)/start_netgear_rn2120.pblx.kwbimg: $(board)/netgear-rn2120/binary.0

to images/Makefile.mvebu and then put a binary.0.base64 into the board
folder.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

imx-usb-loader: add prefix '0x' for hex value ...

Signed-off-by: Stefan Lengfeld <contact@stefanchrist.eu>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Fix linking with new ld, based on u-boot ...

U-boot commit info:
http://git.denx.de/?p=u-boot.git;a=commit;h=e391b1e

Signed-off-by: Andrey Panov <rockford@yandex.ru>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/socfpga'

ARM: socfpga: add arria10 support ...

Arria10 is a SoC + FPGA like the Cyclone5 SoCFPGA that
is already supported in barebox.
Both a the same in some parts, but totaly different in
others. Most of the hardware blocks are the same in the
SoC parts. The OCRAM is larger on the Arria10 and the
SDRAM controller is different.
The serial core only supports 32bit accesses (different to
the 8bit accesses on the Cyclone5).

As Arria10 has 256KB of OCRAM, it is possible to fit a larger
barebox (and/or use PBL) instead of the two stage bootprocess
used on the Cyclone5 and its 64KB OCRAM.

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

ARM: socfpga: rename socfpga->cyclone5 ...

Prepare the SoCFPGA code base for different system types
(Arria10, Stratix10,...).

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

scripts: mkmakefile: apply changes from Linux kernel ...

The version of mkmakefile which has been used in barebox until now dates
back to commit fd5f0cd from the Linux
kernel git history (Tue May 2 12:33:20 2006 +0200).
This patch effectively includes all changes from the aforementioned
commit to the latest stable version of the Linux kernel:

git log --pretty=oneline --abbrev-commit fd5f0cd..v4.10 scripts/mkmakefile
06ed5c2 kbuild: Make scripts executable
9319f45 kbuild: support simultaneous "make %config" and "make all"
0ff3577 kbuild: silence generated makefile message
3c955b4 fixes for using make 3.82
d230124 kbuild: teach mkmakfile to be silent
1d3b3bf kbuild: scripts/mkmakefile: dynamic determination of output directory
971edcf kbuild: re-enable Makefile generation in a new O=... directory
18c32da kbuild: fix building with O=.. options
0b35786 kbuild: call make once for all targets when O=.. is used

In particular, the list of changes includes a fix for the following
Make warning:

  Makefile:18: *** mixed implicit and normal rules: deprecated syntax

GNU Make 3.82 raises an error instead of a warning and aborts the
make process. GNU Make 3.82 is still used today by distributions
like Red Hat Enterprise Linux 7.3.

Signed-off-by: Dennis Menschel <menschel-d@posteo.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

tags: Process Kconfig files in a single pass ...

This is an adoption of the linux kernel commit

| commit a281b85
| Author: Michal Marek <mmarek@suse.com>
| Date:   Wed Oct 14 11:17:13 2015 +0200
|
|     tags: Process Kconfig files in a single pass
|
|     Signed-off-by: Michal Marek <mmarek@suse.com>

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

tags: Do not try to index defconfigs ...

This is an adoption of the linux kernel commit

| commit ab9ca61
| Author: Michal Marek <mmarek@suse.com>
| Date:   Thu Oct 15 11:14:02 2015 +0200
|
|     tags: Do not try to index defconfigs
|
|     The defconfig files are in predictable locations, so there is no need to
|     index them. Plus, the script was only looking for files named
|     'defconfig', which only works on a few architectures nowadays.
|
|     Signed-off-by: Michal Marek <mmarek@suse.com>

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

scripts/tags.sh: drop __TestClearPage*() helpers ...

This is an adoption of the linux kernel commit

| commit 685eaad
| Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
| Date:   Fri Jan 15 16:52:10 2016 -0800
|
|     page-flags: drop __TestClearPage*() helpers
|
|     Nobody uses them.
|
|     Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
|     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
|     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/mvebu'