On 2017/2/25 5:33, John Stultz wrote:
On Thu, Feb 23, 2017 at 5:55 PM, liuxinliang
wrote:
Hi John,
On 2017/2/23 8:56, John Stultz wrote:
In some cases I've been seeing a race where two framebuffers
would be initialized, as kirin_fbdev_output_poll_changed()
might get called quickly in succes
On Thu, Feb 23, 2017 at 5:55 PM, liuxinliang
wrote:
> Hi John,
>
> On 2017/2/23 8:56, John Stultz wrote:
>>
>> In some cases I've been seeing a race where two framebuffers
>> would be initialized, as kirin_fbdev_output_poll_changed()
>> might get called quickly in succession, resulting in the fb
>
Hi John,
On 2017/2/23 8:56, John Stultz wrote:
In some cases I've been seeing a race where two framebuffers
would be initialized, as kirin_fbdev_output_poll_changed()
might get called quickly in succession, resulting in the fb
initialization happening twice. This could cause the system
I might
In some cases I've been seeing a race where two framebuffers
would be initialized, as kirin_fbdev_output_poll_changed()
might get called quickly in succession, resulting in the fb
initialization happening twice. This could cause the system
to boot up with a blank screen.
This patch adds a simple m