Signed-off-by: Héctor Orón Martínez <zumbi@debian.org>

  - Allwinner R16 EVB (Parrot)
  - INet-86DZ Rev 01
  - Olimex A33-OLinuXino
  - Polaroid MID2407PXE03 tablet

Add a machine db entry for DragonBoard 410c, a 96Boards device based
on a Qualcomm Snapdragon 410 with Adreno 306 GPU.

Add a machine db entry for NVIDIA Jetson TX1 Developer Kit, a device
based on Tegra 210.

If a DTB is specified and if the DTB file doesn't exist, we should
produce an error instead of printing the DTB ID and then doing
nothing.  Closes: #833097

Add uboot-generic boot script for ARM64 based on the armhf version.
It uses booti instead of bootz.  bootz refers to the zImage which
is only an ARM image type.  ARM64 uses booti.

I also removed some code which is specific to an armhf platform.

Discussion for the record:
https://lists.debian.org/debian-boot/2016/07/msg00283.html

As of 3.19-rc1, DTBs on arm64 are placed in vendor subdirectories,
i.e. vendor/dtb.  Handle such DTBs by searching the whole kernel
hierarchy.

The DTB continues to be installed in dtbs/kvers/dtb (without a
vendor subdirectory) because the boot script looks for
for dtbs/${fk_kvers}/${fdtfile} and $fdtfile doesn't contain the
vendor subdir.

The current approach assumes that DTB filenames are unique when
disregarding the vendor dir.  I believe this is a pretty safe
assumption since DTB filenames start with the platform name.
If the assumption turns out to be incorrect in the future, we can
add the vendor dir to DTB-Id where needed and change the code to
look for vendor/dtb before looking for just dtb.

This approach was discussed here:
https://lists.debian.org/debian-boot/2016/07/msg00281.html

 - Colorfly E708 Q1 tablet
 - Difrnce DIT4350
 - Dserve DSRV9703C
 - Polaroid MID2809PXE04 tablet
 - Xunlong Orange Pi One
 - Xunlong Orange Pi PC
 - Xunlong Orange Pi 2

This reverts commit f1f502fb.

This reverts commit 1733a110.

 - Allwinner A83T H8Homlet Proto Dev Board v2.0
 - Cubietech Cubietruck Plus
 - ICnova-A20 SWAC
 - iNet-9F Rev 03
 - Itead Ibox A20
 - Sinlinx SinA31s Development Board
 - A10s-Wobo i5
 - Yones TopTech BS1078 v2 Tablet

The issue occurs because a few linkstation devices use a script to detect
DTB shiped by kernel per version, and that script is also invoked after
kernel package upgrading or removing, which results in all kernel files
are removed including DTB. In this condition the linkstation specific script
fails to detect DTB, so flash-kernel hooks script fails, and finally triggers
kernel package upgrading or removing failing.

The fix is simply return a fake DTB as warning message instead of error,
when the kernel lib directory of the specific version doesn't exist.

Add DTB support for "Buffalo/Revogear Kurobox Pro" from kernel 4.5.1