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: 11 Mar 2003 20:59:46 +0800 [thread overview]
Message-ID: <1047387515.984.44.camel@localhost.localdomain> (raw)
In-Reply-To: <1047376355.5640.5.camel@cambridge.braddahead>
On Tue, 2003-03-11 at 17:52, Alex Bennee wrote:
> I sent this to lkml but it probably got missed in the volume of mail.
> Can anyone point me anything that describes how I could test my console
> driver. Would it be the same approach for example as testing the vfb
> frame buffer driver?
>
> -----Forwarded Message-----
> > Hi,
> >
> > I'm writting a console driver for an embedded system for which the
> > hardware isn't quite ready yet. As a result I'm building on a PC with a
> > quickly hacked up proc interface so I can test the logic before the
> > final hardware.
> >
> > On loading the module my code does the following:
> >
> > take_over_console(&sh_con, MAX_NR_CONSOLES - 1, MAX_NR_CONSOLES - 1,
> > 1);
> >
> > Which I understand should associate my new console driver with the last
> > system console (63 in this case). Then to test the console output I do:
> >
> > echo "this is a test string" > /dev/vc/63
> >
I think the above will not work. You can only have 1 active console at
a time, so all inputs to an inactive console will be buffered. Only
when you switch to that particular console that all pending commands
will be flushed.
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.
Tony
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-11 13:02 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 [this message]
2003-03-11 14:28 ` Alex Bennee
2003-03-11 20:07 ` Antonino Daplas
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=1047387515.984.44.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).