Date: Mon, 09 Jul 2001 14:17:06 -0600 From: Warner Losh <imp@harmony.village.org> To: tlambert2@mindspring.com Cc: current@FreeBSD.ORG Subject: Re: Problems with ata probing twice. Message-ID: <200107092017.f69KH6J21578@harmony.village.org> In-Reply-To: Your message of "Mon, 09 Jul 2001 13:13:59 PDT." <3B4A1087.49E2EB20@mindspring.com> References: <3B4A1087.49E2EB20@mindspring.com> <3B49FE28.AEE25978@mindspring.com> <20010707215344.4B1F2380F@overcee.netplex.com.au> <200107072254.f67MsiJ73462@harmony.village.org> <200107091858.f69IwVJ20839@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3B4A1087.49E2EB20@mindspring.com> Terry Lambert writes: : Warner Losh wrote: : > : The problem with this is drivers that can't share : > : interrupts because there is no way to ask the hardware : > : which of several devices caused the interrupt. This : > : means that it's an attribute of the driver, not the : > : bus, so having the bus do this automatically would not : > : be correct. : > : > Give me an example of hardware that does this. I know of no devices : > in the tree that do this.... : : LANCE Ethernet? So what happens when you lose an interrupt for one of these devices? Does life suck? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107092017.f69KH6J21578>