From: Olaf Hering <olaf@aepfle.de>
To: Michael Hanselmann <linux-kernel@hansmi.ch>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@pol.net>,
Daniel R Thompson <daniel.thompson@st.com>,
Jon Smirl <jonsmirl@gmail.com>,
akpm@osdl.org
Subject: Re: backlight: oops in __mutex_lock_slowpath during head /sys/class/graphics/fb0/* in 2.6.18
Date: Fri, 22 Sep 2006 13:26:22 +0200 [thread overview]
Message-ID: <20060922112622.GA26724@aepfle.de> (raw)
In-Reply-To: <20060921215620.GA9518@hansmi.ch>
On Thu, Sep 21, Michael Hanselmann wrote:
> What about the patch below? Does it work for you?
Appears to work.
tangerine:~ # head /sys/class/graphics/fb0/*
==> /sys/class/graphics/fb0/bits_per_pixel <==
8
==> /sys/class/graphics/fb0/bl_curve <==
head: error reading `/sys/class/graphics/fb0/bl_curve': No such device
==> /sys/class/graphics/fb0/blank <==
==> /sys/class/graphics/fb0/console <==
==> /sys/class/graphics/fb0/cursor <==
==> /sys/class/graphics/fb0/dev <==
29:0
==> /sys/class/graphics/fb0/mode <==
==> /sys/class/graphics/fb0/modes <==
U:832x624p-74
==> /sys/class/graphics/fb0/name <==
valkyrie
==> /sys/class/graphics/fb0/pan <==
0,0
==> /sys/class/graphics/fb0/rotate <==
0
==> /sys/class/graphics/fb0/state <==
0
==> /sys/class/graphics/fb0/stride <==
832
==> /sys/class/graphics/fb0/subsystem <==
head: error reading `/sys/class/graphics/fb0/subsystem': Is a directory
head: cannot open `/sys/class/graphics/fb0/uevent' for reading: Permission denied
==> /sys/class/graphics/fb0/virtual_size <==
832,624
next prev parent reply other threads:[~2006-09-22 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060921121952.GA16927@aepfle.de>
2006-09-21 19:37 ` backlight: oops in __mutex_lock_slowpath during head /sys/class/graphics/fb0/* in 2.6.18 Andrew Morton
2006-09-21 21:56 ` Michael Hanselmann
2006-09-22 11:26 ` Olaf Hering [this message]
2006-09-22 23:02 ` Andrew Morton
2006-09-22 23:07 ` Michael Hanselmann
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=20060922112622.GA26724@aepfle.de \
--to=olaf@aepfle.de \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=daniel.thompson@st.com \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).