src-test2/sys/dev/an, branch release/5.2.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.2.0_cvs 2004-01-10T05:53:29Z This commit was manufactured by cvs2svn to create tag 2004-01-10T05:53:29Z cvs2svn cvs2svn@FreeBSD.org 2004-01-10T05:53:29Z urn:sha1:58c9ff44c8041f394c663cb9640e9b77fe07bb13 'RELENG_5_2_0_RELEASE'. This commit was manufactured to restore the state of the 5.2-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs. Drop the driver lock around calls to if_input to avoid a LOR when 2003-11-14T19:00:32Z Sam Leffler sam@FreeBSD.org 2003-11-14T19:00:32Z urn:sha1:5120abbfb44aea8edaca3311a60e73429dc71942 the packets are immediately returned for sending (e.g. when bridging or packet forwarding). There are more efficient ways to do this but for now use the least intrusive approach. Reviewed by: imp, rwatson Replace the if_name and if_unit members of struct ifnet with new members 2003-10-31T18:32:15Z Brooks Davis brooks@FreeBSD.org 2003-10-31T18:32:15Z urn:sha1:9bf40ede4a299f315bc4b0ae5329631b8c7dc271 if_xname, if_dname, and if_dunit. if_xname is the name of the interface and if_dname/unit are the driver name and instance. This change paves the way for interface renaming and enhanced pseudo device creation and configuration symantics. Approved By: re (in principle) Reviewed By: njl, imp Tested On: i386, amd64, sparc64 Obtained From: NetBSD (if_xname) Xircom Wireless Ethernet card is a rebadged Cisco 340, but with a 2003-10-08T01:20:00Z Warner Losh imp@FreeBSD.org 2003-10-08T01:20:00Z urn:sha1:146143aa369ca0890b807e8fceba66bdea7f9687 different vendor id/product id. Submitted by: Keith Davis Use PCIR_BAR(x) instead of PCIR_MAPS. 2003-09-02T17:30:40Z John Baldwin jhb@FreeBSD.org 2003-09-02T17:30:40Z urn:sha1:e27951b29c565206b57c8cdbc2ac344485c2f4f5 Glanced over by: imp, gibbs Tested by: i386 LINT Use __FBSDID(). 2003-08-24T17:55:58Z David E. O'Brien obrien@FreeBSD.org 2003-08-24T17:55:58Z urn:sha1:aad970f1fee9a2a3e5a0f880be9b87c6193b3bd1 Also some minor style cleanups. Prefer new location of pci include files (which have only been in the 2003-08-22T05:54:52Z Warner Losh imp@FreeBSD.org 2003-08-22T05:54:52Z urn:sha1:4fbd232c8640bb1d58dca36e50df7c1c8eb4ca72 tree for two or more years now), except in a few places where there's code to be compatible with older versions of FreeBSD. Fix panic from having multiple locks held when updating firmware. AN_LOCK 2003-08-20T05:52:48Z Doug Ambrisko ambrisko@FreeBSD.org 2003-08-20T05:52:48Z urn:sha1:50b09b375f18677c1c464645e0f2a7b378bdc8c0 was asserted during a tsleep resulting in a panic in tsleep. - Add support for Cisco latest firmware RID sizes that supports 25 SSIDs! 2003-08-20T03:46:05Z Doug Ambrisko ambrisko@FreeBSD.org 2003-08-20T03:46:05Z urn:sha1:e8ef0c292359b4bdd013ee3f182245bfcf1b9cfa - Fix up TX speed changes. - Make mpi-350 cards sort-of work with new firmware. It RXs okay but TXs only work for about 14 packets then fails to get an interrupt. The TX watchdog fires. It has been reported that my hack for now doesn't break cards with the older firmware. It appears my card has lost the ability to RX or TX at all but other peoples cards work. I assume it got damaged in tansport. MFC: 1 week. Mega busdma API commit. 2003-07-01T15:52:06Z Scott Long scottl@FreeBSD.org 2003-07-01T15:52:06Z urn:sha1:f6b1c44d1f70d5f298b911f2c1dcd802b0d11339 Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma. At the moment, this is used for the asynchronous busdma_swi and callback mechanism. Two lockfunc implementations are provided: busdma_lock_mutex() performs standard mutex operations on the mutex that is specified from lockfuncarg. dftl_lock() is a panic implementation and is defaulted to when NULL, NULL are passed to bus_dma_tag_create(). The only time that NULL, NULL should ever be used is when the driver ensures that bus_dmamap_load() will not be deferred. Drivers that do not provide their own locking can pass busdma_lock_mutex,&Giant args in order to preserve the former behaviour. sparc64 and powerpc do not provide real busdma_swi functions, so this is largely a noop on those platforms. The busdma_swi on is64 is not properly locked yet, so warnings will be emitted on this platform when busdma callback deferrals happen. If anyone gets panics or warnings from dflt_lock() being called, please let me know right away. Reviewed by: tmm, gibbs