On Tue, 2008-06-10 at 05:16 +0200, Paul B. Mahol wrote: > On 6/9/08, Coleman Kane <cokane_at_freebsd.org> wrote: > > Ignore the previous patch (#2) and try this one instead: > > * > > http://people.freebsd.org/~cokane/patches/if_ndis-spinlock-to-mtx3.patch > > > > Fine for me, LOR appear any more. Thanks for the report. > > BTW: I'm dont like first line showing over and over again. It would be nice > if that clueless message goes away. Is this a new message introduced with my changes? I sure hope not! Typically that message is there because the API functions (in your case IoGetDeviceObjectPointer) for Win32/Win64 DDK are not completely implemented in NDIS. Different Win32/Win64 drivers may yield different "no match for" messages. In my case, I went through about 10 drivers that had unmatched symbols before I found one that worked flawlessly. Try one of the NDIS drivers I have posted here: * http://www.cokane.org/dokuwiki/freebsd/amd64_compatibility If you need a 32-bit driver, let me know and I'll send one over (the ones on my site are all AMD64). > > no match for IoGetDeviceObjectPointer <---- this one > ndis0: <Broadcom 802.11b/g WLAN> mem 0xf4000000-0xf4003fff irq 17 at > device 0.0 on pci16 > ndis0: [ITHREAD] > ndis0: NDIS API version: 5.1 > -- Coleman Kane
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:31 UTC