public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <deemkay@gmail.com>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev]  Re: mmxext flag
Date: Wed, 23 Mar 2005 07:23:43 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050323T081527-564@post.gmane.org> (raw)
In-Reply-To: 20050322111131.GA1180@phaenix.haell.com

Drake Wyrm <wyrm <at> haell.com> writes:

> > MMX2 is supported by Pentium 3 Katmai and Coppermine processors.
> > MMXEXT is supported by Athlon processors.  As far as I can tell
> > they're two very different things.  I'm confused.
> 
> You, and a lot of other people.
> 
> Also, I should correct my earlier statement. "MMX2" is _a_ marketing
> name for the "Extensions to the MMX Instruction Set", which were
> apparently introduced in the AMD-K6-2E+ and AMD-K6-IIIE+. You're right,
> though; the Athlon was the first mainline processor with mmx(2|ext).
> These extensions were subsequently adopted by Intel into the Pentium II
> much in the same way AMD adopted Intel's original MultiMedia eXtensions.
> 
> In my further research on the subject, it looks like Intel has been of
> late bragging up it's whiz-bang new "Intel Wireless MMX2 Technology".
> It's apparently an instruction set extension targeted at all-in-one
> cell-phone-camera-music-player-PDA gadgets. As far as I can tell, it's
> the only time Intel has used the term "MMX2".
> 
> Therefore, I recommend the use of "mmxext" to refer to the original
> multimedia extensions extensions, to avoid aggravating an
> already-confusing situation.

thanks, that makes things a little less murky.  i see that back in 98-99,
everyone was buzzing about the new KNI/MMX2 instruction set, but all references
to it seem to have disappeared when it was released.  the thing that confuses me
most is that MPlayer insists i have MMX2 support.  now that its flag has changed
to mmxext i find it strange that to enable MMX2 support for an Intel chip, I
have to enable support for an Athlon specific technology (at least that's the
only references i could find indicate).

but this is all semantics anyways.  thanks for the prompt reply.

--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2005-03-23  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21  8:19 [gentoo-dev] mmxext flag David Holm
2005-03-21 21:12 ` Drake Wyrm
2005-03-21 21:12   ` Drake Wyrm
2005-03-21 21:19   ` [gentoo-dev] " Ryan Hill
2005-03-22 11:11     ` Drake Wyrm
2005-03-22 11:11       ` Drake Wyrm
2005-03-23  7:23       ` Ryan Hill [this message]

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=loom.20050323T081527-564@post.gmane.org \
    --to=deemkay@gmail.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.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