From: James Simmons <jsimmons@infradead.org>
To: Otto Solares <solca@guug.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: FBDEV updates.
Date: Thu, 14 Aug 2003 21:52:50 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308142150390.15200-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20030814203658.GE7862@guug.org>
> what is the current state of PM in fb drivers?
Experinmental patch from Ben is in the works.
> does modedb is being used on 2.6 drivers?
Yes.
> Is there an API (or lib) to use framebuffers devices without
> worring about differents visuals?,
???
> to quering, setting or
> disabling EDID support?
Yes. That is the fbmon.c stuff. Still needs work.
> will these drivers export sysfs
> entries instead of control via ioctl's?
Needs to be done. I'm not familiar with sysfs so it hasn't been done.
> thanks for your work on fb.
Your welcome.
next prev parent reply other threads:[~2003-08-14 20:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 19:54 FBDEV updates James Simmons
2003-08-14 20:36 ` Otto Solares
2003-08-14 20:52 ` James Simmons [this message]
2003-08-15 8:40 ` Benjamin Herrenschmidt
2003-08-15 22:31 ` James Simmons
2003-08-15 23:42 ` Benjamin Herrenschmidt
2003-08-16 2:40 ` Otto Solares
2003-08-14 23:16 ` Greg KH
2003-08-15 22:37 ` James Simmons
2003-08-15 23:54 ` Greg KH
2003-08-16 6:01 ` Sven Schnelle
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 1:40 FBdev updates Lawrence Lee (Shanghai)
2003-02-20 1:09 James Simmons
2003-02-20 1:17 ` Jeff Garzik
2003-02-20 1:22 ` James Simmons
2003-02-20 15:02 ` Dave Jones
2003-02-20 15:07 ` James Simmons
2003-02-20 18:29 ` Petr Vandrovec
2003-02-20 19:03 ` Jurriaan
2003-02-20 19:58 ` James Simmons
2003-02-21 1:45 ` David S. Miller
2003-02-20 15:10 ` Ivan Kokshaysky
2002-06-18 20:16 fbdev updates James Simmons
2002-06-18 20:22 ` Larry McVoy
2002-06-05 16:39 James Simmons
2002-06-05 16:50 ` Russell King
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=Pine.LNX.4.44.0308142150390.15200-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.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).