Go Job Hunting at the LQ Job Marketplace
Go Back > Forums > Linux Forums > Linux - Hardware
User Name
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?


  Search this Thread
Old 05-30-2013, 03:58 PM   #16
LQ Newbie
Registered: May 2013
Location: Rolla, MO
Distribution: Mint
Posts: 9

Original Poster
Rep: Reputation: 0

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?
Old 05-30-2013, 04:05 PM   #17
Senior Member
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 3,685
Blog Entries: 10

Rep: Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391Reputation: 1391
Yes, if your passing 802.x packets you use Ethernet frames.
2 members found this post helpful.
Old 06-01-2013, 12:23 PM   #18
LQ Guru
Registered: Mar 2008
Posts: 14,897

Rep: Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098Reputation: 2098
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.

Last edited by jefro; 06-01-2013 at 12:25 PM.
1 members found this post helpful.
Old 06-01-2013, 12:51 PM   #19
LQ Newbie
Registered: May 2013
Location: Rolla, MO
Distribution: Mint
Posts: 9

Original Poster
Rep: Reputation: 0
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.
Old 06-01-2013, 06:42 PM   #20
Senior Member
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,221

Rep: Reputation: 1098Reputation: 1098Reputation: 1098Reputation: 1098Reputation: 1098Reputation: 1098Reputation: 1098Reputation: 1098
You aren't writing a network driver.

And serial drivers already exist. So you may as well drop it as you have been told how to configure TCP/IP over serial.

Even if you were writing a network driver, you still wouldn't rewrite TCP/IP. Just look at some old ethernet drivers for an example.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Serial Port Device Driver GeorgeOfTheBush Linux - Software 1 11-08-2009 01:50 PM
TTy driver how to use underlying serial port vicky_driver Linux - Hardware 0 12-26-2008 05:48 AM
4 port Serial Card Driver DavidHB Linux - Software 4 09-17-2006 07:37 AM
Driver for serial port vasanthraghavan Linux - Software 0 01-31-2005 03:52 PM
serial port driver? abhay7182 Linux - Software 1 08-26-2004 05:32 AM

All times are GMT -5. The time now is 05:37 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration