ea9c501856
of associated mbuf clusters) in the RX ring from 4 to 16. On my really fast PI 400Mhz test machines, 4 descriptors (and associated mbuf clusters) is enough to achieve decent performance without any RX overruns. However, one person reported problems with the following scenario: - P90 system running FreeBSD with a 3c905B-TX adapter, slow IDE hard disk (Quantum Bigfoot?) - PII 266 with SCSI disks running LoseNT and also with a 3c905B-TX - Both machines connected together via crossover cable at 100Mbps full-duplex - LoseNT machine writing largs amounts of data (2.5 GB work of files each in the neighborhood of 1 to 2 MB in size) via samba to the FreeBSD machine In this case, the LoseNT machine is sending data very fast. Apparently there weren't any problems initially because the user was writing to one particular disk which was relatively fast, however after this disk filled up and the user started writing to the second slower disk, RX overruns would occur and sometimes the RX DMA engine would stall after a 100 to 500MB had been transfered. The xl_rxeof() handler is supposed to detect this condition and restart the upload engine; I'm not sure why it doesn't, unless interrupts are being lost and the rx handler isn't getting called. This is still an improvement over the Linux driver, which uses 32 descriptors in its receive ring. :) Problem reported by: Heiko Schaefer <hschaefer@fto.de> |
||
---|---|---|
.. | ||
aic7870.c | ||
brktree_reg.h | ||
brooktree848.c | ||
bt9xx.c | ||
cy_pci.c | ||
cy_pcireg.h | ||
dc21040reg.h | ||
dpt_pci.c | ||
dpt_pci.h | ||
ide_pci.c | ||
ide_pcireg.h | ||
if_de.c | ||
if_devar.h | ||
if_ed_p.c | ||
if_en_pci.c | ||
if_fpa.c | ||
if_fxp.c | ||
if_fxpreg.h | ||
if_fxpvar.h | ||
if_lnc_p.c | ||
if_sr_p.c | ||
if_tl.c | ||
if_tlreg.h | ||
if_tx.c | ||
if_vx_pci.c | ||
if_xl.c | ||
if_xlreg.h | ||
isp_pci.c | ||
locate.pl | ||
meteor_reg.h | ||
meteor.c | ||
ncr.c | ||
ncrreg.h | ||
pci_compat.c | ||
pci_ioctl.h | ||
pci.c | ||
pcic_p.c | ||
pcic_p.h | ||
pcireg.h | ||
pcisupport.c | ||
pcivar.h | ||
README.bt848 | ||
scsiiom.c | ||
simos.c | ||
simos.h | ||
smc83c170.h | ||
tek390.c | ||
tek390.h | ||
wdc_p.c | ||
xrpu.c |
------------------------------------------------------------------------------- Recent versions of 3.0-current have the bktr driver built in. Older versions of 3.0 and all versions of 2.2 need to have the driver files installed by hand: cp ioctl_bt848.h /sys/i386/include/ cp brktree_reg.h brooktree848.c /sys/pci/ In /sys/conf/files add: pci/brooktree848.c optional bktr device-driver ------------------------------------------------------------------------------- In all cases you will need to add the driver to your kernel: In your kernel configuration file: controller pci0 #if you already have this line don't add it. device bktr0 There is no need to specify DMA channels nor interrupts for this driver. ------------------------------------------------------------------------------- Finally you need to create nodes for the driver: Create a video device: mknod /dev/bktr0 c 92 0 Create a tuner device: mknod /dev/tuner0 c 92 16 ------------------------------------------------------------------------------- The code attempts to auto-probe code to detect card/tuner types. The detected card is printed in the dmesg as the driver is loaded. If this fails to detect the proper card you can override it in brooktree848.c: #define OVERRIDE_CARD <card type> where <card type> is one of: CARD_UNKNOWN CARD_MIRO CARD_HAUPPAUGE CARD_STB CARD_INTEL ------------------------------------------------------------------------------- This model now separates the "tuner control" items into a minor device: minor device layout: xxxxxxxx xxxT UUUU UUUU: the card (ie UNIT) identifier, 0 thru 15 T == 0: video device T == 1: tuner device Access your tuner ioctl thru your tuner device handle and anything which controls the video capture process thru the video device handle. Certain ioctl()s such as video source are available thru both devices. ------------------------------------------------------------------------------- If your tuner does not work properly or is not recognized properly try setting the tuner type via or card type: sysctl -w hw.bt848.card=<integer> current valid values are 0 to 5 inclusive sysctl -w hw.bt848.tuner=<integer> where integer is a value from 1 to 10 systcl -w hw.bt848.reverse_mute=<1 | 0> to reverse the mute function in the driver set variable to 1. The exact format of the sysctl bt848 variable is: unit << 8 | value unit identifies the pci bt848 board to be affected 0 is the first bt848 board, 1 is the second bt848 board. value denotes the integer value for tuners is a value from 0 to 10 for reversing the mute function of the tuner the value is 1 or 0. to find out all the bt848 variables: sysctl hw.bt848 ------------------------------------------------------------------------------- The bt848 driver consists of: src/sys/i386/include/ioctl_bt848.h src/sys/pci/brktree_reg.h src/sys/pci/brooktree848.c