From nobody Fri Sep 13 14:13:32 2024 X-Original-To: freebsd-net@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 4X4x9t006nz5Tsh8 for ; Fri, 13 Sep 2024 14:13:38 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Received: from cm0.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X4x9r1vBRz4Xqx for ; Fri, 13 Sep 2024 14:13:35 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-net@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-net@dino.sk Received: from zeta.dino.sk ([84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by cm0.netlabit.sk with ESMTPSA id 0000000001496E75.0000000066E4488D.0001010D; Fri, 13 Sep 2024 16:13:33 +0200 Date: Fri, 13 Sep 2024 16:13:32 +0200 From: Milan Obuch To: freebsd-net@freebsd.org Subject: Re: Ethernet device with shared mdio Message-ID: <20240913161332.4749ce87@zeta.dino.sk> In-Reply-To: References: <20240913090747.48062204@zeta.dino.sk> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.3) List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.47 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_SHORT(-0.17)[-0.168]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4X4x9r1vBRz4Xqx On Fri, 13 Sep 2024 13:40:55 +0000 Mike Belanger wrote: > Thank you for the response and for sharing your scenario. >=20 > We=E2=80=99ve also hacked up the cgem and the ffec driver to support a sh= ared > mdio. That was not too difficult, but we have a new scenario where > the mdio is now being shared between two different devices that use > different drivers (ffec and eqos). This presents a few extra > challenges. Could you elaborate a bit more? Are your hacks published somewhere or could you share? > I was hoping that FreeBSD may have considered supporting a shared > mdio. We can come up with something, but if there is an existing > architecture/approach in the works=E2=80=A6we would like to use a consist= ent > approach. At first glance, miiproxy did not seem like a fit. I don't know anything specific. I think I saw some DTBs with shared MDIO, but did not analysed the details. And miiproxy was just possible solution for the case, where MDIO controller is being initialised after MII controller (which was my case), but I did use some hacks for proof of concept. > I do not have the hardware. I am trying to help somebody else with > this. I have seen the dtb. It=E2=80=99s a Variscite DAR-MX8M-PLUS. OK, this makes the development a bit slower :) Regards, Milan