From: "Antonino A. Daplas" <adaplas@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] fbdev sysfs updates.
Date: Fri, 04 May 2007 03:22:06 +0800 [thread overview]
Message-ID: <1178220126.28617.3.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.64.0705031456330.15445@pentafluge.infradead.org>
On Thu, 2007-05-03 at 15:03 +0100, James Simmons wrote:
> > On Wed, 2007-05-02 at 20:45 +0100, James Simmons wrote:
> > > Andrew can you try this patch. The goal of the patch is to allow the
> > > hardware behind fbdev to be shared with out types of devices i.e
> > > backlight, drm, and display. Please give it a try.
> > >
> >
> > Any real world examples on how this patch can allow sharing with DRM?
> > I'm not sure if your changelog reflects the content of this patch.
>
> DRM would need to be updated to use a child device. The idea is simple.
> Use the device created with device_create instead of the parent device.
> The conflict was storing our private data with the parent device. Now it
> is stored in the child device. Other subsystems already use this approach.
> The drivers would need to be be cleaned up. Right now they use the parent
> device to stored fb_info.
What I basically see in this patch, unless I miss something, is moving
device code from fbmem.c to fbsysfs.c and the creation of fb_power()
hook. I have nothing against the patch in principle, I just think the
changelog is not very clear.
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-05-03 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 19:45 [PATCH] fbdev sysfs updates James Simmons
2007-05-02 21:36 ` Antonino A. Daplas
2007-05-03 14:03 ` James Simmons
2007-05-03 19:22 ` Antonino A. Daplas [this message]
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=1178220126.28617.3.camel@daplas \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).