[PATCH] fbcon: use default if cursor blink interval is not valid

2016-05-19 Thread Ming Lei
On Thu, May 19, 2016 at 10:22 PM, Scot Doyle wrote: > On Thu, 19 May 2016, Pavel Machek wrote: >> Hi! >> >> > Two current [1] and three previous [2] systems locked during boot >> > because the cursor flash timer was set using an ops->cur_blink_jiffies >> > value of 0. Previous patches attempted to

[PATCH] fbcon: use default if cursor blink interval is not valid

2016-05-19 Thread Jeremy Kerr
Hi Scot, > Use the normal cursor blink default interval of 200 ms if > ops->cur_blink_jiffies is not in the range specified in commit > bd63364caa8d. Since invalid values are not used, specific system > initialization timings should not cause lockups. This fixes an issue we're seeing with the ast

[PATCH] fbcon: use default if cursor blink interval is not valid

2016-05-19 Thread Pavel Machek
Hi! > Two current [1] and three previous [2] systems locked during boot > because the cursor flash timer was set using an ops->cur_blink_jiffies > value of 0. Previous patches attempted to solve the problem by moving > variable initialization earlier in the setup sequence [2]. > > Use the normal

[PATCH] fbcon: use default if cursor blink interval is not valid

2016-05-19 Thread Scot Doyle
On Thu, 19 May 2016, Pavel Machek wrote: > Hi! > > > Two current [1] and three previous [2] systems locked during boot > > because the cursor flash timer was set using an ops->cur_blink_jiffies > > value of 0. Previous patches attempted to solve the problem by moving > > variable initialization ea

[PATCH] fbcon: use default if cursor blink interval is not valid

2016-05-19 Thread David Daney
On 05/18/2016 09:21 PM, Scot Doyle wrote: > Two current [1] and three previous [2] systems locked during boot > because the cursor flash timer was set using an ops->cur_blink_jiffies > value of 0. Previous patches attempted to solve the problem by moving > variable initialization earlier in the set