I read Alessandro's LINUX DEVICE DRIVERS, did not understand everything
and started coding.
The bitbus (anybody know it?) is a packet-oriented thing very much like
RS 485. Plus it has a protocol on top like IP. For better usability the
vendor of the micro-OS we use added another protocol on top of that like
TCP.
Now, if I wanted to do it RIGHT (in the sence of perfect) I would need
to implement the two protocol layers for the Linux-Kernel and a
net-device-driver for the board, right?
I know that this would be to big a step. Since I want to get somewhere
soon I thought that I first do it as a simple char-device.
But since I have packages anyway, I started to use the ne.c source as a
start. Everything seems to fit well, but I can not use the
ethernet-structure in my char-driver because that would mean that I need
any type of protocol, right? So I got stuck inbetween a net and a char
device. Is there a way to use net-structures without protocols in
char-drivers?
And a general question: I do have problems understanding some concepts
in drivers. Is this list the right place to ask?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/