I have some machines with fxp(4) built in and some PCI fxp(4) cards.
The only problem I've had with them is that the fxp(4) driver can't cope
with machines having 4GB or more of RAM. It works w/3GB or less. Can't
say about 3GB
> On Mar 12, 2020, at 6:36 PM, SAITOH Masanobu wrote:
>
> I have some cards. Those are too old, some cards doesn't work (broken).
I agree they're too old :-). I mainly care about making sure I break the
minimal set when working on net_mpsafe stuff. I know this driver worked on
Alpha and ARM
Updating src tree:
P src/distrib/sets/lists/modules/ad.aarch64
P src/distrib/sets/lists/modules/ad.arm
P src/distrib/sets/lists/modules/ad.mips
P src/distrib/sets/lists/modules/md.amd64
P src/distrib/sets/lists/modules/md.sparc64
P src/external/bsd/blacklist/bin/blacklistd.c
P src/external/bsd/bl
On 2020/03/13 10:23, Jason Thorpe wrote:
Is anyone currently using fxp(4) successfully? I am having trouble with link
stability on a new-in-box i82559 card, but on a non-x86 platform.
Thx.
-- thorpej
I have some cards. Those are too old, some cards doesn't work (broken).
--
---
Is anyone currently using fxp(4) successfully? I am having trouble with link
stability on a new-in-box i82559 card, but on a non-x86 platform.
Thx.
-- thorpej
Hi,
Martin Husemann wrote:
>> I launch X11. A cursor appears, evberything else is black.
>> Computer resets.
>> Fun.
> Give us some details ;-)
>
> I updated a machine today and it does not do that - most likely this is
> graphics card/driver related.
Oh, my tree is of yesterday, because it takes
On Thu, Mar 12, 2020 at 06:40:13PM +0100, Riccardo Mottola wrote:
> Hi!
>
> I completed now build and full userland including X, installed.
>
> I launch X11. A cursor appears, evberything else is black.
> Computer resets.
> Fun.
Give us some details ;-)
I updated a machine today and it does not
Hi!
I completed now build and full userland including X, installed.
I launch X11. A cursor appears, evberything else is black.
Computer resets.
Fun.
Riccardo
On Wed, Mar 11, 2020 at 06:45:06PM +0100, Maxime Villard wrote:
> Please CC me for issues related to NVMM, there is a number of lists where
> I'm not subscribed.
>
> My understanding is that this commit is the cause (CC ad@):
>
> https://mail-index.netbsd.org/source-changes/2019/12/06/msg1
Paul Ripke writes:
> Currently, fdatasync requires a file descriptor open for writing, as
> per IEEE Std 1003.1, 2004:
> [EBADF]
> The fildes argument is not a valid file descriptor open for writing.
> https://pubs.opengroup.org/onlinepubs/009695399/functions/fdatasync.html
>
> While, IEEE Std 10
Robert Swindells writes:
>
> Is anyone else having problems doing a clean build ?
>
> It is stopping for me in src/lib/libtelnet with this:
>
> #create libtelnet/sra.d
> CC=/u8/build/aarch64-tools/bin/aarch64--netbsd-gcc
> /u8/build/aarch64-tools/bin/n
> bmkdep -f sra.d.tmp -- -std=gnu9
Is anyone else having problems doing a clean build ?
It is stopping for me in src/lib/libtelnet with this:
#create libtelnet/sra.d
CC=/u8/build/aarch64-tools/bin/aarch64--netbsd-gcc /u8/build/aarch64-tools/bin/n
bmkdep -f sra.d.tmp -- -std=gnu99 --sysroot=/var/obj/aarch64 -DHAS_CGETEN
Updating src tree:
P src/UPDATING
U src/distrib/sets/lists/modules/md.evbarm
P src/doc/3RDPARTY
P src/external/gpl3/gcc/dist/ChangeLog
U src/external/gpl3/gcc/dist/LAST_UPDATED
P src/external/gpl3/gcc/dist/MD5SUMS
P src/external/gpl3/gcc/dist/NEWS
P src/external/gpl3/gcc/dist/INSTALL/build.html
P
Currently, fdatasync requires a file descriptor open for writing, as
per IEEE Std 1003.1, 2004:
[EBADF]
The fildes argument is not a valid file descriptor open for writing.
https://pubs.opengroup.org/onlinepubs/009695399/functions/fdatasync.html
While, IEEE Std 1003.1-2008 (and later revisions):
[
14 matches
Mail list logo
