Re: the pcm driver and the bktr device
For the record (just want to have a look at the new configuration and at possible differences), could you post a dmesg of the current config? Cheers, Nick Here it is... I'm not using the vortex right now, (I took it out until the driver is finished, and put in an old ISA ViBRA16X in it's place) Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Sep 5 10:41:41 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) avail memory = 127356928 (124372K bytes) Preloaded elf kernel "kernel" at 0xc029c000. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: VGA-compatible display device at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: UHCI USB controller irq 11 at device 7.2 on pci0 chip2: Intel 82371AB Power management controller at device 7.3 on pci0 pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 13.0 pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 15.0 bktr0: BrookTree 878 irq 9 at device 17.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only smbus0: System Management Bus on bti2c0 bktr0: Hauppauge Model 61291 D110 Hauppauge WinCast/TV, Philips NTSC tuner. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 17.1 irq 9 de0: Digital 21140A Fast Ethernet irq 10 at device 19.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus 0 vpo0: EPP 1.9 mode sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: SoundBlaster 16 4.16 isa_compat: didn't get drq for sbxvi sbxvi0 at port 0x drq 1 on isa0 isa_compat: didn't get ports for sbxvi isa_compat: didn't get drq for sbxvi snd0: SoundBlaster 16 4.16 WARNING: "snd" is usurping "snd"'s cdevsw[] sbmidi0 at port 0x330 on isa0 snd0: SoundBlaster MPU-401 WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: Yamaha OPL3 FM WARNING: "snd" is usurping "snd"'s cdevsw[] ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: Maxtor 90845D4/GAS54112 ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad0 Creating DISK wd0 ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: Maxtor 84320D4/NAVX1920 ATA-3 disk at ata0 as slave ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad1 Creating DISK wd1 ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: FUJITSU MPC3064AT/6020 ATA-3 disk at ata1 as master ad1: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad1 Creating DISK wd1 ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: FUJITSU MPC3064AT/6020 ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad2 Creating DISK wd2 atapi: piomode=4, dmamode=2, udmamode=-1 atapi: PIO transfer mode set acd0: CD-ROM 40X/AKU/U30 CDROM drive at ata1 as slave acd0: drive speed 0 - 6875KB/sec, 128KB cache
Re: the pcm driver and the bktr device
As in
diff -wu brooktree848.c.orig brooktree848.c
--- brooktree848.c.orig Sat Sep 4 14:38:14 1999
+++ brooktree848.c Sat Sep 4 14:38:19 1999
@@ -6865,9 +6865,6 @@
unsigned int rev = pci_get_revid(dev);
static int once;
- if (!once++)
- cdevsw_add(bktr_cdevsw);
-
switch (type) {
case BROOKTREE_848_PCI_ID:
if (rev == 0x12) device_set_desc(dev, "BrookTree 848A");
Attaching is difficult.
Nick
On Sat, 4 Sep 1999, Nick Hibma wrote:
cdevsw_add is called in devsw_module_handler and in bktr_probe. Patch
attached. It looks like the init in bktr_probe became superfluous in
revision 1.90 of brooktree848.c:
revision 1.90
date: 1999/08/23 20:59:12; author: phk; state: Exp; lines: +7 -20
Convert DEVFS hooks in (most) drivers to make_dev().
Diskslice/label code not yet handled.
Vinum, i4b, alpha, pc98 not dealt with (left to respective Maintainers)
Add the correct hook for devfs to kern_conf.c
The net result of this excercise is that a lot less files depends on
DEVFS,
and devtoname() gets more sensible output in many cases.
A few drivers had minor additional cleanups performed relating to cdevsw
registration.
A few drivers don't register a cdevsw{} anymore, but only use
make_dev().
..."
Nick
On Fri, 3 Sep 1999, Kenneth Culver wrote:
It seems I have the classic IRQ conflict going on here.
I have 4 devices that all seem to want the same irq. For some reason the
USB port, the pcm driver, the bktr driver, and one other thing (I havn't
figured out what) all want IRQ 11. The pcm driver is driving an aureal
vortex right now. I have never had this problem before, and even though
they are all sharing the same IRQ, they all work at the same time in
windows. I would like to know why they won't work in FreeBSD. Here is the
output from the dmesg command:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #5: Fri Sep 3 18:57:32 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/MYKERNEL
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x652 Stepping = 2
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR
real memory = 134152192 (131008K bytes)
avail memory = 127393792 (124408K bytes)
Preloaded elf kernel "kernel" at 0xc0293000.
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
apm0: APM BIOS on motherboard
apm: found APM BIOS v1.2, connected at v1.2
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
WARNING: "bktr" is usurping "bktr"'s cdevsw[]
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 0.0 on pci0
pci1: PCI bus on pcib1
vga-pci0: VGA-compatible display device at device 0.0 on pci1
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
chip1: UHCI USB controller irq 11 at device 7.2 on pci0
chip2: Intel 82371AB Power management controller at device 7.3 on pci0
pcm0: Aureal Vortex 8820 irq 11 at device 9.0 on pci0
pcm0: irq test failed
pcm0: codec timeout reading register 2 (fe7604)
pcm0: codec timeout reading register 26 (fe7604)
ac97: dac not ready
bktr0: BrookTree 878 irq 11 at device 13.0 on pci0
bktr0: could not map interrupt
device_probe_and_attach: bktr0 attach returned 6
pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 13.1 irq 11
de0: Digital 21140A Fast Ethernet irq 10 at device 15.0 on pci0
de0: 21140A [10-100Mb/s] pass 2.2
de0: address 00:c0:f0:1f:21:02
pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 17.0
pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 19.0
fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0: PLIP network interface on ppbus 0
lpt0: generic printer on ppbus 0
lpt0: Interrupt-driven port
ppi0: generic parallel i/o on ppbus 0
vpo0:
Re: the pcm driver and the bktr device
It seems I have the classic IRQ conflict going on here. I have 4 devices that all seem to want the same irq. For some reason the USB port, the pcm driver, the bktr driver, and one other thing (I havn't figured out what) all want IRQ 11. This is your BIOS' fault. You need to either move the devices around, or fiddle with your BIOS setup until it assigns separate IRQs to each device. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
