From: Jim Boedicker <jdb-sdi@earthlink.net>
To: gracecott@sancharnet.in
Cc: linux-c-programming@vger.kernel.org
Subject: Re: serial comm
Date: Sat, 01 May 2004 03:38:04 -0500 [thread overview]
Message-ID: <409361EC.9020903@earthlink.net> (raw)
In-Reply-To: <409296F0.4060204@sancharnet.in>
joy wrote:
> Hi, I am trying to send info thru the serial port using a program.it has
> to communicate with a USART (intel 8251A)
> on a single board 8085 kit. any suggestions as to how I can implement this?
>
> Thanx in advance,
> Joy.M.M
>
Assuming you have the Linux documentation installed on your system, why
don't you try reading this document:
/usr/doc/Linux-HOWTOs/Serial-Programming-HOWTO
That Should help you out! ;^)
Jim
--
UNIX and LINUX are Hot, They're more than Hot, They're Steaming, They're
Quicksilver Lightning with a Laserbeam Kicker!
next prev parent reply other threads:[~2004-05-01 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 18:12 serial comm joy
2004-05-01 8:38 ` Jim Boedicker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-03 8:44 Joao Carneiro - DLS
2004-05-05 17:31 ` joy
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=409361EC.9020903@earthlink.net \
--to=jdb-sdi@earthlink.net \
--cc=gracecott@sancharnet.in \
--cc=linux-c-programming@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).