From owner-freebsd-hackers@FreeBSD.ORG  Fri Mar 22 08:09:24 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id CFEBCFAD
 for <hackers@freebsd.org>; Fri, 22 Mar 2013 08:09:24 +0000 (UTC)
 (envelope-from lists@yamagi.org)
Received: from mail.yamagi.org (mail.yamagi.org [IPv6:2a01:4f8:121:2102:1::7])
 by mx1.freebsd.org (Postfix) with ESMTP id 627F8AD2
 for <hackers@freebsd.org>; Fri, 22 Mar 2013 08:09:24 +0000 (UTC)
Received: from lennart-ws.pwag-local.de (unknown [212.48.125.110])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.yamagi.org (Postfix) with ESMTPSA id 31C7B1666312;
 Fri, 22 Mar 2013 09:09:22 +0100 (CET)
Date: Fri, 22 Mar 2013 09:09:22 +0100
From: Yamagi Burmeister <lists@yamagi.org>
To: kaltheat@googlemail.com
Subject: Re: Fwd: Intel microcode update
Message-Id: <20130322090922.6d383a7e8aa515d06851e650@yamagi.org>
In-Reply-To: <1231719416.448222.1363891714362.JavaMail.sas1@[172.29.251.236]>
References: <20130319220625.GB5368@sol>
 <1231719416.448222.1363891714362.JavaMail.sas1@[172.29.251.236]>
X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.17; amd64-portbld-freebsd9.1)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart=_Fri__22_Mar_2013_09_09_22_+0100_aInbnk7+YWOIAfP_"
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 08:09:24 -0000

This is a multi-part message in MIME format.

--Multipart=_Fri__22_Mar_2013_09_09_22_+0100_aInbnk7+YWOIAfP_
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,
yes the microcode file provided by Intel is incompatible with FreeBSD.
You'll need to split it into individual files for each CPU. I vaguely
remeber that there was a script or something like that bundled with one
of the ports. Nevertheless attached is a small C program which does the
same. It's not written by me, I just found it somewhere on the web.

Ciao,
Yamagi

On Thu, 21 Mar 2013 19:48:34 +0100
kaltheat <kaltheat@googlemail.com> wrote:

> 
> Hopefully some hacker could help me ...
> 
> ============ Forwarded message ============
> >From : kaltheat@googlemail.com
> To :  <questions@freebsd.org>
> Date : Tue, 19 Mar 2013 23:06:25 +0100
> Subject : Intel microcode update
> ============ Forwarded message ============
> 
>  
> Hi, 
>  
> I was wondering how to update microcode of an Intel CPU and came across 
> cpucontrol and sysutils/devcpu-data . But last mentioned port is not up-to-date 
> anymore. I searched Intel's webpages for microcode updates and found archives 
> for Linux containing one single microcode.dat file. Could someone tell me if 
> that file is compatible with FreeBSD? As devcpu-data installs .fw files it 
> might be proper to convert/compile microcode.dat in some way. How? 
>  
> Regards, 
> kaltheat 
>  
> 
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> 


-- 
Homepage:  www.yamagi.org
XMPP:      yamagi@yamagi.org
GnuPG/GPG: 0xEFBCCBCB

--Multipart=_Fri__22_Mar_2013_09_09_22_+0100_aInbnk7+YWOIAfP_--