From nobody Mon Nov 22 18:40:21 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2D8FE18AC82C for ; Mon, 22 Nov 2021 18:40:25 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HybgF0H8dz3jK0; Mon, 22 Nov 2021 18:40:25 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f2e:2500:c0bb:26f6:805a:a20b] (p200300cd5f2e2500c0bb26f6805aa20b.dip0.t-ipconnect.de [IPv6:2003:cd:5f2e:2500:c0bb:26f6:805a:a20b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 438499BEE; Mon, 22 Nov 2021 18:40:24 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: <60683883-6673-3e24-a040-4188d1e22556@freebsd.org> Date: Mon, 22 Nov 2021 19:40:21 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: problem with re(4) interface Content-Language: en-US To: Warner Losh , Chuck Tuffli Cc: Chris , FreeBSD-Current References: From: Stefan Esser In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------yWseIeoipEBVh79Pe10yL8Cf" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------yWseIeoipEBVh79Pe10yL8Cf Content-Type: multipart/mixed; boundary="------------00wRUFVtLXmuuDRiEB4atMA1"; protected-headers="v1" From: Stefan Esser To: Warner Losh , Chuck Tuffli Cc: Chris , FreeBSD-Current Message-ID: <60683883-6673-3e24-a040-4188d1e22556@freebsd.org> Subject: Re: problem with re(4) interface References: In-Reply-To: --------------00wRUFVtLXmuuDRiEB4atMA1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 22.11.21 um 18:55 schrieb Warner Losh: > On Mon, Nov 22, 2021 at 10:51 AM Chuck Tuffli wrote= : >=20 >> On Mon, Nov 22, 2021 at 9:34 AM Chris wrote: >>> >>> On 2021-11-22 08:47, Chuck Tuffli wrote: >>>> Running on a recent-ish -current >>>> # uname -a >>>> FreeBSD stargate.tuffli.net 14.0-CURRENT FreeBSD 14.0-CURRENT >>>> main-81b22a9892 GENERIC amd64 >>>> >>>> I'm having trouble using the second NIC interface in a bridge to >> provide >>>> network connectivity to bhyve VMs and need some help figuring out wh= at >> is >>>> wrong. >> ... >>> Because there's subtle differences between them; are you using the re= >> driver >>> from base, or from ports? >> >> The driver is from base. Didn't realize there was one in ports. >> >=20 > The ports driver is tricky... It's an older, buggier version of the bas= e > driver... *BUT* > a number of issues that aren't fixed in base are fixed in it (mostly > dealing better with > errata)... Ideally, we'd pull in the actual fixes from this driver, bu= t > it's a huge patch-set > where it's unclear which bits are for what thing fixed, so nobody (that= I > know of) has > gone through and even come up with an ugly patch for -current. I had hoped to be able to merge RTL8125 support into our driver, based on= the Realtek version the port uses, but gave up for lack of documentation that describes the RTL8125 chips and their PHYs. But in preparation for this work I have analyzed the differences between our driver in base and the one from Realtek. The Realtek driver: - lacks support for a lot of newer features (e.g. NETMAP) - has lots of conditional sections for antique FreeBSD versions - special cases some 50 chip versions with regard to features, timing, ..= =2E - contains microcode patches for nearly every RTL chip version There are even 4 chip versions of the RTL8125 (as the latest Realtek chip= ) that are distinguished in the driver (some need microcode patches, some d= o not). I have created patches to bring our version more in line with additions present in the Realtek driver (e.g. register definitions for RTL8125), bu= t had decided not to commit them, since I had no way of testing them with t= he variety of hardware the driver supports. I could commit the register definitions and other changes that I consider= low risk (even if I do not have the particular hardware revision the chan= ges address). It is sad that Realtek does not provide developers with detailed informat= ion. I'll look again for any leaked RTL8125 data books, but last I checked, th= ere were none. Regards, STefan --------------00wRUFVtLXmuuDRiEB4atMA1-- --------------yWseIeoipEBVh79Pe10yL8Cf Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmGb5BUFAwAAAAAACgkQR+u171r99UQL OwgAkLNnJMkSnBjEE+ndtYAAqGcPXdQrcEFNxKgEko0AVhgvWJMUb3axcVHqG7EuS01nz1EuXxAs 7+nxodAyRRvM9AXo1LW8BmWIS3rErsSWGykCYsOdclJVJrarNeYEsM7PCT0nbF7cpJH5R1Oim6yY WmYxgNBIgZPTQuRQ6/EkzGFS/Bd3mAJNm/C254U+hVKZtXJcE1Mfct+y33RqVfMtkpK/8XPzAmff mk9+WotqEE9tuSphoDpd89D9vdvDc7orrN/b3jLSNpZxyPWLlBMFY9PTJN8xVrVMIDRl883jbpbC geVD8SzxDKF33MLEZ4HFa9egA2a3fKAKJwKky8gQ1w== =JRhC -----END PGP SIGNATURE----- --------------yWseIeoipEBVh79Pe10yL8Cf--