From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@www.infradead.org>
Subject: Re: [PATCH] sysfs support for fbdev
Date: Wed, 2 Mar 2005 13:13:09 -0500 [thread overview]
Message-ID: <9e47339105030210135dbe71ed@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0503012105420.4595@pentafluge.infradead.org>
On Tue, 1 Mar 2005 21:11:20 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
>
> > Not finished yet but here's an update.
>
> Barf!!!! This patch is just nasty hack. Okay a run down on the fbdev api.
> First struct xxx_par is your data structure representing your device.
> There is one per video card. That is that hook in struct fb_info called
> par. The idea was xxx_par could be independent of the fbdev layer and
> could be used DRI. Now for the case of video cards with more than one
> framebuffer then you have bothe struct fb_info's par point to the same
> data structure. The verse works as well. Some systems allow multiple video
> cards hooked up to one montior. Two framebuffers, one display. The
> structure to deal with that is monspecs in struct fb_info. Now the problem
> is it is not a pointer :-( I have to fix that with a patch in the near
> future. If you are going to be messing with montiors work off of struct
> fb_monspecs.
Have you considered moving all of the monitor support out into a
hotplug helper app? This will even work at boot time since early user
space is there when fbdev initializes. The helper app would be on
initrd just like the boot disk drivers.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-02 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 10:00 [PATCH] sysfs support for fbdev Jon Smirl
2005-03-01 21:11 ` James Simmons
2005-03-02 18:13 ` Jon Smirl [this message]
2005-03-03 0:12 ` James Simmons
2005-03-03 0:57 ` Jon Smirl
2005-03-07 18:05 ` James Simmons
2005-03-07 18:10 ` Jon Smirl
2005-03-04 4:08 ` Jon Smirl
2005-03-04 18:26 ` James Simmons
2005-03-04 18:48 ` Jon Smirl
2005-03-04 18:50 ` Sylvain Meyer
2005-03-04 19:48 ` Buttchereit, Axel (XL)
2005-03-04 18:43 ` Sylvain Meyer
2005-03-04 18:50 ` Jon Smirl
2005-03-04 18:54 ` Sylvain Meyer
2005-03-01 23:49 ` Benjamin Herrenschmidt
2005-03-02 1:05 ` James Simmons
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=9e47339105030210135dbe71ed@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jsimmons@www.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).