From: "Michel Dänzer" <michel@daenzer.net>
To: Peter Hurley <peter@hurleysoftware.com>,
Archit Taneja <architt@codeaurora.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Ben Skeggs <bskeggs@redhat.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: BUG caused by "Use new drm_fb_helper functions" series
Date: Wed, 3 Feb 2016 18:30:54 +0900 [thread overview]
Message-ID: <56B1C8CE.1090607@daenzer.net> (raw)
In-Reply-To: <56B0F7B3.3020704@hurleysoftware.com>
On 03.02.2016 03:38, Peter Hurley wrote:
> On 02/01/2016 09:20 PM, Archit Taneja wrote:
>> Hi Peter,
>>
>> On 02/02/2016 02:07 AM, Peter Hurley wrote:
>>> Hi Archit,
>>>
>>> Just booting 4.4-rc5+, I got this splat [1]
>>> At first glance, this appears to be a simple fix.
>>
>> Thanks for sharing this.
>>
>>>
>>> However, I'm concerned that fbcon functions, which may be called with
>>> interrupts disabled, are now hooked up to fbdev functions which may assume
>>> interrupts are not disabled (as is the case with cfb_imageblit()).
>>
>> In the case when CONFIG_FB is enabled, drm_fb_helper_cfb_imageblit
>> helper simply wraps around cfg_imageblit, so I don't see how we'd have
>> any difference in behaviour.
>
>
> Sorry; terrible attribution on my part.
> This bug clearly has nothing to do with this series.
>
> But a better look has me wondering how all these gpus are syncing
> the framebuffer for direct access via cfb_imageblit and friends. I only see
> nouveau and intel gma even trying.
Probably no other DRM driver uses hardware acceleration for fbcon.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2016-02-03 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:37 Peter Hurley
2016-02-02 5:20 ` Archit Taneja
2016-02-02 18:38 ` Peter Hurley
2016-02-03 9:30 ` Michel Dänzer [this message]
2016-02-09 9:32 ` Daniel Vetter
2016-02-09 13:44 ` One Thousand Gnomes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B1C8CE.1090607@daenzer.net \
--to=michel@daenzer.net \
--cc=architt@codeaurora.org \
--cc=bskeggs@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome