From: Antonino Daplas <adaplas@pol.net>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: How can I test my console driver?
Date: 12 Mar 2003 04:07:48 +0800 [thread overview]
Message-ID: <1047407682.1033.178.camel@localhost.localdomain> (raw)
In-Reply-To: <1047392898.2262.4.camel@cambridge.braddahead>
On Tue, 2003-03-11 at 22:28, Alex Bennee wrote:
> > Why not just use take_over_console() with first and last equal to a tty
> > you can switch to? If something bad happens, just switch to a working
> > console.
>
> I tried that. It seems the first time I do a Ctrl-Alt-5 (for example) I
> loose the ability to use my keyboard. The only way I can recover
> anything is to re-boot my machine. This strikes me as a little odd as I
> thought the console was soley interested in output.
>
> Is there anyway to write unbuffered output to the console? After all the
> only way I'm going to know anything is working is through dmesg and/or
> the screen image I read from my debugging proc interface.
>
Maybe you can create dummy methods first, con_startup, con_init (used
during take_over_console), as well as the putc/s, scroll, clear, bmove,
etc. Then you can implement them one by one and see which method
actually triggerred the lockup.
Tony
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
prev parent reply other threads:[~2003-03-11 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 9:52 How can I test my console driver? Alex Bennee
2003-03-11 12:59 ` Antonino Daplas
2003-03-11 14:28 ` Alex Bennee
2003-03-11 20:07 ` Antonino 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=1047407682.1033.178.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=kernel-hacker@bennee.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).