Hi!
> James' new API changes absolutely *no* external API features. I can swear
> by this, because I have changed my fbcon driver already to the new internal
> API.
>
> The situation is basically this:
>
> 1. fb_get_var()
>
> old: The old API always passed the "con" argument with the value of the
> currently active console to fb_get_var. This means that
> FBIO_GET_VSCREENINFO returns the *currently displayed* VT size.
>
> new: The new API ignores the "con" argument and simply returns the
> *currently displayed* VT size.
>
> Therefore, there is no change in user API or functionality of this change
> what so ever.
>
> 2. fb_get_fix()
>
> same as above
>
> 3. fb_get_cmap()
>
> same as above
>
> Therefore, in total, James' internal API cleanup has absolutely *no* externally
> visible changes.
>
> For instance, with the new API, I can still have /dev/tty1 at 800x600, 8bpp,
> tty2 at 1024x768, 24bpp, and /dev/tty7 at 1280x1024 16bpp. I can switch
> between them, and the hardware gets updated correctly. To prove it:
>
> [root@sturm rmk]# chvt 1;fbset 640x480-60;chvt 2;fbset 800x600-60
> -depth 16;chvt 1;fbset;chvt 2;fbset
And how do you set tty2 to 800x600-60, when tty1 is foreground and you
_don't_ want to switch consoles?
Pavel
-- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents me at discuss@linmodems.org- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:18 EST