On Wed, 3 Jul 2019 at 19:41, Rob Clark wrote:
>
> On Wed, Jul 3, 2019 at 9:33 AM Leif Lindholm wrote:
> >
> > On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > > > There is one kernel, and there
> > > > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > > >
On Wed, Jul 3, 2019 at 9:33 AM Leif Lindholm wrote:
>
> On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > > There is one kernel, and there
> > > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > > problem because their distro missed some shim patch really j
On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > There is one kernel, and there
> > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > problem because their distro missed some shim patch really just
> > > doesn't seem like a headache I want to have.
> >
> >
On Sun, 30 Jun 2019 at 22:36, Rob Clark wrote:
>
> From: Rob Clark
>
> On snapdragon aarch64 laptops, a 'UEFIDisplayInfo' variable is provided
> to communicate some information about the display. Crutially it has the
> panel-id, so the appropriate panel driver can be selected. Read this
> out a
On Tue, Jul 02, 2019 at 02:01:49PM -0700, Rob Clark wrote:
> > > So we are dealing with a platform that violates the UEFI spec, since
> > > it does not bother to implement variable services at runtime (because
> > > MS let the vendor get away with this).
> >
> > To clarify, the above remark applies
On Tue, 2 Jul 2019 at 23:02, Rob Clark wrote:
>
> On Tue, Jul 2, 2019 at 1:35 PM Ard Biesheuvel
> wrote:
> >
> > On Tue, 2 Jul 2019 at 22:26, Ard Biesheuvel
> > wrote:
> > >
> > > On Sun, 30 Jun 2019 at 22:36, Rob Clark wrote:
> > > >
> > > > From: Rob Clark
> > > >
> > > > On snapdragon aar
On Tue, 2 Jul 2019 at 22:26, Ard Biesheuvel wrote:
>
> On Sun, 30 Jun 2019 at 22:36, Rob Clark wrote:
> >
> > From: Rob Clark
> >
> > On snapdragon aarch64 laptops, a 'UEFIDisplayInfo' variable is provided
> > to communicate some information about the display. Crutially it has the
> > panel-id,
On Tue, Jul 2, 2019 at 2:59 PM Leif Lindholm wrote:
>
> On Tue, Jul 02, 2019 at 02:01:49PM -0700, Rob Clark wrote:
> > > > So we are dealing with a platform that violates the UEFI spec, since
> > > > it does not bother to implement variable services at runtime (because
> > > > MS let the vendor ge
On Tue, Jul 2, 2019 at 2:53 PM Ard Biesheuvel wrote:
>
> On Tue, 2 Jul 2019 at 23:02, Rob Clark wrote:
> >
> > On Tue, Jul 2, 2019 at 1:35 PM Ard Biesheuvel
> > wrote:
> > >
> > > On Tue, 2 Jul 2019 at 22:26, Ard Biesheuvel
> > > wrote:
> > > >
> > > > On Sun, 30 Jun 2019 at 22:36, Rob Clark
On Tue, Jul 2, 2019 at 1:35 PM Ard Biesheuvel wrote:
>
> On Tue, 2 Jul 2019 at 22:26, Ard Biesheuvel wrote:
> >
> > On Sun, 30 Jun 2019 at 22:36, Rob Clark wrote:
> > >
> > > From: Rob Clark
> > >
> > > On snapdragon aarch64 laptops, a 'UEFIDisplayInfo' variable is provided
> > > to communicate
From: Rob Clark
On snapdragon aarch64 laptops, a 'UEFIDisplayInfo' variable is provided
to communicate some information about the display. Crutially it has the
panel-id, so the appropriate panel driver can be selected. Read this
out and stash in /chosen/panel-id so that display driver can use i
11 matches
Mail list logo
