Date: Mon, 22 May 2006 23:20:01 -0600 From: Scott Long <scottl@samsco.org> To: william wallace <avalonwallace@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: misc questions about the device&driver arch Message-ID: <44729B81.8010909@samsco.org> In-Reply-To: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
william wallace wrote: [...] > MSI: > I've bantered around different suggestions for an API that will support > this. The basic thing that a driver needs from this is to know > exactly how many message interrupt vectors are available to it. It > can't just register vectors and handlers blindly since the purpose of > MSI is to assign special meanings to each vector and allow the driver to > handle each one in specifically. [...] I just wanted to briefly say that an MSI implementation has been done recently, and that it should start getting wider circulation and review soon. That's not to say that more work and design can't be done in this area, but we should probably wait a bit and see what has been done already. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44729B81.8010909>