April 2018 - dev - example.com

[PATCH] update kernel for raspberry pi, fixes kodi startup
by Oliver Schib 29 Apr '18

29 Apr '18

Signed-off-by: Oliver Schib <oliver.schib(a)gmx.ch> --- target/linux/Config.in.kernelversion | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/Config.in.kernelversion b/target/linux/Config.in.kernelversion index 7ae671271..2979f26ab 100644 --- a/target/linux/Config.in.kernelversion +++ b/target/linux/Config.in.kernelversion @@ -204,7 +204,7 @@ config ADK_TARGET_LINUX_KERNEL_GIT depends on ADK_TARGET_LINUX_KERNEL_VERSION_GIT default "6064a9bdf48cefbccc4f6472dd04251f0dec1931" if ADK_TARGET_ARCH_CSKY default "6a2f2e4198eaff63ee75f6085ce9f966c47b4441" if ADK_TARGET_ARCH_LM32 - default "d3126c92d6bcf88e3325b976c0284e45e0cc85c9" if ADK_TARGET_BOARD_BCM28XX + default "e5c309d32b8b0e1c2b05b2f1d37b86cbec3c38de" if ADK_TARGET_BOARD_BCM28XX default "f8d3b2a0fa5054aaed0f14cd457db9d8922bb167" if ADK_TARGET_SYSTEM_ADSP_BF537 default "e7c8afc1dda7b7c18596d90ad6a17ae886650b72" if ADK_TARGET_SYSTEM_KINETIS_K70 default "902739f3353150ac9eb69ad995098f3079d862a3" if ADK_TARGET_SYSTEM_SOLIDRUN_CLEARFOG -- 2.11.0

1 0

kodi and brutefir
by Oliver Schib 04 Apr '18

04 Apr '18

Hi everyone In the last few weeks I have tried getting brutefir to work with kodi in openadk. My goal is to get room correction with kodi on my pi2. :-) While it is quite simple to use the brutefir convolution engine with mpd through jack, this does not work so easily in kodi, since kodi does not support jack. At least there is no official support as far as I'm aware. Now one possibility would be to try and implement jack support in kodi which I think would be rather hard, or maybe see if someone else has done something that could be used. However, there seems to be an easier way. For alsa there is a loopback driver called 'aloop' available in the linux kernel. Basically it simply adds a 'virtual loopback cable' device. This means the audio you play through this device will be available for capture in another device. You can find more on it here:https://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_brid… the idea is straight-forward: Set up kodi to play through this loopback device instead of the speakers, use the other end as input for brutefir, filter the audio and have brutefir output to the speakers. I tried it out, and I think I'm close to having it work. If you are interested, here is a proof of concept:- build adk with e.g. convolution, kodi and ADK_LINUX_KERNEL_SND_ALOOP.- start brutefir:$ brutefir -nodefault config.confwhere config.conf is the attached brutefir cofig file.- play an audio file: $ audio.wav -Dhw:0 On my pi2 with a hifiberry DAC+ installed this will play the brutefir-filtered audio through the hifiberry. If you don't have one, you may need to modify the config file. Now I don't quite have it working with kodi yet.With SND_ALOOP enabled, kodi's audio settings show 5 devices:1 PI: HDMI2 PI: Analogue3 PI: HDMI and Analogue 4 ALSA: Loopback (@CARD=Loopback,DEV=0), LoopbackPCM5 ALSA: Loopback (surround21:CARD=Loopback,DEV=0), Loopback PCM Note that the hifiberry (which works fine in kodi without aloop) is missing here. Why is that? Something seems not quite right.Also, when I select number 4 from the above, audio will be played through the berry even when brutefir is not running. And it is playing at full volume, ignoring kodi's volume setting, which does not sound nice at all.So something is clearly no ok yet.I do not have an asound file at this point (I think none should be needed?)Does anyone have an idea what I'm missing? Thanks for any ideasAll the bestOliver P.S.Here are some aplay/arecord outputs for reference: $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 $ aplay -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=Loopback Loopback, Loopback PCM Default Audio Device sysdefault:CARD=Loopback Loopback, Loopback PCM Default Audio Device front:CARD=Loopback,DEV=0 Loopback, Loopback PCM Front speakers surround21:CARD=Loopback,DEV=0 Loopback, Loopback PCM 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.0 Surround output to Front and Rear speakers surround41:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Loopback,DEV=0 Loopback, Loopback PCM 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers default:CARD=sndrpihifiberry snd_rpi_hifiberry_dacplus, Default Audio Device sysdefault:CARD=sndrpihifiberry snd_rpi_hifiberry_dacplus, Default Audio Device $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 $ arecord -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=Loopback Loopback, Loopback PCM Default Audio Device sysdefault:CARD=Loopback Loopback, Loopback PCM Default Audio Device front:CARD=Loopback,DEV=0 Loopback, Loopback PCM Front speakers surround21:CARD=Loopback,DEV=0 Loopback, Loopback PCM 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.0 Surround output to Front and Rear speakers surround41:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Loopback,DEV=0 Loopback, Loopback PCM 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers

2 4

broken kernel download
by Diez B. Roggisch 04 Apr '18

04 Apr '18

Hi, while working on a new project I discovered that the recent introduction of "waldux" (?) in the pretty massive commit 9bb871a0bb4c239239944d28bd4d5cfa19d84f62 breaks the kernel download mechanism for the raspberry pi. The error seems to be related to double-quotes around the hash. These confuse the mechanism in fetch.mk that tries to work out a way to generate the hash-named archive. It will then fail to extract the sources. You can reproduce by deep-cloning https://github.com/deets/pififorwarder.git via git clone --recursive then change into the modules/openadk folder and check out the above mentioned command. Then just run ../../scripts/build.py, and you should get a non-working build. I'm also having troubles enforcing GLIBC through the task that you can find in configs/tasks. Regardless of what I try to put in there (after manually setting the libc to glibc) - the task can't seem to control this choice. I noticed a similar problem with the kernel configuration: the task can't override the selected kernel anymore. It can only be affected by running menuconfig and manually changing this :( This is not visible in the repository, but I can reproduce it if you like. Any suggestions on how to overcome this? Cheers, Diez

2 3