From: b klein <b_klein1@yahoo.com>
To: linux-assembly@vger.kernel.org
Subject: Re: confused asm newbie
Date: Mon, 17 Nov 2003 03:47:25 -0800 (PST) [thread overview]
Message-ID: <20031117114725.79704.qmail@web41313.mail.yahoo.com> (raw)
In-Reply-To: <oprxh599q8b2epmx@localhost>
hello.
I hope you dont mind me shortening up a little
--- Philip Jacob Smith <pj@evobsyniva.com> wrote:
.
.
.
> I know what you mean about those assembly language
> books. They try to teach assembly like it's a
> language, when it's not (despite the "assembly
> language" name), and so they actually end up
> teaching how to use one particular assembler (which
> is really what you would want to call a language)
> with one particular operating system, and usually
> just do a lot of "here's how you do it" stuff and
> not enough "here's how this works" type stuff.
>
.
.
im trying to learn asm and use nasm, ald and a little
gdb for it. im not a newbie to programming or
assembly. ive learned it some time ago and come back
to it now. so my question is what is the important
bits that are worth learning? Im not interested in
learning a tool, i want to learn the .. well
'language'
but if it isnt a language, what should it be?
addressing modes, big-little endian, memory models,
8-16-32-64 (12?) bits processors, ports, interupts or
something else?
this is my first post, i hope it isnt too bad.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
next prev parent reply other threads:[~2003-11-17 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 12:03 confused asm newbie Jason Roberts
2003-10-23 12:53 ` Frederic Marmond
2003-10-23 14:38 ` willy meier
2003-10-23 15:50 ` Philip Jacob Smith
2003-11-01 17:07 ` GRUB sample kernel question ram
2003-11-01 21:24 ` Alexander Jänicke
2003-11-01 22:36 ` ram
2003-11-17 11:47 ` b klein [this message]
2003-11-17 12:29 ` confused asm newbie Frederic Marmond
2003-11-17 13:18 ` b klein
2003-11-17 13:36 ` Frederic Marmond
2003-11-18 2:51 ` Philip Jacob Smith
2003-11-20 21:52 ` b klein
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=20031117114725.79704.qmail@web41313.mail.yahoo.com \
--to=b_klein1@yahoo.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).