All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [BUG] Strange interaction between X and /dev/fb0 + /dev/fb1
Date: Sun, 31 Jul 2005 13:53:42 +0800	[thread overview]
Message-ID: <42EC6766.2020807@gmail.com> (raw)
In-Reply-To: <42EC5F11.2070606@t-online.de>

Knut Petersen wrote:
> Hi everybody,
> 
>  1: the system boots with video=vesafb:ypan
>  2: cyblafb is loaded by the boot.local script
>  3: con2vt /dev/fb1 /dev/tty1
>  4: runlevel 3 (no X) is used
> 
> As cyblafb detects the video mode used by vesafb, everything works
> fine. If I switch to tty1, the accelerated cyblafb driver is used, all 
> other
> ttys use the slow  vesafb code.
> I can unload cyblafb after a con2ct /dev/fb0 /dev/tty1, load it again, 
> switch
> between ttys, everything without a problem.
> 
> Now I switch to runlevel 5.
> 
>  1: Switching from X to any tty, no matter if it is managed
>     by vesafb or cyblafb,does work without problems.

X restores, at least partially, the state of the card, then set_par
is called which fully restores the state of cyblafb.

>  2: Switching from any tty to X works without a problem.

X usually does a good job of restoring it's own state.

>  3: Switching from X to any tty except tty1 (managed by cyblafb)
>     and then between any ttys works without problems.

Vesa state is usually restored fully by X, so even if vesafb has
no set_par, vesafb comes back working.

> 
>  4: Switching from X to tty1 and then to any other tty does _not_
>     work. The cursor stops blinking, otherwise nothing changes
>     on the monitor. Blindly entered commands produce no visible
>     output, but they are executed.

I don't know why.  But try switching from tty1->X->tty1->!tty1 and
!tty1->X->tty1->!tty1. Do you still get the same behavior?
 
Tony


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

      reply	other threads:[~2005-07-31  5:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  5:18 [BUG] Strange interaction between X and /dev/fb0 + /dev/fb1 Knut Petersen
2005-07-31  5:53 ` Antonino A. Daplas [this message]

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=42EC6766.2020807@gmail.com \
    --to=adaplas@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.