From: "Jatin Kumar" <jatin.kumar@gatech.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: asynchronous resolution change
Date: Mon, 24 Nov 2008 20:52:52 -0500 [thread overview]
Message-ID: <333fec630811241752i616754f5wcde88e812a439b01@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811190933200.27671@anakin>
[-- Attachment #1.1: Type: text/plain, Size: 1915 bytes --]
On Wed, Nov 19, 2008 at 3:35 AM, Geert Uytterhoeven <geert@linux-m68k.org>wrote:
> On Tue, 18 Nov 2008, Jatin Kumar wrote:
> > I am new to linux fb model and had some queries regarding resolution
> change
> > mechanisms.
> >
> > Consider a situation where the frambuffer kernel module (vfb/xenfb etc)
> > wants to change the resolution.
> >
> > 1. Is there a mechanism to this, considering the applications/windowing
> > system/console above the framebuffer hasnt initiated the size change?
> >
> > 2. Is there a way to do an upcall into the application/windowing
> > system/console modules to inform them about the size change
> asynchronously?
> >
> > In this particular case ; the display hardware(instead of the user) has
> > initiated the resolution change.Is it possible in the current fb
> framework
> > to support it?
>
> Yes there is! If the resolution is changed, and the number of columns and
> lines of the console changes, the tty subsystem will send the SIGWINCH
> signal
> to the application, cfr. tty_do_resize() in drivers/char/tty_io.c.
>
> Note that not all applications handle it. E.g. X doesn't, AFAIK.
>
> Gr{oetje,eeting}s,
>
> Geert
Hi Geert,
Thanks much for the info.
Is the tty_io_resize( ) relatively new? .
I am looking at 2.6.18.8 src code (used for xen) and could not find the
function.
Also are there any plans for exposing a similar callback api in the linux fb
model to make the applications stay updated about the underlying
resolution/hardware mode changes?
Thanks so much,
Jatin
>
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker.
> But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus
> Torvalds
>
[-- Attachment #1.2: Type: text/html, Size: 2913 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
next prev parent reply other threads:[~2008-11-25 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 1:04 asynchronous resolution change Jatin Kumar
2008-11-19 8:35 ` Geert Uytterhoeven
2008-11-25 1:52 ` Jatin Kumar [this message]
2008-11-25 8:36 ` Geert Uytterhoeven
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=333fec630811241752i616754f5wcde88e812a439b01@mail.gmail.com \
--to=jatin.kumar@gatech.edu \
--cc=geert@linux-m68k.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).