Date: Sun, 8 Jan 2012 23:27:25 +0100 From: Stefan Bethke <stb@lassitu.de> To: Marius Strobl <marius@alchemy.franken.de> Cc: freebsd-arch@freebsd.org Subject: Re: Extending sys/dev/mii Message-ID: <23477898-8D85-498C-8E30-192810BD68A8@lassitu.de> In-Reply-To: <20120108130039.GG88161@alchemy.franken.de> References: <8D025847-4BE4-4B2C-87D7-97E72CC9D325@lassitu.de> <20120104215930.GM90831@alchemy.franken.de> <47ABA638-7E08-4350-A03C-3D4A23BF2D7E@lassitu.de> <1763C3FF-1EA0-4DC0-891D-63816EBF4A04@lassitu.de> <20120106182756.GA88161@alchemy.franken.de> <95372FB3-406F-46C2-8684-4FDB672D9FCF@lassitu.de> <20120106214741.GB88161@alchemy.franken.de> <F60B2B70-049F-4497-BBA8-3C421088C1EA@lassitu.de> <20120108130039.GG88161@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 08.01.2012 um 14:00 schrieb Marius Strobl: > Okay, this is the kind of information I was looking for as coupling > devices with newbus that have no close relation in the hierarchy is > tedious. However, when not using newbus the question arises how do > you intend to associate the device_t of say arge0 with the mdiobus0 > hanging off somewhere beneath iicbus0? In my experimental tree, I've hacked together a small function that = parses a string for a devclass name and unit number, and looks that up. I'm also trying a number of other approaches; mainly I'm trying to = understand how newbus works, and what kind of driver I want at the = various points, ideally auto-attached, or configured by hints, instead = of by custom code. I think I'll need another couple of days to get a = good enough understanding of drivers, devclasses and their tree, and the = device tree. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23477898-8D85-498C-8E30-192810BD68A8>