Date: Thu, 16 Nov 2006 09:31:54 -0800 (PST) From: mjacob@freebsd.org To: John Baldwin <jhb@freebsd.org> Cc: Scott Long <scottl@samsco.org>, src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, ru@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/em if_em.c if_em.h src/sys/dev/mpt mpt.h mpt_pci.c Message-ID: <20061116092809.O9739@ns1.feral.com> In-Reply-To: <200611161114.42297.jhb@freebsd.org> References: <455BA0B6.1000109@samsco.org> <455BA914.7010602@samsco.org> <20061115.220331.-957833409.imp@bsdimp.com> <200611161114.42297.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> Is there some convention for MSI naming? Or are the resources >> basically anonymous? > > They are just IRQ values. On x86 they will be >= 256, but that may not be > true on other platforms. Other busses might also support multiple IRQs per > device (if you had HT peripherals I think they could do this). In general > IRQs are just cookies anyway. On x86 they index into the interrupt_sources[] > array. On other platforms they can have other meanings. It would almost be > better if SYS_RES_IRQ was just SYS_RES_INTR. > Let me put back on my very very dusty Solaris DDI team hat and point out that you either coerce the naming of interrupts to an architected number space (as did Digital Unix and does Linux and more or less does FreeBSD) or leave the naming of interrupts to the bus nexus it has meaning to.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061116092809.O9739>