Date: Thu, 12 Jul 2012 07:20:59 -0600 From: Warner Losh <imp@bsdimp.com> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-current@freebsd.org, Arnaud Lacombe <lacombar@gmail.com> Subject: Re: newbus' ivar's limitation.. Message-ID: <40098958-831C-49AE-8A7A-BE0B8EE15C34@bsdimp.com> In-Reply-To: <201207120801.25810.jhb@freebsd.org> References: <CACqU3MVh6shncm2Vtqj9oe_HxowWscCZ1eJf0q2F%2B=t_xKKBfQ@mail.gmail.com> <73F3FBC9-337C-4F61-9470-5173D6DAE56B@bsdimp.com> <CACqU3MX5M0Didz0MX0jeUCY-xeeyS1-ZLkayfkOJzEs8cUQLxg@mail.gmail.com> <201207120801.25810.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 12, 2012, at 6:01 AM, John Baldwin wrote: > New-bus is certainly not the only way to organize a device hierarchy = and is=20 > not perfect, but in your case I suggest you tone down your language = until you=20 > have enough information to develop an informed opinion. It is also not the only way to represent relationships between objects, = or to export services to the rest of the kernel. =46rom earlier = descriptions, it seems like some of these relationships aren't very = newbus-y. =46rom what I know about FDT, many of them are 'this device's = interrupt pin is tied to GPIO 12 on controller 3' which isn't a = parent/child relationship, but rather some kind of interrupt cookie = you'll need to implement bus_setup_intr. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40098958-831C-49AE-8A7A-BE0B8EE15C34>