From: jeff <jko@bctonline.com>
To: linux-assembly@vger.kernel.org
Subject: Re: Keyboard and Mouse library
Date: Thu, 17 Jul 2003 00:17:27 -0700 [thread overview]
Message-ID: <200307170017.27280.jko@bctonline.com> (raw)
In-Reply-To: <200307160015.06499.lx@lxhp.in-berlin.de>
On Tuesday 15 July 2003 04:15 pm, hp wrote:
> yes, but (most of) those C-'programmers' don't understand (and ignore)
> assembly, so you might need to learn their 'language'...
True, most of Linux seems to be documented from a "C" programmers
perspective. One has to learn a long list of symbolic names for
things and then look in the .h files to see what codes they create.
Then you run into a lot of ifdef statements and have trouble
deciding if this symbol code is for BSD or AIX or ? Eventually,
it is necessary to compile the code and use GDB to see
what code is generated.
Sigh... I sometimes wish we had a simple assembler interface
to the kernel. If a call can only be accessed as root then
that would be handled etc. Everything clearly documented
for assembler code. No macros. No includes. Just
registers, dwords, words, and bytes. If common operations
require several kernel functions they could be added.
Enough dreaming... back to work <grin> Jeff Owens
next prev parent reply other threads:[~2003-07-17 7:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 13:19 Q: -fpic and $_GLOBAL_OFFSET_TABLE_ Oleg Nesterov
2003-07-15 23:24 ` hp
2003-07-16 10:03 ` Keyboard and Mouse library jeff
2003-07-15 19:54 ` Luciano Miguel Ferreira Rocha
2003-07-15 23:15 ` hp
2003-07-16 6:49 ` hp
2003-07-17 7:17 ` jeff [this message]
2003-07-16 3:09 ` linuxassembly
2003-07-16 6:46 ` hp
2003-07-16 8:07 ` linuxassembly
2003-07-17 16:45 ` Maciej Hrebien
2003-07-17 19:26 ` linuxassembly
2003-07-17 20:11 ` Maciej Hrebien
2003-07-17 22:12 ` hp
2003-07-17 12:29 ` jeff
2003-07-17 20:14 ` Konstantin Boldyshev
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=200307170017.27280.jko@bctonline.com \
--to=jko@bctonline.com \
--cc=linux-assembly@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).