On Tue, Mar 3, 2015 at 12:46 AM, Simon Glass wrote:
> Hi,
>
> On 2 March 2015 at 01:41, Alexandre Courbot wrote:
>>
>> On Thu, Feb 12, 2015 at 5:51 PM, Tomeu Vizoso
>> wrote:
>> > As there isn't a way for the firmware on the Nyan chromebooks to hand
>> > over the display to the kernel.
>>
>>
On 2 March 2015 at 09:41, Alexandre Courbot wrote:
> On Thu, Feb 12, 2015 at 5:51 PM, Tomeu Vizoso
> wrote:
>> As there isn't a way for the firmware on the Nyan chromebooks to hand
>> over the display to the kernel.
>
> Could this have a side-effect on models for which the firmware *does*
> hand
On Thu, Feb 12, 2015 at 5:51 PM, Tomeu Vizoso
wrote:
> As there isn't a way for the firmware on the Nyan chromebooks to hand
> over the display to the kernel.
Could this have a side-effect on models for which the firmware *does*
hand over the display to the kernel? E.g. temporary glitch or black
Hi,
On 2 March 2015 at 01:41, Alexandre Courbot wrote:
>
> On Thu, Feb 12, 2015 at 5:51 PM, Tomeu Vizoso
> wrote:
> > As there isn't a way for the firmware on the Nyan chromebooks to hand
> > over the display to the kernel.
>
> Could this have a side-effect on models for which the firmware
As there isn't a way for the firmware on the Nyan chromebooks to hand
over the display to the kernel.
Signed-off-by: Tomeu Vizoso
---
drivers/gpu/drm/tegra/sor.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/tegra/sor.c b/drivers/gpu/drm/tegra/sor.c
index
