Date: Sun, 21 Jan 2018 10:58:16 -0700 From: Sean Bruno <sbruno@freebsd.org> To: Andre Albsmeier <andre@fbsd.e4m.org> Cc: svn-ports-head@freebsd.org Subject: Re: svn commit: r459464 - in head/sysutils/devcpu-data: . files Message-ID: <9387cf18-fc18-b00c-fdae-2942229513b9@freebsd.org> In-Reply-To: <20180121081159.GA1434@voyager> References: <201801191928.w0JJS8DL067070@repo.freebsd.org> <20180121081159.GA1434@voyager>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --D44KNpaWvRa6hebo2bo2458V3mEX9pNzx Content-Type: multipart/mixed; boundary="Y4KcGrr2NqosXbndPe5OyBNbwH5E9ypat"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: Andre Albsmeier <andre@fbsd.e4m.org> Cc: svn-ports-head@freebsd.org Message-ID: <9387cf18-fc18-b00c-fdae-2942229513b9@freebsd.org> Subject: Re: svn commit: r459464 - in head/sysutils/devcpu-data: . files References: <201801191928.w0JJS8DL067070@repo.freebsd.org> <20180121081159.GA1434@voyager> In-Reply-To: <20180121081159.GA1434@voyager> --Y4KcGrr2NqosXbndPe5OyBNbwH5E9ypat Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 01/21/18 01:11, Andre Albsmeier wrote: > On Fri, 19-Jan-2018 at 19:28:08 +0000, Sean Bruno wrote: >> Author: sbruno >> Date: Fri Jan 19 19:28:08 2018 >> New Revision: 459464 >> URL: https://svnweb.freebsd.org/changeset/ports/459464 >> >> Log: >> sysutils/devcpu-data: Revert back to legacy microcode.dat implementa= tion. >=20 > Thanks! >=20 >> Either there is a problem with the Intel supplied microcode files or= >> cpucontrol does not yet understand how to process a micrcode update = file >> with multiple entries. >=20 > cpucontrol simply ignores all but the first one of concatenated updates= > (see my mail as of 18 Jan 2018 19:08:40). I don't know if this can be > considered a problem with the Intel file (at least it's their file ;-))= >=20 > Maybe a single file would work if it contained what cpucontrol calls > "extended signature table" but I have no idea if this is an official > and still supported Intel feature or where it came from... >=20 Yep. I dug into the details of the files this week and that was my conclusion as well. In the file that I was proposing as a exception in an earlier revision, it didn't have the extended sig table and one of the bytes wasn't set correctly, so it was skipped entirely. sean --Y4KcGrr2NqosXbndPe5OyBNbwH5E9ypat-- --D44KNpaWvRa6hebo2bo2458V3mEX9pNzx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlpk1LhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LYqQwf8D3unAYhhbQo3maqUZgcaXNi9Ijbkhkxu59FwohGwmlzR4iptnUNuLtDb 1J1J14RjbNYaZGjdJXNI9jJJQw4A89J5YSeFo8Fo+p/TmoXVkS37lexEZxOaUsLq eKY/GvBugY1fhQ/NBeWk8X9uj8a7LRyE658ZzENY5M4Gxts2ks9oVpBlBWZeLAEM nquJyMSB0IiqKF/ZBRZeuRVX/veQ+U/82v4JaTKwBvyS34ihWtu5V72X0im1r8p+ Ygjia6ZW0HifTnD+AYha8hrjGMTst0Q35MF8QHxRu4Bsowa/KPjAC5r2/mqcsi6L v6E41YlxHO4EvVH8LSdUFl07YEWo9w== =V/Xq -----END PGP SIGNATURE----- --D44KNpaWvRa6hebo2bo2458V3mEX9pNzx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9387cf18-fc18-b00c-fdae-2942229513b9>