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 17:07:51 +0200 [thread overview]
Message-ID: <20110912170751.039f5c77@milhouse> (raw)
In-Reply-To: <F55731B4-001F-40B0-A38B-D0AD964CF590@ing.unibs.it>
On Mon, 12 Sep 2011 16:44:48 +0200
francesco.gringoli at ing.unibs.it wrote:
> BTW starting with ucode11 there are a couple of new jumps, opcodes 0x70 and 0x70|1. If I'm not wrong they are not documented BUT they behave exactly as je and jne. Did you ever take a look at them? They seem duplicate opcodes but it's weird that they duplicate wires on the chips.
I didn't check that, yet.
Maybe they are faster, but must not be used under certain conditions.
Or maybe they don't have the "ret problem". These are pure guesses, though...
--
Greetings, Michael.
next prev parent reply other threads:[~2011-09-12 15:07 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
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 [this message]
-- 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=20110912170751.039f5c77@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).