From: blindnet@connect.reach.net (Jim Corbett)
To: blinux-list@redhat.com
Subject: Drivers question / statement.
Date: Wed, 4 Dec 1996 16:15:14 -0500 [thread overview]
Message-ID: <199612042115.QAA29857@connect.reach.net> (raw)
Hello there,
I posted a message yesterday, and wow what responsce. Nany thanks.
However I have one point that I would like to argue. That being C .
No matter what language you use to develope the source code, the compiling
and linking procedures convert the source into machine level instructions,
or dam near it.
Since C was developed with hardwware in mind, it is more than capable of
working at this level. It has the ability to work with BIOS, interrupts,
IRQ's and do a hell of a gob as well.
I have only been playing with C and C plus plus for one year and I am
already able to write programs to manage interrupt conflicts.
Equally as well Assembler was developed for the same purpose in mind. Most
of the com files that are currently in use were written in Assembler.
If the will is there, we need not rely upon companies to provide us with pre
written drivers. Its great if they will provide a utility that will allow
us to tackle our own drivers, but if its not available we shouldn't sit
around on our hands.
There is many powerful languages out there ready to be used for such a task.
I not saying that I am the greatest programmer, but only with a years
experience I am having a ball playing around with this stuff. its
challenging to see what I can come up with.
Just my opinion, thats all.
Never say never.
Jim Corbett
BLINDNET@reach.net
Jim Corbett
BLINDNET@reach.net
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199612042115.QAA29857@connect.reach.net \
--to=blindnet@connect.reach.net \
--cc=blinux-list@redhat.com \
/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).