unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ed L Cashin <cashin@cs.uga.edu>
Subject: Re: Controlling an external device with elisp
Date: Mon, 05 May 2003 11:57:27 -0400	[thread overview]
Message-ID: <87y91lpes8.fsf@cs.uga.edu> (raw)
In-Reply-To: 873cjtzu8b.fsf@gmx.net

upro <upro@gmx.net> writes:

> Ed L Cashin <cashin@cs.uga.edu> writes:
...
>> No, it's perfectly possible.  The thing is that you can *use* the
>> device from emacs but ultimately talking to hardware is a kernel
>> thing.  Assuming Linux, as your reference to the Coffee mini-HOWTO
>> would suggest, your choices are to ...
>>
>>   * build the circuit to recognize codes you can send using an
>>     existing driver
>>
>>     e.g., you could put the device on your first serial port and
>>     control it from emacs by writing strings like "please turn on the
>>     light" or numbers like 101 to /dev/ttyS0.
>>
>> or
>>
>>   * use IO primitives or write your own driver as suggested in the
>>     Coffee mini-HOWTO
>
> Are these IO primitives in C? I don't really understand this. 

Yes, in fact, this is where our thread becomes off-topic in
gnu.emacs.help.  It's linux-specific.  Remember section 3 in the
Coffee mini-HOWTO how they mention ioperm and outb?  It's that kind of
thing.

> I prefer the second suggestion, since I have very few knowledge of how
> to build circtios (not to speak of how to recognize signals...)

In that case, your work is mostly in creating a simple driver.  Using
it from emacs will be easy once it's in place.  

Some leads: I hear the O'Reilley book, _Linux Device Drivers_, is good
for learning how to write drivers.  You can also search the kernel
sources for examples of simple device drivers and think about joining
the kernelnewbies mailing list.

-- 
--Ed L Cashin     PGP public key: http://noserose.net/e/pgp/

      reply	other threads:[~2003-05-05 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 17:16 Controlling an external device with elisp upro
2003-05-04 18:52 ` Jonas Steverud
2003-05-04 19:50   ` upro
2003-05-05  0:48     ` Bijan Soleymani
2003-05-05  2:45     ` Ed L Cashin
2003-05-05  8:13       ` upro
2003-05-05 15:57         ` Ed L Cashin [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y91lpes8.fsf@cs.uga.edu \
    --to=cashin@cs.uga.edu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).