Mail Archives: djgpp/1998/01/08/19:46:36
From: | Adam Young <ayoung AT ksu DOT edu>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Comparison: Serial Port Routines
|
Date: | Thu, 8 Jan 1998 18:19:28 -0600
|
Organization: | Kansas State University
|
Lines: | 26
|
Message-ID: | <Pine.SOL.3.96L.980108180450.18398A-100000@abc.ksu.ksu.edu>
|
NNTP-Posting-Host: | abc.ksu.ksu.edu
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hello All,
I have a question about the two serial routines written for DJGPP: BCSERIO
and SVAsync.
BCSERIO uses assembly to do all of its handling of the FIFO and such,
while SVASync uses mainly C to handle the serial port. What I am wanting
to know is what is the difference between the two methods (ie advantages
and disadvantages). I have always heard that assembly language is faster
than C. Here is what confuses me: Isn't the C code converted to assembly
language, therefore being just as fast as straight assembly?
This question came about from me trying to learn how interrupts are
handled by C and assembly when dealing with the serial port. I do not know
much about assembly language, but I do know alot more than I did a few
days ago. I have checked out "djgppasm.doc" and Ralf Brown's interrupt
list and other assembly sites the last few days. Which I guess leads me to
one more (kind of related) question: Can DJGPP handle interrupts on a
basic level like assembly can?
Hopefully, someone can see where I am coming from. I am really not sure
WHERE I am going with this, but it has me intrigued. Thanks in advance!
Adam
ayoung AT ksu DOT edu
- Raw text -