From: Alex Bennee <kernel-hacker@bennee.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: How can I test my console driver?
Date: 07 Mar 2003 14:36:14 +0000 [thread overview]
Message-ID: <1047047773.31348.10.camel@cambridge.braddahead> (raw)
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
However my dmesg output shows no sign of any of the console functions
being called to write data, although the module itself has loaded
succesfully and run the take_over_console code.
Obviously I'm mis-understanding how the console should be accessed but
I'm stuck looking for any pointers. I've been looking thorugh the
newport_con.c driver for pointers but so far I've not seen any extra
magic that I'm missing. Can anyone point me in the right direction/offer
some tips?
--
Alex, homepage: http://www.bennee.com/~alex/
I want to marry a girl just like the girl that married dear old dad.
-- Freud
next reply other threads:[~2003-03-07 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 14:36 Alex Bennee [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=1047047773.31348.10.camel@cambridge.braddahead \
--to=kernel-hacker@bennee.com \
--cc=linux-kernel@vger.kernel.org \
/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.