00:04 <Armbian-Discord> <I​gorPec> try building focal for jethub board

00:06 <IgorPec> i noticed this problem in our CI

00:40 <nekomancer[m]> jethub?

00:48 <lanefu> Yeah it's an amlogic board for automation by a Russian company

00:49 <lanefu> They've been really great examples of a vendor adding support for their own devices

00:58 <Armbian-Discord> <r​pardini> I'm building some release, will build focal jethub soon

01:00 <c0rnelius> Adding support for their own devices? Does include custom patching to bluez?

01:19 <c0rnelius> Yeah Mayfield is looking like Hurricane Andrew hit it. But just in like a few mile radius.

01:20 <c0rnelius> Sorry, wrong channel.

01:30 <lanefu> Can't speak to the bluez patch

01:32 <lanefu> Bleh yeah I grew up in KY always tornadoes more amazing how little they hit frankly

01:33 <lanefu> But yeah steel buildings don't stand a chance

01:33 <c0rnelius> I don't know that they need it or do so, but for example the Foundation does `they don't need too` but they do anyway. As a matter of fact Ubuntu even applies the patches across arm now.

01:34 <c0rnelius> lanefu: Yeah looks like a mess. There goes X-Mas.

01:36 <c0rnelius> I'm not sure whats worse, getting hit be Andrew in Summer or hit by `whatever that was` at the start of winter. Gotta feel for those people.

01:37 <lanefu> Yeah still don't have any context on bluez patching haven't been following

01:37 <c0rnelius> this is what Ubuntu and the foundation do -> https://github.com/pyavitz/pi-bluetooth/blob/bluez-patches/bluez-raspi-support.patch

01:38 <lanefu> "the foundation" being rpi foundation?

01:38 <c0rnelius> You can simply just link /lib/firmware to /etc/firmware and fix the whole problem.

01:38 <c0rnelius> Yeah RPI

01:40 <c0rnelius> They do it to prevent the AA:AA:AA:AA:AA that would show its self in bluetooth, but of course over thought the problem.

01:46 <lanefu> So looks like /etc/firmware is intended to be for additional firmware not shipped by a distro

01:47 <lanefu> Really seems like bluez problem is it's not following what other Kernel modules do and observe the directory heirachy

01:48 <lanefu> Tldr I wouldn't symlink the whole dir /lib/firmware to /etc/firmware either

02:18 <c0rnelius> lanefu: Well it works, also if follow how the kernel actually observes firmware it doesn't break anything.

02:19 <c0rnelius> Putting the link in place that is

02:20 <c0rnelius> So putting the link in place just allows stupid boards like the Pi to find it without needing to patch a whole deb package and make ur own.

02:21 <c0rnelius> This also seems to vary between systemd vs sysvinit systems.

02:22 <c0rnelius> This is the real key -> https://www.kernel.org/doc/html/v4.17/driver-api/firmware/fw_search_path.html

02:24 <c0rnelius> So for example if you wanted to add firmware but not have it bothered by what the OS installs you can force the board to look here first on the cmdline -> firmware_class.path=/lib/firmware/updates/brcm

02:27 <c0rnelius> Although with Ubuntu I do believe its created a problem because they decided to go with said patching instead of just using the standard thats been set in place. So if added firmware is put in the `default location` of their choosing it can sometimes screw up bluetooth.

02:32 <c0rnelius> But the default search path should be: `/lib/firmware/updates/` after that it checks `/lib/firmware` bluez on the other hand by default looks for `/etc/firmware` hence the link.

02:37 <lanefu> ah

02:38 <c0rnelius> lanefu: I researched this for a way to long :)

02:39 <Armbian-Discord> <l​anefu> i googled for 5 min lol

02:39 <c0rnelius> Before or after?

02:42 <c0rnelius> It goes deeper though. As some of these boards use the stupid patchram garbage or there own special little script to get it started. Bluetooth on arm is pretty much a shit show from what I can tell.

02:42 <lanefu> when we talked about it an hour ago

02:42 <c0rnelius> Oh I was eating.

02:44 <c0rnelius> Well if anyone is wondering why the Pi4's bluetooth is giving you `AAs` on anything besides Impish and Higher its missing the symlink.

02:44 <c0rnelius> Debian and Devuan don't use these patches. As far as I know.

02:47 <c0rnelius> I actually suggested at one point Devuan could include them, but that went nowhere. Lazy I guess? To much effort? Who knows.

17:57 <c0rnelius> Not sure why they said the Audio wasn't working on the Pi4 build, Analog works fine. I just tested it.

17:58 <IgorPec> probably hdmi?

17:58 <IgorPec> you tested our last nighlty build?

17:58 <c0rnelius> My monitor doesn't have speakers so I couldn't test hdmi but it is in aplay -l and pulseaudio shows two profiles you can select.

17:58 <c0rnelius> Yeah I just downloaded it

17:58 <c0rnelius> Maineline Linux

17:58 <IgorPec> yeah

17:58 <IgorPec> that's the only one for now

17:59 <c0rnelius> you should set ACT led to mmc1 so it stops blinking :)

17:59 <IgorPec> i will not touch rpi ;)

18:00 <c0rnelius> Setup looks like the how Ubuntu doesn't mostly. But whom ever is working on it, its pretty simples to add in.

18:01 <c0rnelius> does it*

18:03 <c0rnelius> Could do it this way -> https://raw.githubusercontent.com/pyavitz/debian-image-builder/feature/files/led-trigger/raspi4

18:03 <c0rnelius> or this way if ur gonna give a foundation kernel option -> https://github.com/pyavitz/rpi-img-builder/blob/master/lib/function/universal#L460

18:04 <IgorPec> its not a technical problem

18:05 <IgorPec> i am tottally overloaded and i don't need another device to tackle

18:05 <c0rnelius> Nah its just annoying :)

18:05 <IgorPec> i can imagine, but it doesn't annoye me ;)

18:07 <c0rnelius> Well, mine sits in the corner doing nothing usually and someone left one here they wanted me to install RetroPie and hook them up with games. But then they never came back to get it? Been here like a year in a box. Thats what I just used to run the test.

18:08 <c0rnelius> I'm sure the HDMI audio works and they just didn't adjust the profile or try creating an asound.conf file to default to hdmi.

18:08 <IgorPec> people expect things as such just works OOB

18:09 <IgorPec> afaik rpardini never booted desktop

18:10 <c0rnelius> Booted fine. I tried the Xfce one.

18:10 <IgorPec> for 1st build / stage, this is perfectly fine. it would be strange to be without bugs

18:10 <c0rnelius> He overclocked the shit out of it :)

18:11 <c0rnelius> And youtube mostly worked, but thats to be expected on Mainline.

18:11 <c0rnelius> Probs work better if he pulled from foundation.

18:12 <c0rnelius> Since Mesa now supports all that junk for the Pis out of the box. So MPV for example would have no probs doing atleast 1080p movies and whatnot.

18:17 <IgorPec> yeah, that's planned for the release part. we need to get someone that will tackle small things

18:18 <IgorPec> we have current x86 and rpi tied to ubuntu kernel

18:18 <IgorPec> not sure if this will still work the same?

18:18 <IgorPec> but switching to fundation's one is not difficult

18:23 <c0rnelius> Be pretty much the same, just pulling from them instead of kernel.org.

18:23 <c0rnelius> Also you don't need all those bcm2835 dtb files.

18:23 <c0rnelius> They are pointless

18:26 <c0rnelius> Also they provide the overlays, so it zero work on ur part. Just copy them in with the packaging patch applied to the builddeb.