Re: initial Intel Elkhart Lake Ethernet support / dwqe(4) at pci

On Wed, Oct 11, 2023 at 10:27:24AM +0200, Stefan Sperling wrote: > On Tue, Oct 10, 2023 at 09:06:59PM +0200, Mark Kettenis wrote: > > > OK for your diff. Please put it in and I'll rebase on top. > > > > done > > Thanks. Here is a rebased version. Re-tested with the same results. not all the incl

Re: Send international text with mail(1) - proposal and patches

On Thu, Oct 12, 2023 at 02:10:47AM +0200, Steffen Nurpmeso wrote: > Crystal Kolipe wrote in > : > |On Thu, Oct 12, 2023 at 12:36:48AM +0200, Steffen Nurpmeso wrote: > |> Non-7-bit clean headers need RFC 2047 (and/or RFC 2231) encoding. > | > |The use of MIME encoded words to encode header cont

umb: delete old v4 address before adding the new one

Currently when a umb device gets a new IPv4 address, it just adds it to the interface and tries to set the default route through it. If there's a different previous address, it stays there, and any routes using it also remain in place, so umb can't set the new default route. You see something lik

Re: tcp syn cache unlock

On Tue, Oct 10, 2023 at 05:26:14PM +0300, Vitaliy Makkoveev wrote: > On Tue, Oct 10, 2023 at 09:06:23AM -0500, Scott Cheloha wrote: > > On Fri, Oct 06, 2023 at 03:41:39PM +0200, Alexander Bluhm wrote: > > > On Fri, Oct 06, 2023 at 03:47:31PM +0300, Vitaliy Makkoveev wrote: > > > > On Fri, Oct 06, 2

Re: Send international text with mail(1) - proposal and patches

Crystal Kolipe wrote in : |On Thu, Oct 12, 2023 at 12:36:48AM +0200, Steffen Nurpmeso wrote: |> Non-7-bit clean headers need RFC 2047 (and/or RFC 2231) encoding. | |The use of MIME encoded words to encode header content is no longer |considered best practice. See, for example RFC 6532. Yes

Re: Send international text with mail(1) - proposal and patches

On Thu, Oct 12, 2023 at 12:36:48AM +0200, Steffen Nurpmeso wrote: > Non-7-bit clean headers need RFC 2047 (and/or RFC 2231) encoding. The use of MIME encoded words to encode header content is no longer considered best practice. See, for example RFC 6532. But as Omar said, let's get the basics of

Re: Send international text with mail(1) - proposal and patches

Hello Omar. Omar Polo wrote in <2HJQ4VX5L4J1P.3G4A39B0RA6T7@venera>: ... |>MUAs always set appropriate MIME headers. RFC 2046 section 4.1.2 |>paragraph 8 also "strongly" recommends the explicit inclusion of a |>"charset" parameter even for us-ascii. So that really went me lookin

libc: _POSIX_TIMERS is defined to -1 despite largely functional support

The `_POSIX_TIMERS` macro is defined to -1, indicating no support for the POSIX timers option. This option indicates support for the `clock_getres`, `clock_gettime`, `clock_settime`, `nanosleep`, and `timer_*` functions. While the `timer_*` functions do not appear to be supported by OpenBSD, the ub

Re: initial Intel Elkhart Lake Ethernet support / dwqe(4) at pci

On Wed, Oct 11, 2023 at 02:05:52PM +0200, Stefan Sperling wrote: > Anyway, here is an eephy(4) diff to enable/disable delays on the 88E1512. That diff wasn't quite right. The register offset should be 0x21, and Linux configures delays every time after link auto-negotiation. I am still unsure if t

Re: Some bwfm(4) diffs

Peter J. Philipp wrote: > On Tue, Oct 10, 2023 at 06:25:44AM +0200, Peter J. Philipp wrote: > > > > Thanks, I actually have one of these myself. So I'm going to > > > > investigate (and probably drop one of the diffs). > > > > > > I don't see any problems on my machine. Firmware loads and WiFi

Re: initial Intel Elkhart Lake Ethernet support / dwqe(4) at pci

> Date: Wed, 11 Oct 2023 10:27:24 +0200 > From: Stefan Sperling > > On Tue, Oct 10, 2023 at 09:06:59PM +0200, Mark Kettenis wrote: > > > OK for your diff. Please put it in and I'll rebase on top. > > > > done > > Thanks. Here is a rebased version. Re-tested with the same results. ok kettenis@

Re: initial Intel Elkhart Lake Ethernet support / dwqe(4) at pci

On Wed, Oct 11, 2023 at 10:27:24AM +0200, Stefan Sperling wrote: > On Tue, Oct 10, 2023 at 09:06:59PM +0200, Mark Kettenis wrote: > > > OK for your diff. Please put it in and I'll rebase on top. > > > > done > > Thanks. Here is a rebased version. Re-tested with the same results. Turns out I made

Re: Some bwfm(4) diffs

On Tue, Oct 10, 2023 at 06:25:44AM +0200, Peter J. Philipp wrote: > > > Thanks, I actually have one of these myself. So I'm going to > > > investigate (and probably drop one of the diffs). > > > > I don't see any problems on my machine. Firmware loads and WiFi works > > just fine on my MacBookPr

Re: initial Intel Elkhart Lake Ethernet support / dwqe(4) at pci

On Tue, Oct 10, 2023 at 09:06:59PM +0200, Mark Kettenis wrote: > > OK for your diff. Please put it in and I'll rebase on top. > > done Thanks. Here is a rebased version. Re-tested with the same results. diff refs/heads/master refs/heads/dwqe commit - 8af2f04850cda85ea291bfaddc0e4d58c40f2935 comm

Re: bwfm(4): support scan v3

On Tue, Oct 10, 2023 at 11:41:39PM +0200, Mark Kettenis wrote: > The firmware for the BCM4388 has yet another version of the "escan" > command. But we can treat it the same as v2 since it just added a new > parameter in place of some padding. We just set that new parameter to > zero, which doesn'

Re: mail(1) MIME support [PATCH]

More changes: - I changed my overpopulated Message-ID for the function used by smtpd(8) (generate_uid()). Now the Message-ID generated by mail(1) is identical to the one generated by smtpd(8). - Added a conditional to skip adding the Message-ID if the machine doesn't have hostname ye