The marketing name is 'Xeon Processor Scalable Family'
Intel Xeon Bronze 3XXX processor
Intel Xeon Gold 6XXF processor
Intel Xeon Platinum 6XXF processor
Intel Xeon Platinum 8XXF processor
Intel Xeon Silver 4XXX processor
Intel Xeon Gold 5XXX processor
Intel Xeon Platinum 6XXX processor
Intel
On Fri, Feb 19, 2021 at 07:10:02PM +0100, Claudio Jeker wrote:
> Some TAL files now include an https URI where the TA can be fetched from.
> With this diff rpki-client will download the TA from https unless that
> fails and then fall back to rsync.
>
> This is not yet perfect but the diff is
> Date: Thu, 25 Feb 2021 20:10:00 +0100
> From: Marcus Glocker
>
> We had this discussion recently when fbtab(5) for xenodm(1) was fixed
> 6 weeks ago, but we didn't come to an agreement yet. tb@ asked me the
> same question yesterday whether we can add video(1) to fbtab to avoid
> manual chown
On Wed, Feb 24, 2021 at 09:21:56PM +0100, Theo Buehler wrote:
> On Wed, Feb 24, 2021 at 09:00:05PM +0100, Theo Buehler wrote:
> > On Wed, Feb 24, 2021 at 06:47:00AM +0100, Jan Klemkow wrote:
> > > another co-worker of mine has found an other regress in the LibreSSL
> > > legacy verifier. I took
Hi,
while testing different x509 validator corner cases i found that a bunch of
errors are currently not handled in libcrypto.
In particular duplicate or undecodable extensions are ignored.
The diff below sets EXFLAG_INVALID whenever X509_get_ext_d2i() returns
an error (other than "not found")
We had this discussion recently when fbtab(5) for xenodm(1) was fixed
6 weeks ago, but we didn't come to an agreement yet. tb@ asked me the
same question yesterday whether we can add video(1) to fbtab to avoid
manual chown of /dev/video0, which I think a lot of people do today.
Therefore here
On 2021/02/25 20:10, Marcus Glocker wrote:
> We had this discussion recently when fbtab(5) for xenodm(1) was fixed
> 6 weeks ago, but we didn't come to an agreement yet. tb@ asked me the
> same question yesterday whether we can add video(1) to fbtab to avoid
> manual chown of /dev/video0, which I
On Thu, Feb 25, 2021 at 08:00:32PM +, Stuart Henderson wrote:
> On 2021/02/25 20:10, Marcus Glocker wrote:
> > We had this discussion recently when fbtab(5) for xenodm(1) was fixed
> > 6 weeks ago, but we didn't come to an agreement yet. tb@ asked me the
> > same question yesterday whether
On Thu, Feb 25, 2021 at 09:34:45PM +0100, Mark Kettenis wrote:
> > Date: Thu, 25 Feb 2021 20:10:00 +0100
> > From: Marcus Glocker
> >
> > We had this discussion recently when fbtab(5) for xenodm(1) was fixed
> > 6 weeks ago, but we didn't come to an agreement yet. tb@ asked me the
> > same
On 2021/02/25 22:02, Marcus Glocker wrote:
> On Thu, Feb 25, 2021 at 08:00:32PM +, Stuart Henderson wrote:
>
> > On 2021/02/25 20:10, Marcus Glocker wrote:
> > > We had this discussion recently when fbtab(5) for xenodm(1) was fixed
> > > 6 weeks ago, but we didn't come to an agreement yet.
Hi,
My vaio repeatedly crashed by "Data modified on freelist"(*1) or other
memory corruptions. After my long time debug, I found the route cause
is a handling of references of LocalX, like the following:
If ((SMRW (0x0B, 0x16, 0x21, RefOf (Local0)) == Zero))
In the called
Hi
IA32_EPT_VPID_CAP_XO_TRANSLATIONS is specified as 0x0 and not (1ULL << 0)
ie 0 and not bit 0 as on.
Please see the attach diff to correct this and rename
IA32_EPT_VPID_CAP_XO_TRANSLATIONS to IA32_EPT_VPID_CAP_XO to reduce
wordyness.
Cheers
Adam
diff 0e7183d43c8ed36e5d169be05df61472565710eb
On Thu, Feb 25, 2021 at 02:55:22PM +0100, Karel Gardas wrote:
>
> > The marketing name is 'Xeon Processor Scalable Family'
> > Intel Xeon Bronze 3XXX processor
> > Intel Xeon Gold 6XXF processor
> > Intel Xeon Platinum 6XXF processor
> > Intel Xeon Platinum 8XXF processor
> > Intel Xeon Silver
On Fri, Feb 26, 2021 at 05:24:59PM +1100, Jonathan Gray wrote:
> On Thu, Feb 25, 2021 at 02:55:22PM +0100, Karel Gardas wrote:
> >
> > > The marketing name is 'Xeon Processor Scalable Family'
> > > Intel Xeon Bronze 3XXX processor
> > > Intel Xeon Gold 6XXF processor
> > > Intel Xeon Platinum
On Thu, Feb 25, 2021 at 09:14:06PM +, Stuart Henderson wrote:
> On 2021/02/25 22:02, Marcus Glocker wrote:
> > On Thu, Feb 25, 2021 at 08:00:32PM +, Stuart Henderson wrote:
> >
> > > On 2021/02/25 20:10, Marcus Glocker wrote:
> > > > We had this discussion recently when fbtab(5) for
I was testing mg's goto-line function via the minibuffer (M-x goto-line)
and I just kept my finger on the '0' key. After a brief time '0's
started appearing in the main buffer, where the cursor had been. For a
second I thought there had been an issue with memory allocation but after
looking at
On Thu, Feb 25, 2021 at 11:29:09AM +0100, Karel Gardas wrote:
> On 2/25/21 10:34 AM, Jonathan Gray wrote:
> > On Wed, Feb 24, 2021 at 05:01:50PM +0100, Karel Gardas wrote:
> > > Hello,
> > >
> > > attach patch adds some SkyLake-E related PCI ids. Tested on
> > > Kontron/Fujitsu
> > > D3598-B
On 2/25/21 10:34 AM, Jonathan Gray wrote:
On Wed, Feb 24, 2021 at 05:01:50PM +0100, Karel Gardas wrote:
Hello,
attach patch adds some SkyLake-E related PCI ids. Tested on Kontron/Fujitsu
D3598-B with Intel Xeon W-2123.
Thanks for review, comment(s) and/or commit.
Karel
I can only find a
There has been some interest here and there,
an I have been running it for about 1.5 years.
With crappy laptop cooling, failing CPU fans
and the summer approaching fast i think i'll
share the newest iteration.
Greetings Ben
===
This will throttle down your intel graphic card for
better thermal
On Thu, Feb 25, 2021 at 07:52:08AM +0100, Hrvoje Popovski wrote:
> Hi all,
>
> i'm getting this log after update to latest snapshot
>
>
> pkg_add -ui
> quirks-3.580 signed on 2021-02-24T18:23:18Z
> |No change in quirks-3.580String found where operator expected at
>
On Wed, Feb 24, 2021 at 05:01:50PM +0100, Karel Gardas wrote:
>
> Hello,
>
> attach patch adds some SkyLake-E related PCI ids. Tested on Kontron/Fujitsu
> D3598-B with Intel Xeon W-2123.
>
> Thanks for review, comment(s) and/or commit.
>
> Karel
>
I can only find a handful of Ubox/PCU
Less verbose output patch below. Still using 'Sky Lake-E' since I think
it's more close
to OpenBSD's 'Apollo Lake' and 'Gemini Lake' style then would be
'Skylake-E'.
diff --git a/sys/dev/pci/pcidevs b/sys/dev/pci/pcidevs
index ba975d05548..a9209c75bfc 100644
--- a/sys/dev/pci/pcidevs
+++
Patch below is less verbose and using Skylake-E name.
diff --git a/sys/dev/pci/pcidevs b/sys/dev/pci/pcidevs
index ba975d05548..8c629ba9e1a 100644
--- a/sys/dev/pci/pcidevs
+++ b/sys/dev/pci/pcidevs
@@ -4188,6 +4188,58 @@ product INTEL ATOMC2000_PCU_SMB 0x1f3c Atom C2000 PCU
SMBus
product
Tom Cosgrove in private email pointed out that even Intel is not
consistent in processors naming
and provided enough evidence that this is indeed 'Skylake-E'. I'll
submit corrected patch asap.
On 2/25/21 12:22 PM, Karel Gardas wrote:
Less verbose output patch below. Still using 'Sky
24 matches
Mail list logo
