From: "Ville Syrjälä" <syrjala@sci.fi>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
DRI development list <dri-devel@lists.sourceforge.net>,
Paulius Zaleckas <paulius.zaleckas@gmail.com>,
Michal Suchanek <hramrach@centrum.cz>
Subject: Re: [Linux-fbdev-devel] drm_fb_helper: Impossible to change video
Date: Thu, 11 Mar 2010 05:03:08 +0000 [thread overview]
Message-ID: <20100311050308.GC4536@sci.fi> (raw)
In-Reply-To: <alpine.LFD.2.00.1003110212290.13366@casper.infradead.org>
On Thu, Mar 11, 2010 at 02:22:14AM +0000, James Simmons wrote:
>
> > > > There are other drivers that support multihead already (matroxfb, any
> > > > other?) and have their own driver-specific inteface.
> > >
> > > Each crtc is treated as a seperate fbdev device. I don't recall any
> > > special ioctls. Maybe for mirroring which was never standardized.
> >
> > matroxfb does have a bunch of custom ioctls to change the crtc<->output
> > mapping.
>
> Yes the mapping issue were never address.
>
> > I don't think the CRTCû_info makes much sense if the main use
> > case is fbcon.
>
> Actually that is what I had in mind when I reworked the fbdev api. Plus
> with the linux console project I got multiple VTs working at the same
> time.
>
> > fbcon will use a single fb device and so you can't see
> > the console on multiple heads anyway which makes the whole thing
> > somewhat pointless. And if you're trying to do something more complex
> > you will be a lot better off bypassing fbdev altogether.
>
> Not true. You can map different displays to different vcs. Give con2fb a
> try some time :-)
I know about it but only one VT can be active at any given time.
> Now there is the issue of more than one keyboard being
> mapped at a time. BTW I did getting multipe VT working at the same
> time working in the past. It requires some cleanup on the console layer.
Well if you think that cleanup is possible and worth the effort then it
might make sense. The crtc<->output mapping is still unresolved though
and it depends on hardware which combinations are supported. If for
example the hardware can't drive multiple outputs with the same CRTC
or if the outputs require totally different timings then you can't
clone the same VT to multiple outputs.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2010-03-11 5:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 13:16 [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Paulius Zaleckas
2009-11-20 15:55 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video Clemens Ladisch
2009-11-20 18:53 ` James Simmons
2009-11-20 19:05 ` Andrew Morton
2009-11-20 19:39 ` Paulius Zaleckas
2009-11-20 20:01 ` James Simmons
2009-11-20 20:13 ` Paulius Zaleckas
2009-11-20 20:48 ` James Simmons
2009-11-21 4:25 ` Dave Airlie
2009-11-21 4:27 ` Dave Airlie
2010-03-01 9:18 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-03 5:02 ` Dave Airlie
2010-03-03 8:23 ` Michal Suchanek
2010-03-03 9:23 ` Dave Airlie
2010-03-03 10:32 ` Michal Suchanek
2010-03-10 18:11 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 21:04 ` Ville Syrjälä
2010-03-10 21:16 ` Michal Suchanek
2010-03-11 2:24 ` James Simmons
2010-03-11 2:22 ` James Simmons
2010-03-11 5:03 ` Ville Syrjälä [this message]
2010-03-10 18:04 ` James Simmons
2010-03-10 17:42 ` James Simmons
2010-03-10 18:05 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Alex Deucher
2010-03-10 18:10 ` Alex Deucher
2010-03-10 18:47 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 19:49 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-10 20:06 ` Alex Deucher
2010-03-11 10:13 ` Michel Dänzer
2010-03-11 10:31 ` Pauli Nieminen
2010-03-11 15:12 ` Alex Deucher
2010-03-11 15:17 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-11 15:47 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-12 14:52 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-12 20:51 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Dave Airlie
2010-03-13 14:40 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-13 21:01 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Dave Airlie
2010-03-14 11:41 ` Michel Dänzer
2010-03-15 18:38 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-16 13:46 ` Michel Dänzer
2010-03-16 13:56 ` James Simmons
2010-03-16 14:00 ` Michel Dänzer
2010-03-25 12:30 ` James Simmons
2010-03-15 18:22 ` James Simmons
2010-03-10 20:58 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video mode Michal Suchanek
2010-03-11 3:41 ` [Linux-fbdev-devel] drm_fb_helper: Impossible to change video James Simmons
2010-03-10 17:35 ` 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=20100311050308.GC4536@sci.fi \
--to=syrjala@sci.fi \
--cc=dri-devel@lists.sourceforge.net \
--cc=hramrach@centrum.cz \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=paulius.zaleckas@gmail.com \
/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).