[PATCH]: Add support to Realtek 8168GU to re(4) driver

Hi tech@, I put my hands today on a Dell Lattitude 3440 and it has an Atheros AR9565 and a Realtek 8168. Trying -current on it shows up that re(4) attaches but it cannot recognize the hardware revision and properly init the card (full dmesg at end): re0 at pci3 dev 0 function 0 Realtek

Re: [PATCH]: Add support to Realtek 8168GU to re(4) driver

at 06:02:41PM -0400, Rafael Neves wrote: Hi tech@, I put my hands today on a Dell Lattitude 3440 and it has an Atheros AR9565 and a Realtek 8168. Trying -current on it shows up that re(4) attaches but it cannot recognize the hardware revision and properly init the card (full dmesg at end

[PATCH]: Add nVidia GeForce GT 470M to pcidevs

Hi tech@, The patch below adds the nVidia GeForce GT 740M found on a Dell Lattitude 3440. This laptop has a onboard inteldrm(4) and this nVidia as dedicated graphics. Please, note two things. First, pcidump shows it a NVIDIA unknown but on Windows nVidia control panel recognizes it as a

Fix of sysctl.c rev. 1.191 related bug and unbreak diskless(8)

vfs.ffs.dirhash_maxmem=2097152 vfs.ffs.dirhash_mem=325453 vfs.nfs.iothreads=-1 Thanks in advance for any comments. Regards Rafael Neves dmesg: OpenBSD 5.3-current (GENERIC) #15: Thu Jul 4 11:52:29 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

Fix to diskless(8) manpage: add amd64 and i386 to the list of clients that needs rpc.bootparamd(8)

Hi, Amd64 and i386 diskless(8) setups need rpc.bootparamd(8) to be enabled to read /etc/bootparams. The patch below adds both archs to the list of the ones that needs rpc.bootparamd(8). Index: diskless.8 === RCS file:

Re: Fix to diskless(8) manpage: add amd64 and i386 to the list of clients that needs rpc.bootparamd(8)

...@bsws.de * Rafael Neves rafaelne...@gmail.com [2013-07-14 11:01]: Amd64 and i386 diskless(8) setups need rpc.bootparamd(8) no, they don't. True diskless(4) operation (with root on nfs) needs rpc.bootparamd(8) an *all* architectures. Merely booting a bsd.rd kernel only

Re: Fix of sysctl.c rev. 1.191 related bug and unbreak diskless(8)

On 7/15/13, Philip Guenther guent...@gmail.com wrote: On Sun, Jul 14, 2013 at 12:54 AM, Rafael Neves rafaelne...@gmail.com wrote: The patch below fixes a bug on sysctl(8) introduced by revision 1.191 of sysctl.c. After rev1.191, `sysctl vfs' mangles information about filesystems (mounted

Re: Fix to diskless(8) manpage: add amd64 and i386 to the list of clients that needs rpc.bootparamd(8)

On 7/14/13, Rafael Neves rafaelne...@gmail.com wrote: On 7/14/13, Theo de Raadt dera...@cvs.openbsd.org wrote: Date: Sun, 14 Jul 2013 18:51:13 +0200 From: Sebastian Benoit be...@openbsd.org Mark Kettenis(mark.kette...@xs4all.nl) on 2013.07.14 17:06:24 +0200: ... Index: diskless.8

Re: [patch] if-free cleanup in sys/arch

> pointers (see sys/lib/libsa/alloc.c). > > But we're going to fix that too, right? > > It seems that now NULL can be passed to this free implmenation. This has changed yesterday in revision 1.11 ( http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/lib/libsa/alloc.c.diff?r1=1.10=1.11=h ). Regards, Rafael Neves

Remove TMPDIR support from sendbug(1) and newfs(8) manpages

Hi, The TMPDIR enviroment support was removed from sendbug(1) and newfs(8), but the manpages still document them. The inlined patches remove these leftovers. Regards, Rafael Neves Patch: Index: sbin/newfs/newfs.8 === RCS file

Document the sendsyslog2(2) system call

quot;, so I thought that could be misleading as sendsyslog2(2) does not open the device, it is a direct channel. Comments? Regards, Rafael Neves Patch: Index: lib/libc/sys/Makefile.inc === RCS file: /cvs/src/lib/libc/sys/Makefile.i

Re: Manpage for uctuctl(4)

Hi, On Sun, Sep 18, 2016 at 03:33:00PM +0200, Ingo Schwarze wrote: > Hi, > > Mike Belopuhov wrote on Sun, Sep 18, 2016 at 01:35:45PM +0200: > > On Sun, Sep 18, 2016 at 06:15 +, Visa Hankala wrote: > >> On Sat, Sep 17, 2016 at 02:40:09PM +0100, Rafael Neves wrot

Re: Use who = 0 instead getpid(2) in setprioriy(2) call in watchdog(8)

On Sat, Sep 17, 2016 at 02:36:49PM +0100, Rafael Neves wrote: > Hi, > > The patch bellow replaces in watchdog(8), the setpriority(2) + getpid(2) > idiom with a single > setpriority(2) with who = 0. > [snip] Sorry, the patch in the original e-mail does not apply, here follows

Use who = 0 instead getpid(2) in setprioriy(2) call in watchdog(8)

Hi, The patch bellow replaces in watchdog(8), the setpriority(2) + getpid(2) idiom with a single setpriority(2) with who = 0. Index: usr.sbin/watchdogd/watchdogd.c === RCS file: /cvs/src/usr.sbin/watchdogd/watchdogd.c,v retrieving

Change a nice(3) call to setpriority(2) in top(1)

Hi, I found in top(1) a call to nice(3) that I think that should be changed to setpriority(2). When given the -q flag the manpage claims that top will be reniced to -20. This is implemented trough nice(3) taking advantage that a program are loaded with 0 niceness priority, so decrementing 20

Manpage for uctuctl(4)

Hi, Here follows a manpage for octuctl(4), based on dwctwo(4) manpage. I am not sure if the title should stop in Controller or in Interface, so I mantained the phrasing of commit. Index: share/man/man4/octuctl.4 === RCS file:

In renice(8), replace exit(3) call in main() with return

Hi, The patch bellow replaces an exit(3) call in main() to a return to enable the stack protector. Index: usr.bin/renice/renice.c === RCS file: /cvs/src/usr.bin/renice/renice.c,v retrieving revision 1.19 diff -u -p -r1.19 renice.c

Fix a typo in INSTALL.octeon

Hi, The patch below replace one "$loadaddr" to "${loadaddr}" in U-Boot instructions of INSTALL.octeon. Regards, Rafael Neves Index: install === RCS file: /cvs/src/distrib/notes/octeon/install,v retrieving revi

New driver apupgio(4): interface for LEDs and button of APU1. (Advices needed)

Hi tech@, I wrote a driver to control the APU1 LEDs and read the state of the pushbutton switch, like skgpio(4). I would like some reviews and hints about some project decisions that I have to make. I am cooking a diff to support APU{2,3,4}, but it is an extension of this code. Setup: Machine:

[PATCH]: Make -P option of mount_mfs(8) support DUIDs

Hi tech@, When I had to change a HD between machines I figured out that -P option of mount_mfs(8) does not work with DUIDs: # mount_mfs -P ca7552589896b01e.d swap /mnt mount_mfs: cannot stat ca7552589896b01e.d: No such file or directory mount_mfs(8) already allows a DUID as the `special`

Re: [PATCH]: Make -P option of mount_mfs(8) support DUIDs

On Mon, Apr 08, 2019 at 12:35:41AM +0100, Rafael Neves wrote: > Hi tech@, > > When I had to change a HD between machines I figured out that -P option > of mount_mfs(8) does not work with DUIDs: > > # mount_mfs -P ca7552589896b01e.d swap /mnt > mount_mfs: cannot st

Tighten nl(1) pledge(2) a bit

ess, except the file supplied. But it seemed like a hack. Comments? Regards, Rafael Neves Patch 1 (just pledge): Index: usr.bin/nl/nl.c === RCS file: /cvs/src/usr.bin/nl/nl.c,v retrieving revision 1.6 diff -u -p -r1.6 nl.c --- u

Re: [PATCH]: Make -P option of mount_mfs(8) support DUIDs

On Sun, Apr 14, 2019 at 08:05:21PM +0100, Rafael Neves wrote: > On Mon, Apr 08, 2019 at 12:35:41AM +0100, Rafael Neves wrote: > > Hi tech@, > > > > When I had to change a HD between machines I figured out that -P option > > of mount_mfs(8) does not work with DUID

Re: Tighten nl(1) pledge(2) a bit

On Sat, Apr 20, 2019 at 07:10:21PM -0600, Theo de Raadt wrote: > Rafael Neves wrote: > > > Hi tech@, > > > > The Patch 1 below tighten pledge(2) promises to stdio, after the > > freopen(3) call, > > I've commited this. > > > and replaces an exit(

[PATCH] Avoid leftover temporary mount points when using -P (mfs)

mnt() must changed to it work properly. The `created` if uses a <= by symmetry. But this is a differente issue, that I think could be changed in a separated diff. Regards, Rafael Neves Patch: Index: newfs.c === RCS file:

Re: [PATCH] Avoid leftover temporary mount points when using -P (mfs)

On Wed, Aug 28, 2019 at 03:39:17PM +0200, Otto Moerbeek wrote: > On Sat, Aug 17, 2019 at 12:13:50PM -0300, Rafael Neves wrote: > > > Hi, > > > > Submitting to tech@ to broader audience. > > > > When using -P option in mfs with a directory or a block devic

Re: [PATCH] Avoid leftover temporary mount points when using -P (mfs)

On Mon, Sep 02, 2019 at 07:26:27AM +0200, Otto Moerbeek wrote: > On Sun, Sep 01, 2019 at 05:01:55PM -0300, Rafael Neves wrote: > > > On Wed, Aug 28, 2019 at 03:39:17PM +0200, Otto Moerbeek wrote: > > > On Sat, Aug 17, 2019 at 12:13:50PM -0300, Rafael Neves wro

Re: [PATCH] Avoid leftover temporary mount points when using -P (mfs)

On Mon, Sep 02, 2019 at 03:59:48PM -0300, Rafael Neves wrote: > On Mon, Sep 02, 2019 at 07:26:27AM +0200, Otto Moerbeek wrote: > > On Sun, Sep 01, 2019 at 05:01:55PM -0300, Rafael Neves wrote: > > > > > On Wed, Aug 28, 2019 at 03:39:17PM +0200, Otto Moerbeek wrote: >

Re: [PATCH]: Make -P option of mount_mfs(8) support DUIDs

On Sat, May 04, 2019 at 06:18:27PM +0100, Rafael Neves wrote: > On Sun, Apr 14, 2019 at 08:05:21PM +0100, Rafael Neves wrote: > > On Mon, Apr 08, 2019 at 12:35:41AM +0100, Rafael Neves wrote: > > > Hi tech@, > > > > > > When I had to change a HD between m