From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Nigel Cunningham <ncunningham@linuxmail.org>
Subject: Re: Devices don't get linked to their class.
Date: Sat, 4 Sep 2004 20:41:55 +0800 [thread overview]
Message-ID: <200409042041.55199.adaplas@hotpop.com> (raw)
In-Reply-To: <1094187751.2979.41.camel@laptop.cunninghams>
On Friday 03 September 2004 13:02, Nigel Cunningham wrote:
> This morning I began work on addressing the problem. I thought the best
> approach would be to use device classes to find the struct dev for the
> frame buffer driver, and then use the same code I use for storage
> devices to avoid suspending the frame buffer until later. I successfully
> wrote a helper to find the 'graphics' class that fbmem.c creates, but
> now I've run into a more serious issue. register_framebuffer (in the
> same time) calls class_simple_device_add with a NULL for the pointer to
> the struct device. Is it possible for this issue to be addressed? I can
I guess it's doable, but will require small changes to all framebuffer
drivers. All you need is struct device, right? Maybe I can brew up a test
patch next week.
> see that (at least in the Radeon case) one could simply call
> register_framebuffer with an additional parameter, but thought I'd email
> you and seek your wisdom.
>
> By the way, am I missing something? It looks like framebuffer_alloc does
> nothing with the dev parameter passed to it.
For now, yes. Maybe in the future, when full-pledged sysfs support is
added...
Tony
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-04 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 5:02 Devices don't get linked to their class Nigel Cunningham
2004-09-04 12:41 ` Antonino A. Daplas [this message]
2004-09-05 6:21 ` Nigel Cunningham
2004-09-05 10:40 ` Antonino A. Daplas
2004-09-05 21:45 ` Nigel Cunningham
2004-09-06 3:38 ` [PATCH] " Nigel Cunningham
[not found] ` <32016.10.250.10.1.1094456212.squirrel@sq04.pol.net>
2004-09-06 21:56 ` Nigel Cunningham
2004-09-07 19:50 ` Kronos
2004-09-08 0:55 ` Antonino A. Daplas
2004-09-08 3:21 ` Nigel Cunningham
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=200409042041.55199.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ncunningham@linuxmail.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).