Date: Sat, 30 Jul 2016 12:26:02 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Michal Meloun <mmel@freebsd.org>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Svatopluk Kraus <skra@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: INTRNG (Was: svn commit: r301453....) Message-ID: <3d17565e-8831-295a-46be-6341e17a8e6b@freebsd.org> In-Reply-To: <CANCZdfqmLGq3d2i_u3TVHGMWT2SWFSSUmfXD%2BS-MBimmBfCbRA@mail.gmail.com> References: <201606051620.u55GKD5S066398@repo.freebsd.org> <8bfd8668-bc49-e109-e610-b5cd470be3ec@freebsd.org> <57950005.6070403@FreeBSD.org> <f82018ee-51e7-60fa-2682-f0ef307a52b5@freebsd.org> <57961549.4020105@FreeBSD.org> <e2cace17-0924-2084-5fcf-626f87e41cc3@freebsd.org> <CANCZdfr%2BZ4XxXRY0yMiWXwp=8iKq54y3uJ9-OfAOdfxAs1qdtw@mail.gmail.com> <f94bfd25-fabf-efc3-55c9-cfdfd9e4d6e6@freebsd.org> <CANCZdfpz=z3gc3pyb_Qssa3vGJSnPv_r6J-SWDPPpE9zPYB9=w@mail.gmail.com> <ab44ddb1-515b-94ac-6b12-673b7c53d658@freebsd.org> <57976867.6080705@FreeBSD.org> <f2edac8f-2859-cd98-754e-881e2b2d1e63@freebsd.org> <5798E104.5020104@FreeBSD.org> <a5d43044-1733-6cc7-2e99-e85b60b0fcf3@freebsd.org> <579A25BB.8070206@FreeBSD.org> <30790e40-58b4-3371-c0f0-b7545571f389@freebsd.org> <579AFFC5.1040005@FreeBSD.org> <eb603349-eb88-866d-7a26-9e026518fd39@freebsd.org> <579CD355.1050203@FreeBSD.org> <460fa0b3-ddb7-6247-2412-3d75a589d5e7@freebsd.org> <CANCZdfqmLGq3d2i_u3TVHGMWT2SWFSSUmfXD%2BS-MBimmBfCbRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/30/16 11:06, Warner Losh wrote: > On Sat, Jul 30, 2016 at 10:59 AM, Nathan Whitehorn > <nwhitehorn@freebsd.org> wrote: >> It's not just a few lines change. Newbus provides no mechanism for a bus to >> attach at two different bus passes. > Sure it does. That's used in the Atmel code (which might not be in the tree) for > some things. Newbus lets you know for each new pass that something is happening. > > Perhaps you could be clearer as to what exactly it doesn't provide. > > Warner > interesting. I hadn't realized that. We'd need to find all the bus drivers in the tree and make them attach this way, I guess. There are still some ordering dilemmas here coming from the static nature of the ordering. For example, if you have two PICs supported by the same driver, one of which is attached to the other, how do you order their attachments? I have a whole list of these at https://wiki.freebsd.org/Complicated_Interrupts. The list is basically the full set of weird cases we support with the current code. It would be great to get some responses to how you would implement those specific things with this new API. As usual, there are two things I would like to see: 1. A case of something that wasn't supported by the old API, but is supported by the new API. 2. How I would support all of the complicated cases the existing code supports, listed on the wiki, with the new API. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3d17565e-8831-295a-46be-6341e17a8e6b>