.
Thanks!
Frank
The left-over pci setup differences are:
--- lspci-csm-201901272019-01-27 14:42:57.454117956 +0100
+++ lspci-uefi-20190127.12019-01-28 07:10:47.857701110 +0100
@@ -4,7 +4,7 @@
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1451
Subsystem: Advanced Micro
> On Jan 28, 2019, at 8:11 AM, Masanobu SAITOH wrote:
>
> On 2019/01/28 15:07, Jason Thorpe wrote:
>> Doesn’t it seem a little dangerous to just blindly enable?
>
> You mean it should be enable only when the secondary bridge is configured
> correctly?
>
> Both FreeBSD and OpenBSD blindly ena
Le 28/01/2019 à 03:36, David Holland a écrit :
On Sun, Jan 27, 2019 at 07:10:24PM +0100, Maxime Villard wrote:
> > Restore satlink's majors entries commented out and marked obsolete.
> > Otherwise they might accidentally get reused later and cause a
> > security problem.
>
> This is com
On 2019/01/28 15:07, Jason Thorpe wrote:
Doesn’t it seem a little dangerous to just blindly enable?
You mean it should be enable only when the secondary bridge is configured
correctly?
Both FreeBSD and OpenBSD blindly enabled it. One of the difference between
NetBSD and others is that they c
Doesn’t it seem a little dangerous to just blindly enable?
-- thorpej
Sent from my iPhone.
> On Jan 28, 2019, at 6:09 AM, SAITOH Masanobu wrote:
>
> Module Name:src
> Committed By:msaitoh
> Date:Mon Jan 28 04:09:51 UTC 2019
>
> Modified Files:
>src/sys/dev/pci: ppb.c
>
> L
Date:Sun, 27 Jan 2019 21:07:22 -0800
From:"Tom Spindler (moof)"
Message-ID: <20190128050722.ga37...@babymeat.com>
| I'd argue that "300ms" or "120us" or "15ns" are all pretty unambiguous,
| and that an exactly two char suffix would be rather unlikely to be line
On Mon, Jan 28, 2019 at 07:52:22AM +0700, Robert Elz wrote:
> That PR needed to be fixed, even before it was filed, as stray
> characters after the numeric value are more likely to be something
> attempting linux "sleep 2m" (ie: sleep 120) raher than someone
> attempting to sleep for a currency val
ergreen.c:5688)evergreen_startup]
*ERROR* radeon: error initializing UVD (-1).
kern info: [drm] ib test on ring 0 succeeded in 0 usecs
kern info: [drm] ib test on ring 3 succeeded in 0 usecs
Differences between pci configs (lspic -v)
--- lspci-csm-20190127 2019-01-27 14:42:57.454117956 +0100
On Sun, Jan 27, 2019 at 07:10:24PM +0100, Maxime Villard wrote:
> > Restore satlink's majors entries commented out and marked obsolete.
> > Otherwise they might accidentally get reused later and cause a
> > security problem.
>
> This is completely useless, please revert. You are re-adding ref
Date:Sun, 27 Jan 2019 16:38:34 +
From:David Holland
Message-ID: <20190127163833.gb20...@netbsd.org>
| The Unix shell environment is about processing text, and, largely,
| processing text in arbitrary ad hoc ways. It fundamentally relies on
| being able to tr
Date:Sun, 27 Jan 2019 22:56:17 +0100
From:Kamil Rytarowski
Message-ID: <1906f04e-93b9-a2c5-62a0-bf430ca60...@gmx.com>
| Passing to sleep 1,2 or 1.000 makes as much sense
The question isn't really whether it makes sense, that's up
to the user to decide, not us, but
On 27.01.2019 06:54, Kamil Rytarowski wrote:
> On 27.01.2019 05:42, Robert Elz wrote:
>> Yes, like English... I wasn't previously aware that '.' was ever used
>> as the grouping char, though I did believe that some locales use a
>> space for that purpose.
>
> I don't know whether there is formal
Le 27/01/2019 à 18:59, David A. Holland a écrit :
Module Name:src
Committed By: dholland
Date: Sun Jan 27 17:59:23 UTC 2019
Modified Files:
src/sys/arch/algor/conf: majors.algor
src/sys/arch/alpha/conf: majors.alpha
src/sys/arch/amd64/conf: majors.amd64
R* radeon: error initializing UVD (-1).
kern info: [drm] ib test on ring 0 succeeded in 0 usecs
kern info: [drm] ib test on ring 3 succeeded in 0 usecs
Differences between pci configs (lspic -v)
--- lspci-csm-20190127 2019-01-27 14:42:57.454117956 +0100
+++ lspci-uefi-20190127 2019-01-27 14:51:27.
Actually, I suspect now that what I remember reading was the rationale in the
page in XCU section 4 for the printf command.
kre
Date:Sun, 27 Jan 2019 18:42:22 +0300
From:Valery Ushakov
Message-ID: <20190127154222.gg18...@pony.stderr.spb.ru>
| This was changed in Issue 7. The link to the Austin group
| interpretations repository seems to be broken, though. Where can I
| find the text fo
On Sat, Jan 26, 2019 at 12:28:08PM +0100, Kamil Rytarowski wrote:
> This is where I disagree. In my opinion (of a native user of ",") -
> parsing locale specific input for such programs doesn't make sense.
>
> Locale specific format is in my opinion appropriate only for programs
> that proces
On Sun, Jan 27, 2019 at 12:03:09 +, Robert Elz wrote:
> Modified Files:
> src/usr.bin/printf: printf.c
>
> Log Message:
> Revert previous, it was based upon a misreading of the POSIX
> spec. POSIX requires "as if by calling strtod()" which we
> did already ... by calling strtod(). G
18 matches
Mail list logo
