mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-19 10:53:58 +00:00
c3ed41584c
- probe for PHYs by checking the BMSR (phy status) register instead of the vendor ID register. - fix the autonegotiation routine so that it figures out the autonegotiated modes correctly. - add tweaks to support the Olicom OC-2326 now that I've actually had a chance to test one o Olicom appears to encode the ethernet address in the EEPROM in 16-bit chunks in network byte order. If we detect an Olicom card (based on the PCI vendor ID), byte-swap the station address accordingly. XXX The Linux driver does not do this. I find this odd since the README from the Linux driver indicates that patches to support the Olicom cards came from somebody at Olicom; you'd think if anyone would get that right, it'd be them. Regardless, I accepted the word of the disgnoatic program that came bundled with the card as gospel and fixed the attach routine to make the station address match what it says. o The version of the 2326 card that I got for testing is a strange beast: the card does not look like the picture on the box in which it was packed. For one thing, the picture shows what looks like an external NS 83840A PHY, but the actual card doesn't have one. The card has a TNETE100APCM chip, which appears to have not only the usual internal tlan 10Mbps PHY at MII address 32, but also a 10/100 PHY at MII address 0. Curiously, this PHY's vendor and device ID registers always return 0x0000. I suspect that this is a mutant version of the ThunderLAN chip with 100Mbps support. This combination behaves a little strangely and required the following changes: - The internal PHY has to be enabled in tl_softreset(). - The internal PHY doesn't seem to come to life after detecting the 100Mbps PHY unless it's reset twice. - If you want to use 100Mbps modes, you have to isolate the internal PHY. - If you want to use 10Mbps modes, you have to un-isolate the internal PHY. The latter two changes are handled at the end of tl_init(): if the PHY vendor ID is 0x0000 (which should not be possible if we have a real external PHY), then tl_init() forces the internal PHY's BMCR register to the proper values. |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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