src-test2/sys/dev/bfe, branch release/7.0.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.0.0_cvs 2008-02-24T05:45:17Z This commit was manufactured by cvs2svn to create tag 2008-02-24T05:45:17Z cvs2svn cvs2svn@FreeBSD.org 2008-02-24T05:45:17Z urn:sha1:a9c219fa3cec18ef9f30edec6fa106bf0e2d423d 'RELENG_7_0_0_RELEASE'. This commit was manufactured to restore the state of the 7.0-RELEASE image. o break newbus api: add a new argument of type driver_filter_t to 2007-02-23T12:19:07Z Paolo Pisati piso@FreeBSD.org 2007-02-23T12:19:07Z urn:sha1:ef544f631226436ef590825881e7a28369df82f6 bus_setup_intr() o add an int return code to all fast handlers o retire INTR_FAST/IH_FAST For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current Reviewed by: many Approved by: re@ Add suspend/resume support. Unlike many other NIC drivers, 2006-11-20T23:30:07Z John Baldwin jhb@FreeBSD.org 2006-11-20T23:30:07Z urn:sha1:6daee769f4277fe356aee26fa3f0154b0a982b63 bfe_init_locked() wasn't sufficient to bring the chip back to life, it also required a call to bfe_chip_reset() during resume. Tested by: Stepan Zastupov +redchrom at gmail+ MFC after: 1 week Back out the BUS_DMA_ALLOCNOW change from rev 1.39. Scottl informed me that 2006-05-28T20:35:39Z Mike Silbersack silby@FreeBSD.org 2006-05-28T20:35:39Z urn:sha1:3981b687c0c813a54220d0bacc8eb3057dd6f3f0 it's unnecessary, as the TX/RX lists are static allocations. Re-revert back to rev 1.8: 2006-05-28T18:44:39Z Mike Silbersack silby@FreeBSD.org 2006-05-28T18:44:39Z urn:sha1:f99da8e0d891e8937f14dc315014203a06c4e1b1 - Reduce the number of RX and TX buffers bfe uses so that it does not use more bounce buffers than busdma is willing to allow it to use See if_bfe.c for comments on why this is now safe to do. 1. Make sure that the TX and RX descriptor rings are 4096 byte aligned. 2006-05-28T18:41:47Z Mike Silbersack silby@FreeBSD.org 2006-05-28T18:41:47Z urn:sha1:678d2a9a8cd913981b79f90ec47009d276b3495f Also use BUS_DMA_ALLOCNOW to be on the safe side. 2. Look for the Descriptor Error, and Descriptor Protocol Error flags from the card, and down the interface if we detect either. #1 (along with fixes to busdma) makes sure that this card works in all memory situations. Prior to this change, it was just luck that 512 count RX/TX lists were properly aligned. Now we can use any size of RX/TX lists and still have them properly aligned. #2 ensures that we don't get into an endless interrupt storm if busdma fails us. Descriptor Protocol Error would occur if we misaligned the TX/RX rings, and Descriptor Error would occur if we tried to give the card descriptors or rings with addresses > 1G. Trying to reinitialize the card isn't going to fix these errors, hence we don't try. Since DELAY() was moved, most <machine/clock.h> #includes have been 2006-05-16T14:37:58Z Poul-Henning Kamp phk@FreeBSD.org 2006-05-16T14:37:58Z urn:sha1:c40da00ca320a38816049edd21966bd4045b2303 unnecessary. Revert if_bfereg.h rev 1.8; restore the RX and TX list sizes to 511. 2006-05-11T17:39:06Z Mike Silbersack silby@FreeBSD.org 2006-05-11T17:39:06Z urn:sha1:5c5ac08992210fc3fe15b4a51675df30ff158bc7 Two users have reported problems due to the smaller list sizes. Fix three more bugs in bfe: 2006-05-04T07:41:01Z Mike Silbersack silby@FreeBSD.org 2006-05-04T07:41:01Z urn:sha1:5511c4d6dc41144ab0ca52af6f0fceb409603230 - Fix bfe_encap so that it will pass the address of the mbuf back up to its caller if/when it modifies it, as it does when doing a m_defrag on a mbuf chain. - Make sure to unload the dmamap for ALL fragments of a packet, not just the first - Use BUS_DMA_NOWAIT for all bus_dmamap_load calls so that the allocation of the map is not delayed - this driver is not set up to handle such delays. - Reduce the number of RX and TX buffers bfe uses so that it does not use more bounce buffers than busdma is willing to allow it to use With these changes, the driver now works properly for a user with a 2GB system, and it also works on my system when the acceptable address range is lowered to 128MB. Previously, both of these setups would act up after a few minutes of activity. Tweak the DMA limit from rev 1.33, it was off by one byte. 2006-04-28T05:38:12Z Mike Silbersack silby@FreeBSD.org 2006-04-28T05:38:12Z urn:sha1:981b2dea6b5753dcea91268049d4367c526726c8 Submitted by: scottl