From: Zappacky <zappacky.lists@gmail.com>
To: G L <gusgl2001@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Volunteer for BC4328 Development
Date: Fri, 25 Jul 2008 06:09:01 -0400 [thread overview]
Message-ID: <4889A63D.1080005@gmail.com> (raw)
In-Reply-To: <BAY108-W2814460AA0EC5F04885C08A68B0@phx.gbl>
G L wrote:
> I see from the mailing lists that Zappacky was also interested in this.
> Perhaps Zappacky can give me info as to how he got started here.
>
I absolutely can! I've been a tad bit inactive lately, as I recently got a full
time job, but I'll be restarting work on it soon. I can't give you a whole lot
of info right now (I'm running out the door), but I just wanted to let you know
that I'm not dead/invisible/gone.
Welcome to the team!
In a separate email I have sent you 3 pdf files which I have found EXTREMELY
helpful. They are the MIPS ABI (so you know what the heck the stack is doing and
how parameters etc are laid out), the MIPS IV instruction set (a nice
reference), and the MIPS programmmer's guide (also a nice reference).
-Andrew (a.k.a. Zappacky)
parent reply other threads:[~2008-07-25 10:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BAY108-W2814460AA0EC5F04885C08A68B0@phx.gbl>]
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=4889A63D.1080005@gmail.com \
--to=zappacky.lists@gmail.com \
--cc=gusgl2001@hotmail.com \
--cc=linux-wireless@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).