Re: Obvious one-liner - Use 3DNOW on MK8

From: James M. (dart_at_windeath.2y.net)
Date: 08/22/04

  • Next message: Lee Revell: "Re: Linux Incompatibility List" 
    Date:	Sun, 22 Aug 2004 00:52:27 -0500
To: Andi Kleen <ak@muc.de>

    Then perhaps the code should be removed or at least explain in the help
    why it can't be selected...do you have a preference?

    Does having this disabled confuse apps like Mplayer who detect the cpu
    and expect it to be there? I'm guessing the kernel handles it correctly
    but I'm just curious.

    Andi Kleen wrote:
    > "James M." writes:
    >
    >
    >>Title says it...my Athlon 64 definitely uses 3DNOW. Patch changes
    >>arch/i386/Kconfig and has a 3 line fudge factor(I created it a few
    >>kernels back). Might want to check other arches for the same bug.
    >
    >
    > It it's not a bug, it is a feature. The K8 is better off not using
    > the 3dnow memcpy, which is the only feature this CONFIG controls.
    >
    > Please don't apply.
    >
    > -Andi
    >
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Lee Revell: "Re: Linux Incompatibility List"
    • Quantcast