Date: Sun, 13 Aug 2000 16:57:56 -0600 From: Warner Losh <imp@village.org> To: Devin Butterfield <dbutter@wireless.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: "Unknown" driver gobbles resources?? Message-ID: <200008132257.QAA10640@harmony.village.org> In-Reply-To: Your message of "Sun, 13 Aug 2000 05:11:30 PDT." <39969072.EED2B8F6@wireless.net> References: <39969072.EED2B8F6@wireless.net> <200008112235.PAA00839@mass.osd.bsdi.com> <39953196.1103F555@wireless.net> <200008121302.JAA00442@jupiter.delta.ny.us>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <39969072.EED2B8F6@wireless.net> Devin Butterfield writes: : So my question is this: Do I need to do anything special to recover the : resources from the unknown driver so that during loading *my* module can : get the resources it needs?? Do I need to add something to my identify, : probe, or attach routines to make this work right? With modern enough versions of -current, you shouldn't have to do anything at all to make this work. It should just happen. And you'll likely not need an identify routine. The Unknown device just sucks up the plug and play resources. Therefore, there's already a device node in the tree addociated with that plug and play hardware, so your probe routine will just be called. However, this is fairly recent (like on the order of the first part of July, 2000). Before that you did ineed have to jump though many many hoops to make this work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008132257.QAA10640>