From nobody Tue Dec 21 08:57:47 2021
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 3A87218EA10A
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Tue, 21 Dec 2021 08:57:57 +0000 (UTC)
	(envelope-from freebsd-net@dino.sk)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4JJ9Mm1yq0z3qb2
	for <freebsd-net@freebsd.org>; Tue, 21 Dec 2021 08:57:55 +0000 (UTC)
	(envelope-from freebsd-net@dino.sk)
Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254])
  (AUTH: LOGIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
  by mailhost.netlabit.sk with ESMTPSA; Tue, 21 Dec 2021 09:57:48 +0100
  id 00DADC7E.61C1970C.0000201C
Date: Tue, 21 Dec 2021 09:57:47 +0100
From: Milan Obuch <freebsd-net@dino.sk>
To: freebsd-net@freebsd.org
Subject: Postponed/detached MII attachment?
Message-ID: <20211221095747.68f398c2@zeta.dino.sk>
X-Mailer: Claws Mail 3.18.0git303 (GTK+ 2.24.33; i386-portbld-freebsd11.4)
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-net
List-Help: <mailto:freebsd-net+help@freebsd.org>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Subscribe: <mailto:freebsd-net+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-net+unsubscribe@freebsd.org>
Sender: owner-freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4JJ9Mm1yq0z3qb2
X-Spamd-Bar: /
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
X-Spamd-Result: default: False [0.39 / 15.00];
	 RCVD_VIA_SMTP_AUTH(0.00)[];
	 ARC_NA(0.00)[];
	 NEURAL_HAM_MEDIUM(-0.57)[-0.571];
	 FROM_HAS_DN(0.00)[];
	 TO_MATCH_ENVRCPT_ALL(0.00)[];
	 R_SPF_ALLOW(-0.20)[+mx];
	 MIME_GOOD(-0.10)[text/plain];
	 TO_DN_NONE(0.00)[];
	 DMARC_NA(0.00)[dino.sk];
	 RCPT_COUNT_ONE(0.00)[1];
	 MID_RHS_MATCH_FROMTLD(0.00)[];
	 NEURAL_HAM_SHORT(-0.73)[-0.735];
	 NEURAL_SPAM_LONG(0.99)[0.994];
	 FROM_EQ_ENVFROM(0.00)[];
	 R_DKIM_NA(0.00)[];
	 MIME_TRACE(0.00)[0:+];
	 ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK];
	 SUBJECT_ENDS_QUESTION(1.00)[];
	 RCVD_TLS_ALL(0.00)[];
	 RCVD_COUNT_TWO(0.00)[2]
X-ThisMailContainsUnwantedMimeParts: N

Hi,

a week ago I tried to get some hint from hackers, no response there.
(Subject: Two devices created for one block in device tree?)

I have a board with SoC containing two MACs (cgem driver) plus two
PHYs, but MDIO bus controlling both PHYs is connected to second MAC.
Thus my problem is how can I attach miibus instance to first (cgem0)
driver after second one (cgem1) is initialized.

As noted in my mail mentioned above, I am aware of miiproxy device,
which should be basically the solution. It is used only for arge driver
in official FreeBSD src tree, which uses hints, while I need FDT based
device tree.

Could anybody offer any hint, pointer, assistance? I am trying to get
somewhere, but all my attempts do not yield usable resuld, yet.

Regards,
Milan