From: Alexander Holler <holler@ahsoftware.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Borislav Petkov <bp@alien8.de>, Shawn Guo <shawn.guo@linaro.org>,
Sasha Levin <levinsasha928@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Josh Boyer <jwboyer@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <florianSchandinat@gmx.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fbdev@vger.kernel.org,
Bernie Thompson <bernie@plugable.com>,
Steve Glendinning <steve.glendinning@shawell.net>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] fb: Rework locking to fix lock ordering on takeover
Date: Fri, 04 Jan 2013 14:36:09 +0100 [thread overview]
Message-ID: <50E6DAC9.802@ahsoftware.de> (raw)
In-Reply-To: <20130104132557.70e0c527@pyramind.ukuu.org.uk>
Am 04.01.2013 14:25, schrieb Alan Cox:
> On Fri, 04 Jan 2013 13:50:37 +0100
> Alexander Holler <holler@ahsoftware.de> wrote:
>
>> Am 28.12.2012 13:40, schrieb Borislav Petkov:
>>> On Fri, Dec 28, 2012 at 07:50:27PM +0800, Shawn Guo wrote:
>>>> +1
>>>>
>>>> http://thread.gmane.org/gmane.linux.kernel/1413953/focus=1415070
>>>
>>> Cool, works fine here too. Is Linus on CC? (/me checks.. ) Yes he is,
>>> good.
>>>
>>> Linus, Alan's patch works at least in 2 cases, you might consider
>>> picking it up directly since the fb maintainer is absent, reportedly.
>>
>>
>> Btw. I think all the usb-fb's (udlfb, smscufx and udl) are broken, at
>> least on ARM(v5). When I have linked in udlfb the following happens on
>> boot (with an attached USB-LCD and with or without the "Rework locking
>> patch):
>
> They are broken if used as the system console (has been known for years).
Ah. Thats why I didn't see it before. Usually I've used the serial as
system console. So thats why it worked before. ;)
> Perhaps your x86 test has the system console still on another device ?
Exactly thats the case. Thanks for pointing it out.
> For the udl layer it shouldn't matter as Dave Airlie wrote a DRM driver
> for udl which obsoletes the old fb layer one and works much better
> (although the error handling is still totally broken and leaks like a
> sieve if it fails)
>
> Fixing the console isn't that difficult - you just need to make your
> device queue the console I/O to a worker thread of some kind. We don't
That is what I wanted to try next. ;)
> want to do that by default because we want to get the messages out
> reliably and immediately on saner hardware. Given there are several
> such cases a general helper and a console "I am crap" flag might be better
> than hacking each driver.
All those drivers look very similiar. I will see if I'm successfull in
writing such an IamCrapHelper. Might need some time, but I will post a
patch for review, if I've done and tested it. I'm only using the USB-LCD
on occasion, so it doesn't have high priority for me because I don't
really need it.
Thanks for the hints.
Regards,
Alexander
next prev parent reply other threads:[~2013-01-04 13:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 19:27 [PATCH] fb: Rework locking to fix lock ordering on takeover Alan Cox
2012-11-21 12:45 ` Josh Boyer
2012-11-21 12:53 ` Alan Cox
2012-12-18 15:20 ` Josh Boyer
2012-12-25 16:08 ` Sasha Levin
2012-12-26 2:41 ` Cong Wang
2012-12-26 18:09 ` Sasha Levin
2012-12-27 4:53 ` Borislav Petkov
2012-12-28 11:50 ` Shawn Guo
2012-12-28 12:40 ` Borislav Petkov
2013-01-04 12:50 ` Alexander Holler
2013-01-04 13:25 ` Alan Cox
2013-01-04 13:36 ` Alexander Holler [this message]
2013-01-05 11:41 ` Alexander Holler
2013-01-05 11:42 ` [PATCH] fb: udlfb: fix scheduling while atomic Alexander Holler
2013-01-06 12:46 ` Alexander Holler
2013-01-09 13:47 ` [PATCH v2] " Alexander Holler
2013-01-05 12:07 ` [PATCH] fb: Rework locking to fix lock ordering on takeover Alan Cox
2013-01-05 12:06 ` Alexander Holler
2013-01-07 9:37 ` Jiri Kosina
2013-01-12 18:36 ` Borislav Petkov
2013-01-12 20:51 ` Linus Torvalds
2013-01-12 21:05 ` Alan Cox
2013-01-12 21:13 ` Andrew Morton
2013-01-13 0:02 ` Borislav Petkov
2013-01-15 12:06 ` Maarten Lankhorst
2013-01-15 15:12 ` Alan Cox
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=50E6DAC9.802@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=airlied@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernie@plugable.com \
--cc=bp@alien8.de \
--cc=florianSchandinat@gmx.de \
--cc=jwboyer@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=steve.glendinning@shawell.net \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.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