From: "Scott Nash" <ksnash@directvinternet.com>
To: <linux-kernel@vger.kernel.org>
Subject: char device kernel module won't write
Date: Wed, 18 Dec 2002 23:08:58 -0600 [thread overview]
Message-ID: <001501c2a71c$bd043e50$9900a8c0@Scottlaptop> (raw)
I am trying to finish a driver to write to a small lcd screen. I can write
to the screen all day but I need to get the write function to work. This is
under kernel 2.2.16-22. I started with the tagged fops set up. Then to see
if it made a difference I fully declared the fops structure making sure all
the positions were acounted for with NULL or fuction call. I basically have
nothing but open, release, read, write and llseek defined. I selected a
major of 200 after not seeing it defined. The device loads fine. I made a
test program for it, which opens the device, writes one line and then
closes. When I try to write,in the test, the debug statements for read
function come up and I get an oops.
Everything says that the write I wrote and placed in fops structure should
be called. What I am trying to write to device is: struct lcdpacket{int
line;char text[18]};
I have tried to change places of read and write but those incompatible
pointers keep coming up.
I am debating on going on list, but please cc me right now.
reply other threads:[~2002-12-19 5:05 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='001501c2a71c$bd043e50$9900a8c0@Scottlaptop' \
--to=ksnash@directvinternet.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.