> > Probably. but Jaromir only set it up for i386/amd64, and I was just
> > following his lead.
>
> Fair enough. So, who wants to be the first to connect an nvme to their
> vax? :-)
actually, martin@ already tried an nvme card on his sparc64 but
it appears to require PCIe 2.x at a minimum, and
"Maxime Villard" writes:
> Module Name: src
> Committed By: maxv
> Date: Sat Sep 17 12:00:35 UTC 2016
>
> Modified Files:
> src/sys/kern: kern_proc.c
>
> Log Message:
> Use VM_MAXUSER_ADDRESS for proc0, not VM_MAX_ADDRESS. It normally does not
> change anything, since kernel proces
"Paul Goyette" writes:
> Module Name: src
> Committed By: pgoyette
> Date: Sat Sep 17 02:27:19 UTC 2016
>
> Modified Files:
> src/distrib/sets/lists/modules: md.amd64 md.i386 mi
>
> Log Message:
> Fix sets lists for nvme module. Since it is being built only for the
> i386 and amd6
"Jaromir Dolecek" writes:
> Module Name: src
> Committed By: jdolecek
> Date: Fri Sep 16 15:20:50 UTC 2016
>
> Modified Files:
> src/sys/dev: ld.c ldvar.h
> src/sys/dev/ata: ld_ataraid.c
> src/sys/dev/i2o: ld_iop.c
> src/sys/dev/ic: ld_aac.c ld_cac.c ld_icp.c ld_ml
Hi,
From: Masanobu SAITOH , Date: Tue, 20 Sep 2016 14:02:37
+0900
> On 2016/09/19 11:00, Ryo ONODERA wrote:
>> Hi,
>>
>> With this change, the following wm(4) device links in 10BASE-T when it
>> is connected to 100BASE or 1000BASE hub.
>
> Could you show me the dmesg of wm and *phy?
Here is wm
