Bug#833561: arm64: dtbs no longer installed in vendor subdir

[Martin Michlmayr]

* Ian Campbell  [2016-08-06 11:38]:
> But indeed in https://packages.debian.org/experimental/arm64/linux-imag
> e-4.7.0-rc7-arm64-unsigned/filelist the subdirectory is missing.

linux-image-4.7.0-rc3-arm64-unsigned from snapshot has the problem too.

-- 
Martin Michlmayr
http://www.cyrius.com/

Processed: retitle 832359 to linux-kbuild: Include "scripts/headers_install.sh" and "scripts/unifdef", needed by "scripts/Makefile.headersinst"

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 832359 linux-kbuild: Include "scripts/headers_install.sh" and 
> "scripts/unifdef", needed by "scripts/Makefile.headersinst"
Bug #832359 [linux-kbuild-4.6] linux-kbuild include useless Makefile.headersinst
Changed Bug title to 'linux-kbuild: Include "scripts/headers_install.sh" and 
"scripts/unifdef", needed by "scripts/Makefile.headersinst"' from 'linux-kbuild 
include useless Makefile.headersinst'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
832359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833561: arm64: dtbs no longer installed in vendor subdir

[Ian Campbell]

On Sat, 2016-08-06 at 11:14 +0100, Ian Campbell wrote:
> On Fri, 2016-08-05 at 18:37 -0700, Martin Michlmayr wrote:
> > 
> > I ran dtbs_install manually to verify:
> > 
> > ARCH=arm64 make  -n -C debian/build/build_arm64_none_arm64
> > dtbs_install INSTALL_DTBS_PATH=/home/tbm/debian/linux-4.7~rc7/x
> > echo '  INSTALL arch/arm64/boot/dts/amd/amd-overdrive.dtb'; mkdir
> > -p
> > /home/tbm/debian/linux-4.7~rc7/x; cp arch/arm64/boot/dts/amd/amd-
> > overdrive.dtb /home/tbm/d ebian/linux-4.7~rc7/x
> 
> With pristine upstream 4.7-rc7 I see the subdirs, must be something
> in
> our local patches?
> 
> $ make ARCH=arm64 defconfig dtbs dtbs_install
> INSTALL_DTBS_PATH=$HOME/tmp/dtbs -j12 CROSS_COMPILE=aarch64-linux-
> gnu- -s &&  find ~/tmp/dtbs | head -n 10
> /home/ijc/tmp/dtbs
> /home/ijc/tmp/dtbs/altera
> /home/ijc/tmp/dtbs/altera/socfpga_stratix10_socdk.dtb
> /home/ijc/tmp/dtbs/mediatek
> /home/ijc/tmp/dtbs/mediatek/mt6795-evb.dtb
> /home/ijc/tmp/dtbs/mediatek/mt8173-evb.dtb
> /home/ijc/tmp/dtbs/broadcom
> /home/ijc/tmp/dtbs/broadcom/ns2-svk.dtb
> /home/ijc/tmp/dtbs/broadcom/vulcan-eval.dtb
> /home/ijc/tmp/dtbs/amd

Things seem ok with the debian/4.7_rc7-1_exp1 tag in our git repo:

git reset --hard debian/4.7_rc7-1_exp1
git clean -fdqx debian
./debian/rules orig
./debian/rules debian/control
make -f debian/rules.gen setup_arm64
cd debian/build/build_arm64_none_arm64/
rm -rf ~/tmp/dtbs && make ARCH=arm64 dtbs dtbs_install 
INSTALL_DTBS_PATH=$HOME/tmp/dtbs CROSS_COMPILE=aarch64-linux-gnu- -s &&  find 
~/tmp/dtbs | head -n 10

Results in :
/home/ijc/tmp/dtbs
/home/ijc/tmp/dtbs/amd
/home/ijc/tmp/dtbs/amd/amd-overdrive.dtb
/home/ijc/tmp/dtbs/amd/amd-overdrive-rev-b1.dtb
/home/ijc/tmp/dtbs/amd/amd-overdrive-rev-b0.dtb
/home/ijc/tmp/dtbs/amd/husky.dtb
/home/ijc/tmp/dtbs/nvidia
/home/ijc/tmp/dtbs/nvidia/tegra210-smaug.dtb
/home/ijc/tmp/dtbs/nvidia/tegra132-norrin.dtb
/home/ijc/tmp/dtbs/nvidia/tegra210-p2371-2180.dtb

Or similar to your original:

$ make -n -C debian/build/build_arm64_none_arm64/ dtbs_install 
INSTALL_DTBS_PATH=$HOME/tmp/dtbs V=1 | head -n 15
make: Entering directory 
'/local/scratch/ijc/development/debian/pkg-kernel/master.git/debian/build/build_arm64_none_arm64'
make -C /local/scratch/ijc/development/debian/pkg-kernel/master.git 
O=/local/scratch/ijc/development/debian/pkg-kernel/master.git/debian/build/build_arm64_none_arm64/.
 dtbs_install
make -C 
/local/scratch/ijc/development/debian/pkg-kernel/master.git/debian/build/build_arm64_none_arm64
 KBUILD_SRC=/local/scratch/ijc/development/debian/pkg-kernel/master.git \
-f /local/scratch/ijc/development/debian/pkg-kernel/master.git/Makefile 
dtbs_install
/local/scratch/ijc/development/debian/pkg-kernel/master.git/Makefile:681: 
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not 
supported by compiler
make -f 
/local/scratch/ijc/development/debian/pkg-kernel/master.git/scripts/Makefile.dtbinst
 obj=arch/arm64/boot/dts
mkdir -p /home/ijc/tmp/dtbs
make -f 
/local/scratch/ijc/development/debian/pkg-kernel/master.git/scripts/Makefile.dtbinst
 obj=arch/arm64/boot/dts/al
make[4]: Nothing to be done for '__dtbs_install'.
make -f 
/local/scratch/ijc/development/debian/pkg-kernel/master.git/scripts/Makefile.dtbinst
 obj=arch/arm64/boot/dts/altera
make[4]: Nothing to be done for '__dtbs_install'.
make -f 
/local/scratch/ijc/development/debian/pkg-kernel/master.git/scripts/Makefile.dtbinst
 obj=arch/arm64/boot/dts/amd
echo '  mkdir -p /home/ijc/tmp/dtbs/amd; cp 
arch/arm64/boot/dts/amd/amd-overdrive.dtb /home/ijc/tmp/dtbs/amd'; mkdir -p 
/home/ijc/tmp/dtbs/amd; cp arch/arm64/boot/dts/amd/amd-overdrive.dtb 
/home/ijc/tmp/dtbs/amd
echo '  mkdir -p /home/ijc/tmp/dtbs/amd; cp 
arch/arm64/boot/dts/amd/amd-overdrive-rev-b0.dtb /home/ijc/tmp/dtbs/amd'; mkdir 
-p /home/ijc/tmp/dtbs/amd; cp arch/arm64/boot/dts/amd/amd-overdrive-rev-b0.dtb 
/home/ijc/tmp/dtbs/amd
echo '  mkdir -p /home/ijc/tmp/dtbs/amd; cp 
arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dtb /home/ijc/tmp/dtbs/amd'; mkdir 
-p /home/ijc/tmp/dtbs/amd; cp arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dtb 
/home/ijc/tmp/dtbs/amd
echo '  mkdir -p /home/ijc/tmp/dtbs/amd; cp arch/arm64/boot/dts/amd/husky.dtb 
/home/ijc/tmp/dtbs/amd'; mkdir -p /home/ijc/tmp/dtbs/amd; cp 
arch/arm64/boot/dts/amd/husky.dtb /home/ijc/tmp/dtbs/amd

But indeed in https://packages.debian.org/experimental/arm64/linux-imag
e-4.7.0-rc7-arm64-unsigned/filelist the subdirectory is missing.

I'm at a complete loss as to why you and the buildd have such different
results.

Bug#833561: arm64: dtbs no longer installed in vendor subdir

[Ian Campbell]

On Fri, 2016-08-05 at 18:37 -0700, Martin Michlmayr wrote:
> I ran dtbs_install manually to verify:
> 
> ARCH=arm64 make  -n -C debian/build/build_arm64_none_arm64
> dtbs_install INSTALL_DTBS_PATH=/home/tbm/debian/linux-4.7~rc7/x
> echo '  INSTALL arch/arm64/boot/dts/amd/amd-overdrive.dtb'; mkdir -p
> /home/tbm/debian/linux-4.7~rc7/x; cp arch/arm64/boot/dts/amd/amd-
> overdrive.dtb /home/tbm/d ebian/linux-4.7~rc7/x

With pristine upstream 4.7-rc7 I see the subdirs, must be something in
our local patches?

$ make ARCH=arm64 defconfig dtbs dtbs_install INSTALL_DTBS_PATH=$HOME/tmp/dtbs 
-j12 CROSS_COMPILE=aarch64-linux-gnu- -s &&  find ~/tmp/dtbs | head -n 10
/home/ijc/tmp/dtbs
/home/ijc/tmp/dtbs/altera
/home/ijc/tmp/dtbs/altera/socfpga_stratix10_socdk.dtb
/home/ijc/tmp/dtbs/mediatek
/home/ijc/tmp/dtbs/mediatek/mt6795-evb.dtb
/home/ijc/tmp/dtbs/mediatek/mt8173-evb.dtb
/home/ijc/tmp/dtbs/broadcom
/home/ijc/tmp/dtbs/broadcom/ns2-svk.dtb
/home/ijc/tmp/dtbs/broadcom/vulcan-eval.dtb
/home/ijc/tmp/dtbs/amd

Ian.

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Chris Rhodin]

On 08/02/2016 16:56, Ben Hutchings wrote:

On Mon, 2016-08-01 at 22:51 -0700, Chris Rhodin wrote:
[...]

I get this from dmesg.  I'm assuming the new error -2 indicates the file
was not found.

[...]

Yes.  And the other error code (-110) indicates a time-out.

Can you test whether the attached patch fixes this?  You can do this by
following the instructions at
.

Ben.


Hi Ben,

That worked.  All four ports can now connect and communicate.  I haven't 
tested handshaking, hardware or software.


I did have to export "ezusb_writememory" from ezusb.c.


Chris

Missing firmware (dvb_rio.inp) on firmware-siano package.

[Eugenio J . Vidal García]

Dear maintainers.

I've recently bought a dvb usb stick that is identified as a Siano Rio
Digital Receiver and it needs the firwmare dvb_rio.inp to work.

I was wondering if could it be possible to include this file in the
firmware-siano package?

The file is available in:
https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb_rio.inp

And what I think it's the license is available in:
https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/LICENCE.siano

---

dmesg output:

[ 1349.608096] usb 5-1: new high-speed USB device number 3 using ehci-pci
[ 1349.741487] usb 5-1: New USB device found, idVendor=187f, idProduct=0600
[ 1349.741498] usb 5-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 1349.741504] usb 5-1: Product: MDTV Receiver
[ 1349.741509] usb 5-1: Manufacturer: MDTV Receiver
[ 1349.742890] usb 5-1: firmware: direct-loading firmware dvb_rio.inp
[ 1350.200575] DVB: registering new adapter (Siano Rio Digital Receiver)
[ 1350.201096] usb 5-1: DVB: registering adapter 0 frontend 0 (Siano Mobile
Digital MDTV Receiver)...

---

The device works fine with this firmware.
(Tested on Debian stable; Linux 3.16.0-4-686-pae #1 SMP Debian
3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux)

I live in Europe where the DVB-T system is used.
I only need to change the default mode of the driver adding a config file
named smsmdtv.conf in /etc/modprobe.d/ with the line:

options smsmdtv default_mode=4

What if I'm not wrong enables DEVICE_MODE_DVBT_BDA as the default mode.
(Referenced by the kernel sources in:
/linux-4.7/drivers/media/common/siano/smscoreapi.h)
(Not sure if DEVICE_MODE_DVBT_BDA comes from Broadcast Driver Architecture
but with the default DEVICE_MODE_DVBT does not work.)

---
Thanks in advance.
Eugeni.