From: Frank Kotler <fbkotler@comcast.net>
To: ALberto Andres <betorumbero@hotmail.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: Writing Linux Device drivers with NASM
Date: Mon, 13 Mar 2006 11:56:27 -0500 [thread overview]
Message-ID: <4415A43B.8030804@comcast.net> (raw)
In-Reply-To: <BAY102-F10A22842764940C4627CBAA3E00@phx.gbl>
ALberto Andres wrote:
> Hi everybody, I'm writing a guide about device drivers in assembly under
> linux. I'm using NASM. If anybody is interested here is the URL:
>
> http://albertoandreotti.5000megs.com/
Great, Alberto! Couple thing seems strange to me. I don't know anything
about device drivers, so perhaps it really *is* that strange...
You say:
2. Stack cleanup is performed by the called function.
3. Function name is decorated by prepending an underscore character
But that doesn't seem to be what you show...
And... your strings have got CRs in 'em. Is that normal/required for
device drivers?
I'm sure I'll have more questions... Great resource. Thanks!
Best,
Frank
next prev parent reply other threads:[~2006-03-13 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 15:45 Writing Linux Device drivers with NASM ALberto Andres
2006-03-13 16:56 ` Frank Kotler [this message]
2006-03-13 17:38 ` ALberto Andres
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=4415A43B.8030804@comcast.net \
--to=fbkotler@comcast.net \
--cc=betorumbero@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.