00:21 <alex_> fischerm i'm having some random boot issues atm (from cpu panics at mmcqd/2 to waiting for some systemd units not starting but system not proceeding forward), will report as soon as I boot fully

00:22 <fischerm> so my jerry works like a charm with mainline or arch's linux-armv7-chromebook

00:22 <fischerm> the intern's c201 does, too

00:23 <fischerm> alex_: ^^

00:24 <alex_> Last time I tried I would get a white screen

00:24 <fischerm> alex_: 4.9.4?

00:25 <fischerm> alex_: it started working for me with 4.8rc3 or something like that

00:25 <alex_> fischerm, 4.9 something tried around christmas

00:27 <fischerm> hmm

04:36 <naobsd> hmm

13:04 <Graphicscore> Hi all

13:04 <Graphicscore> Quick question, Is there any Android 6.0.1 or greater source available for the rk3288 ?

13:09 <phh> I know rockchip have an android 6.0(.1?) for rk3288, idk if it's public

16:25 <rperier> mmind00: I am working on a ASoC machine driver for rock2 and firefly --> a machine driver rk3288 specific generic that supports cpu dai_link to multicodec (on the rock2 and the firefly the analog headphone and hdmi audio are connected on the same i2s line, so we have no choices). We're wondering if it is more interesting to refactorize rockchip_max98090, to make it more generic and common between veyron and rock2/firefly or do you prefer

16:25 <rperier> another separated driver for that ? (rockchip_rk3288_i2s.c with builtin hdmi and dynamic analog audio handling from the DT)

16:25 <rperier> I have a mixed feeling to be honest, so I prefer to ask the maintainer directly

16:27 <rperier> I'm afraid that if we refactorize rockchip_max98090 , the driver is too complicated to maintain

19:23 <mmind00> rperier: I guess that is more a question for Mark Brown (broonie in #armlinux) as he is the asoc maintainer ... my sound-contacts have been sparse so far