Re: [PATCH] staging: sm750fb: avoid conflicting vesafb

2017-08-04 Thread Greg Kroah-Hartman
On Sat, Jul 29, 2017 at 10:17:43PM +0100, Sudip Mukherjee wrote: > From: Teddy Wang > > commit 740c433ec35187b45abe08bb6c45a321a791be8e upstream > > If vesafb is enabled in the config then /dev/fb0 is created by vesa > and this sm750 driver gets fb1, fb2. But we need to be fb0 and fb1 to > effec

Re: [PATCH] staging: sm750fb: avoid conflicting vesafb

2017-07-30 Thread Greg Kroah-Hartman
On Sat, Jul 29, 2017 at 10:17:43PM +0100, Sudip Mukherjee wrote: > From: Teddy Wang > > commit 740c433ec35187b45abe08bb6c45a321a791be8e upstream > > If vesafb is enabled in the config then /dev/fb0 is created by vesa > and this sm750 driver gets fb1, fb2. But we need to be fb0 and fb1 to > effec

[PATCH] staging: sm750fb: avoid conflicting vesafb

2017-07-29 Thread Sudip Mukherjee
From: Teddy Wang commit 740c433ec35187b45abe08bb6c45a321a791be8e upstream If vesafb is enabled in the config then /dev/fb0 is created by vesa and this sm750 driver gets fb1, fb2. But we need to be fb0 and fb1 to effectively work with xorg. So if it has been alloted fb1, then try to remove the ot