From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43-asm, b43-dasm: Add 5 new instructions.
Date: Mon, 12 Sep 2011 13:35:46 +0200 [thread overview]
Message-ID: <20110912133546.6710c606@milhouse> (raw)
In-Reply-To: <alpine.LFD.2.02.1109121040030.18551@oracolo.ing.unibs.it>
On Mon, 12 Sep 2011 10:50:16 +0200 (CEST)
Francesco Gringoli <francesco.gringoli@ing.unibs.it> wrote:
> Opcode 0x101: multiply op1 and op2 and store upper 16 bits in op3.
> Suggested name "mul" (multiply).
So this means the lower 16 bits are discarded? Or where are they put?
My guess would be that there's also an instruction that multiplies
op1 with op2 and puts the lower 16 bits into op3.
What about opcode 0x100? Are you really sure it does the same as 0x101?
--
Greetings, Michael.
next prev parent reply other threads:[~2011-09-12 11:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 8:50 [PATCH] b43-asm, b43-dasm: Add 5 new instructions Francesco Gringoli
2011-09-12 9:12 ` Gábor Stefanik
2011-09-12 9:25 ` Michael Büsch
2011-09-12 10:09 ` francesco.gringoli at ing.unibs.it
2011-09-12 10:35 ` Michael Büsch
2011-09-12 10:58 ` francesco.gringoli at ing.unibs.it
2011-09-12 11:19 ` Michael Büsch
2011-09-12 13:16 ` francesco.gringoli at ing.unibs.it
2011-09-12 13:32 ` Michael Büsch
2011-09-12 9:15 ` Michael Büsch
2011-09-12 9:56 ` francesco.gringoli at ing.unibs.it
2011-09-12 10:02 ` Michael Büsch
2011-09-12 11:35 ` Michael Büsch [this message]
2011-09-12 13:49 ` francesco.gringoli at ing.unibs.it
2011-09-12 14:04 ` francesco.gringoli at ing.unibs.it
2011-09-12 14:13 ` Michael Büsch
2011-09-12 14:31 ` Michael Büsch
2011-09-12 14:44 ` francesco.gringoli at ing.unibs.it
2011-09-12 15:07 ` Michael Büsch
-- strict thread matches above, loose matches on Subject: below --
2011-09-12 15:23 Francesco Gringoli
2011-09-12 15:36 ` Michael Büsch
2011-09-12 17:30 francesco.gringoli at ing.unibs.it
2011-09-12 18:02 ` Michael Büsch
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=20110912133546.6710c606@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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).