Den 23.08.2016 20:01, skrev Daniel Vetter:
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote:
+static int sdrm_fbdev_event_notify(struct notifier_block *self,
+ unsigned long action, void *data)
+{
+ struct sdrm_device *sdrm;
+
Den 23.08.2016 20:01, skrev Daniel Vetter:
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote:
+static int sdrm_fbdev_event_notify(struct notifier_block *self,
+ unsigned long action, void *data)
+{
+ struct sdrm_device *sdrm;
+ struct fb_event
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote:
>>> +static int sdrm_fbdev_event_notify(struct notifier_block *self,
>>> + unsigned long action, void *data)
>>> +{
>>> + struct sdrm_device *sdrm;
>>> + struct fb_event *event
On Tue, Aug 23, 2016 at 7:52 PM, Noralf Trønnes wrote:
>>> +static int sdrm_fbdev_event_notify(struct notifier_block *self,
>>> + unsigned long action, void *data)
>>> +{
>>> + struct sdrm_device *sdrm;
>>> + struct fb_event *event = data;
>>> +
Den 23.08.2016 14:41, skrev Daniel Vetter:
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote:
There is currently no non-fbdev mechanism in place to kick out
simpledrm when the real hw-driver is probed. As a stop gap until
that is in place, honour remove_conflicting_framebuffers()
Den 23.08.2016 14:41, skrev Daniel Vetter:
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote:
There is currently no non-fbdev mechanism in place to kick out
simpledrm when the real hw-driver is probed. As a stop gap until
that is in place, honour remove_conflicting_framebuffers()
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote:
> There is currently no non-fbdev mechanism in place to kick out
> simpledrm when the real hw-driver is probed. As a stop gap until
> that is in place, honour remove_conflicting_framebuffers() and
> delete the simple-framebuffer
On Mon, Aug 22, 2016 at 10:25:25PM +0200, Noralf Trønnes wrote:
> There is currently no non-fbdev mechanism in place to kick out
> simpledrm when the real hw-driver is probed. As a stop gap until
> that is in place, honour remove_conflicting_framebuffers() and
> delete the simple-framebuffer
There is currently no non-fbdev mechanism in place to kick out
simpledrm when the real hw-driver is probed. As a stop gap until
that is in place, honour remove_conflicting_framebuffers() and
delete the simple-framebuffer platform device when it's called.
Signed-off-by: Noralf Trønnes
There is currently no non-fbdev mechanism in place to kick out
simpledrm when the real hw-driver is probed. As a stop gap until
that is in place, honour remove_conflicting_framebuffers() and
delete the simple-framebuffer platform device when it's called.
Signed-off-by: Noralf Trønnes
---
10 matches
Mail list logo