> On October 5, 2019 at 1:16 PM Matthias Brugger <matthias.bgg@xxxxxxxxx> wrote:
>
>
> Hi Uli,
>
> On 04/10/2019 21:09, Ulrich Hecht wrote:
> > Hi!
> >
> > This driver seems to have fallen by the wayside because, while otherwise
> > fine, it has a firmware update feature that requires a blob that is not in
> > the linux-firmware repo.[1]
> >
> > Whatever the cause for that may be, the update code is entirely optional
> > (my chip works fine with whatever firmware is currently installed), so I
> > have removed it in order to get this merged after all. I have also
> > followed various trivial API changes that have piled up since 2016; see
> > the individual patches for details.
> >
> > I'm using this driver on an Acer Chromebook R13 ("Elm"); see
> > https://github.com/uli/kernel/tree/elm-working-5.4.
> >
>
> Thanks for your effort to get things upstream.
> I just tried your branch on my R13. I had to do a trivial config change I had to
> do, as I don't have and care about the bluetooth FW right now.
Thank you for testing!
> But after that my screen keeps black. I was able to build and boot
> elm-working-5.3 and elm-working-5.2.
>
> Unfortunatley I don't have a serial console on the Chromebook, so it's difficult
> to find out where it hangs. Can you please double check if your new
> elm-working-5.4 actually really works?
No, it doesn't. :( It seems I forgot to run mkimage/vbutil_kernel when testing...
I have pushed a fix to the elm-working-5.4 tree, and I will send a v20 tomorrow. Sorry for the inconvenience.
CU
Uli
