Looking for example network driver that uses serial port (2.6.34)
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The board we currently use has linux running on it, and currently makes use of ethernet and wifi network interfaces. I don't know if this helps answer your question, but the program that actually does the communicating is a c++ program that makes use of sockets to communicate with other machines running the same program. What I was hoping to accomplish is to provide a network interface that could be used as a replacement for the ethernet and wifi connections. So the network interface needs to show up when I do "ifconfig" but it doesn't yet because I'm the one writing the driver for it. The communication device is going to be something external to the TS-7800 so really isn't specific to this board. The way in which it actually connects to the board that is going to make use of it hasn't been decided, but it has been suggested that the 232 connection will be used, which is why I'm trying to work with that for now.
Forgive my networking inexperience, but does the Ethernet (and ethernet frame) stuff apply when you're not using RJ45 for connecting the devices on a network?
There was rs-232c way before any thought of tcp/ip. I'd guess it unlikely that you would use ip over serial for an industrial device. I have seen a number of industrial devices that have moved up to IP when modified over the prior serial devices. If your end device (which must be a secret) uses serial communications then say it. If it uses some sort of serial over ip then say that. The built in ethernet would be only useful if it has to communicate to other tcp/ip ethernet devices using common switches/hubs.
There are many books on how to program for serial communications and all the old tools are still available like kermet and zmodem. All this was very common 20 years ago.
The nature of the device isn't a secret, it just doesn't exist yet, that's why I know nothing about it. This is part of an independent study research project for school. I'm just being asked to do some ground work for when it does exist. The problem is that I don't know much about networking, or writing device drivers, so I'm trying to learn as I go, but having a hard time finding real (working) examples.
What I'm trying to accomplish in the short run is to have a "fake" network interface that our current software can bind to in the same way it currently makes use of the ethernet network it is currently using. So if I'm not mistaken, that means I need to use IP, correct? Is it possible to get to the point where I'm creating an interface (that would show up on ifconfig) that I can bind to and just dump outgoing traffic to the serial port without worrying about packaging the information correctly? Even if the 232 connection isn't used in the future, I'd like to do this so that I can demonstrate that it is indeed creating output, even if it is useless. I'm under the impression that I need to know more about the device to determine how it should be packaged, but I'm hoping that I can get this "fake" driver working now (just dumping useless stuff to the serial port) and later fix it when the device is better specified.