linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Gatliff <bgat@billgatliff.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Framebuffer "hangs" at startup
Date: Tue, 17 Oct 2006 21:43:49 -0500	[thread overview]
Message-ID: <453594E5.4060606@billgatliff.com> (raw)

Guys:


Bear with me, this one is a bit tricky to describe...  :)

I'm testing a 2.6.12 kernel and a 2.6.18.1 kernel, and a few in between, 
and they all do it.  All on ARM targets: PXA255 with onboard LCD 
framebuffer, and AT91RM9200 with an S1D13xxx framebuffer.  Duplicated 
with Qt 4.x and SDL 1.2-debian.

The first time I start up a framebuffer-based application, say Qt or 
Antigrain/SDL, things appear to go fine.  But if I abort said program 
with a CTRL-C and restart it, then the application appears to start up 
fine but there's no screen output.  I don't see any output until I do a 
CTRL-Z and then restore the program to the foreground with "fg".  Then 
the screen clears and things start drawing as usual.  The screen also 
draws if I do a CTRL-C instead of -Z, but then the program aborts as you 
would expect.

If I'm running the program under strace then the screen never recovers 
whether I do a CTRL-Z or not.  I see the code hanging in an 
ioctl(KGDKBENT) on /dev/tty8.

Honestly, I'm totally stumped.  Anyone have any suggestions?


b.g.

-- 
Bill Gatliff
bgat@billgatliff.com


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

                 reply	other threads:[~2006-10-18  2:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=453594E5.4060606@billgatliff.com \
    --to=bgat@billgatliff.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 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).