On Sun, Aug 25, 2019 at 02:58:47PM +0200, Otto Moerbeek wrote:
> On Sun, Aug 25, 2019 at 08:32:04PM +0800, Michael Mikonos wrote:
>
> > Hello,
> >
> > I noticed that flex is too trusting and assumes
> > calloc/malloc will always succeed. Hopefully I
> > caught all of them.
> > I tried to follow t
Hi all,
Today, I've decided to try openrsync(1) instead of cp(1) and here
my thoughts so far:
1. Without rsync package installed, as is the case on a fresh OpenBSD
install, openrsync's --rsync-path attribute becomes compulsory, i.e.:
$ touch file
$ openrsync file /tmp
/us
Hi Richard,
I'm still getting congestion using acpihpet0. Not sure about
the arp, i don't think there is that much. Older hardware
using bsd.mp on the same lan doesn't have this issue.
Thanks!
On Aug 22, 2019, at 5:57 AM, Richard Procter
wrote:
Hi Eric,
I was unfamiliar with how the conges
1) Fix max frame length check to account for the firmware's Rx result
header in the buffer, which contains two uint16_t fields.
Frame data begins after this header.
2) Do not write to mbuf length fields before the mbuf has been removed
from the Rx ring.
Based on dragonfly commit 96eaec
On Tue, Aug 27, 2019 at 06:48:43AM +0100, Jason McIntyre wrote:
>
> On Tue, Aug 27, 2019 at 10:50:05AM +0800, Kevin Lo wrote:
> > Hi,
> >
> > The diff below adds support for RTL8153B to ure(4).
> > Tested on Totolink u1003.
> >
>
> morning. the changes for ure.4 are fine, but can you adjust the
