Re: USB2 device
From: Michael E. Mercer (mmercer_at_nc.rr.com)
Date: 03/30/04
- Previous message: Julian Elischer: "Re: USB2 device"
- In reply to: Julian Elischer: "Re: USB2 device"
- Next in thread: Julian Elischer: "Re: USB2 device"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Julian Elischer <julian@elischer.org> Date: Mon, 29 Mar 2004 18:54:17 -0500
Julian,
Yes. How do I know I got cam loaded? There is no option/device for cam
in LINT.
Attached you will find my kernel config file...
> usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb4:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
(0x8086)(0x0000), rev 1.00
port 1 addr 2: high speed, self powered, config 1, product
0x0058(0x0058), NEC(0x0409), rev 1.00
port 2 powered
port 3 powered
port 4 powered
port 5 powered
port 6 powered
port 7 powered
port 8 powered
On Mon, 2004-03-29 at 18:51, Julian Elischer wrote:
> plug it in and then run usbdevs -v
>
> Let's see what it sees.
>
> (do you have cam and 'da' and umass all loaded?)
>
>
>
>
> On Mon, 29 Mar 2004, Michael E. Mercer wrote:
>
> > Julian,
> >
> > I built the kernel with ehci, it boots and I see another hub using ehci.
> > However when I plug in my JumpDrive, it does not get added.
> >
> > Michael Mercer
> >
> > Copyright (c) 1992-2003 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > The Regents of the University of California. All rights reserved.
> > FreeBSD 4.9-STABLE #0: Mon Mar 29 18:19:39 EST 2004
> > mmercer@fast.mmercer.com:/usr/obj/usr/src/sys/g49
> > Timecounter "i8254" frequency 1193182 Hz
> > CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3006.83-MHz 686-class CPU)
> > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
> >
> > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> > Hyperthreading: 2 logical CPUs
> > real memory = 1072889856 (1047744K bytes)
> > avail memory = 1039880192 (1015508K bytes)
> > Programming 24 pins in IOAPIC #0
> > IOAPIC #0 intpin 2 -> irq 0
> > IOAPIC #0 intpin 17 -> irq 10
> > IOAPIC #0 intpin 18 -> irq 5
> > IOAPIC #0 intpin 19 -> irq 11
> > FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
> > cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000
> > cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000
> > io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec00000
> > Preloaded elf kernel "kernel" at 0xc042b000.
> > Warning: Pentium 4 CPU: PSE disabled
> > Pentium Pro MTRR support enabled
> > md0: Malloc disk
> > Using $PIR table, 12 entries at 0xc00f50e0
> > apm0: <APM BIOS> on motherboard
> > apm0: found APM BIOS v1.2, connected at v1.2
> > npx0: <math processor> on motherboard
> > npx0: INT 16 interface
> > pcib0: <Host to PCI bridge> on motherboard
> > pci0: <PCI bus> on pcib0
> > agp0: <Intel 82875P host to AGP bridge> mem 0xd0000000-0xdfffffff at
> > device 0.0 on pci0
> > pcib1: <PCI to PCI bridge (vendor=8086 device=2579)> at device 1.0 on
> > pci0
> > pci1: <PCI bus> on pcib1
> > pci1: <NVidia model 0322 graphics accelerator> at 0.0 irq 10
> > pcib2: <PCI to PCI bridge (vendor=8086 device=257b)> at device 3.0 on
> > pci0
> > pci2: <PCI bus> on pcib2
> > em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port
> > 0xcf80-0xcf9f mem 0xfe9e0000-0xfe9fffff irq 5 at device 1.0 on pci2
> > em0: Speed:N/A Duplex:N/A
> > uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0xef00-0xef1f
> > irq 10 at device 29.0 on pci0
> > usb0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
> > usb0: USB revision 1.0
> > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0xef20-0xef3f
> > irq 11 at device 29.1 on pci0
> > usb1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
> > usb1: USB revision 1.0
> > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub1: 2 ports with 2 removable, self powered
> > uhci2: <Intel 82801EB (ICH5) USB controller USB-C> port 0xef40-0xef5f
> > irq 5 at device 29.2 on pci0
> > usb2: <Intel 82801EB (ICH5) USB controller USB-C> on uhci2
> > usb2: USB revision 1.0
> > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub2: 2 ports with 2 removable, self powered
> > uhci3: <Intel 82801EB (ICH5) USB controller USB-D> port 0xef80-0xef9f
> > irq 10 at device 29.3 on pci0
> > usb3: <Intel 82801EB (ICH5) USB controller USB-D> on uhci3
> > usb3: USB revision 1.0
> > uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub3: 2 ports with 2 removable, self powered
> > ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfebffc00-0xfebfffff irq
> > 11 at device 29.7 on pci0
> > ehci_pci_attach: companion usb0
> > ehci_pci_attach: companion usb1
> > ehci_pci_attach: companion usb2
> > ehci_pci_attach: companion usb3
> > usb4: EHCI version 1.0
> > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
> > usb4: <EHCI (generic) USB 2.0 controller> on ehci0
> > usb4: USB revision 2.0
> > uhub4: (0x8086) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
> > uhub4: 8 ports with 8 removable, self powered
> > uhub5: NEC Corporation USB2.0 Hub Controller, class 9/0, rev 2.00/1.00,
> > addr 2
> > uhub5: 4 ports with 4 removable, self powered
> > uhub5: cannot open interrupt pipe
> > device_probe_and_attach: uhub5 attach returned 6
> > uhub5: NEC Corporation USB2.0 Hub Controller, class 9/0, rev 2.00/1.00,
> > addr 2
> > uhub5: 4 ports with 4 removable, self powered
> > uhub5: cannot open interrupt pipe
> > device_probe_and_attach: uhub5 attach returned 6
> > pcib3: <Intel 82801BA/BAM (ICH2) Hub to PCI bridge> at device 30.0 on
> > pci0
> > pci3: <PCI bus> on pcib3
> > fwohci0: <VIA VT6306> port 0xdc00-0xdc7f mem 0xfeaff800-0xfeafffff irq 5
> > at device 3.0 on pci3
> > fwohci0: OHCI version 1.0 (ROM=1)
> > fwohci0: No. of Isochronous channel is 8.
> > fwohci0: EUI64 00:e0:18:00:00:58:2a:e6
> > fwohci0: Phy 1394a available S400, 3 ports.
> > fwohci0: Link S400, max_rec 2048 bytes.
> > firewire0: <IEEE1394(FireWire) bus> on fwohci0
> > fwe0: <Ethernet over FireWire> on firewire0
> > if_fwe0: Fake Ethernet address: 02:e0:18:58:2a:e6
> > fwohci0: Initiate bus reset
> > fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
> > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
> > firewire0: bus manager 0 (me)
> > isab0: <PCI to ISA bridge (vendor=8086 device=24d0)> at device 31.0 on
> > pci0
> > isa0: <ISA bus> on isab0
> > atapci0: <Intel ICH5 ATA100 controller> port
> > 0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > pci0: <unknown card> (vendor=0x8086, dev=0x24d3) at 31.3 irq 10
> > pcm0: <Intel ICH5 (82801EB)> port 0xee80-0xeebf,0xe800-0xe8ff mem
> > 0xfebff400-0xfebff4ff,0xfebff800-0xfebff9ff irq 10 at device 31.5 on
> > pci0
> > pcm0: <Analog Devices AD1985 AC97 Codec>
> > orm0: <Option ROM> at iomem 0xc0000-0xcefff on isa0
> > pmtimer0 on isa0
> > fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,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,0x64 on isa0
> > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> > kbd0 at atkbd0
> > psm0: <PS/2 Mouse> irq 12 on atkbdc0
> > psm0: model IntelliMouse Explorer, device ID 4
> > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
> > isa0
> > sc0: <System console> at flags 0x100 on isa0
> > sc0: VGA <16 virtual consoles, flags=0x300>
> > sio0: configured irq 4 not in bitmap of probed irqs 0
> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> > sio0: type 16550A
> > sio1: configured irq 3 not in bitmap of probed irqs 0
> > sio1 at port 0x2f8-0x2ff irq 3 on isa0
> > sio1: type 16550A
> > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> > ppc0: FIFO with 16/16/9 bytes threshold
> > plip0: <PLIP network interface> on ppbus0
> > lpt0: <Printer> on ppbus0
> > lpt0: Interrupt-driven port
> > ppi0: <Parallel I/O> on ppbus0
> > APIC_IO: Testing 8254 interrupt delivery
> > APIC_IO: routing 8254 via IOAPIC #0 intpin 2
> > SMP: AP CPU #1 Launched!
> > ad0: 39205MB <Maxtor 6E040L0> [79656/16/63] at ata0-master UDMA100
> > ad3: 194481MB <Maxtor 6Y200P0> [395136/16/63] at ata1-slave UDMA100
> > acd0: DVD-R <OPTORITEDVD RW DD0203> at ata1-master PIO4
> > Mounting root from ufs:/dev/ad3s1a
> > em0: Link is up 100 Mbps Full Duplex
> > em0: Link is up 100 Mbps Full Duplex
> >
> >
> >
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
#
# g4.9 -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ./LINT configuration file. If you are
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.56 2003/12/19 22:52:44 jhb Exp $
machine i386
cpu I686_CPU
ident g49
maxusers 512
#####################################################################
# SMP OPTIONS:
#
# SMP enables building of a Symmetric MultiProcessor Kernel.
# APIC_IO enables the use of the IO APIC for Symmetric I/O.
#
# Notes:
#
# An SMP kernel will ONLY run on an Intel MP spec. qualified motherboard.
#
# Be sure to disable 'cpu I386_CPU' && 'cpu I486_CPU' for SMP kernels.
#
# Check the 'Rogue SMP hardware' section to see if additional options
# are required by your hardware.
#
# Mandatory:
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O
#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
options MATH_EMULATE #Support for x87 emulation
options INET #InterNETworking
options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT #FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big directories
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT #NFS usable as root device, NFS required
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660 required
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI
options UCONSOLE #Allow users to grab the console
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B #Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM #Rate limit bad replies
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
device isa
device eisa
device pci
device pcm
# Floppy drives
device fdc0 at isa? port IO_FD1 irq 6 drq 2
device fd0 at fdc0 drive 0
device fd1 at fdc0 drive 1
#
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc0 at isa? port IO_KBD
device atkbd0 at atkbdc? irq 1 flags 0x1
device psm0 at atkbdc? irq 12
device vga0 at isa?
# splash screen/screen saver
pseudo-device splash
# syscons is the default console driver, resembling an SCO console
device sc0 at isa? flags 0x100
# Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver
#device vt0 at isa?
options XSERVER # support for X server on a vt console
options FAT_CURSOR # start with block cursor
device agp # support several AGP chipsets
# Floating point support - do not disable.
device npx0 at nexus? port IO_NPX irq 13
# Power management support (see LINT for more options)
device apm0 # Advanced Power Management
# Serial (COM) ports
device sio0 at isa? port IO_COM1 flags 0x10 irq 4
device sio1 at isa? port IO_COM2 irq 3
device sio2 at isa? disable port IO_COM3 irq 5
device sio3 at isa? disable port IO_COM4 irq 9
# Parallel port
device ppc0 at isa? irq 7
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
#device vpo # Requires scbus and da
device scbus #base SCSI code
device ch #SCSI media changers
device da #SCSI direct access devices (aka disks)
device pass
# PCI Ethernet NICs.
device em # Intel PRO/1000 adapter Gigabit Ethernet Card (``Wiseman'')
# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
# Pseudo devices - the number indicates how many units to allocate.
pseudo-device loop # Network loopback
pseudo-device ether # Ethernet support
pseudo-device sl 1 # Kernel SLIP
pseudo-device ppp 1 # Kernel PPP
pseudo-device tun # Packet tunnel.
pseudo-device pty # Pseudo-ttys (telnet etc)
pseudo-device md # Memory "disks"
pseudo-device gif # IPv6 and IPv4 tunneling
pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation)
# The `bpf' pseudo-device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
pseudo-device bpf #Berkeley packet filter
# USB support
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface
device usb # USB Bus (required)
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device ums # Mouse
device uscanner # Scanners
device urio # Diamond Rio MP3 Player
# USB Ethernet, requires mii
device aue # ADMtek USB ethernet
device cue # CATC USB ethernet
device kue # Kawasaki LSI USB ethernet
# Fm Radio
device ufm
# USB Iomega Zip 100 Drive (Requires scbus and da)
device umass
# USB modem support
device umodem
# USB com devices
device ucom
device uplcom
device uvscom
device uvisor
device uftdi
# FireWire support
device firewire # FireWire bus code
device fwe # Ethernet over FireWire (non-standard!)
################# ADDED 20040316
#
# Certain applications can grow to be larger than the 128M limit
# that FreeBSD initially imposes. Below are some options to
# allow that limit to grow to 256MB, and can be increased further
# with changing the parameters. MAXDSIZ is the maximum that the
# limit can be set to, and the DFLDSIZ is the default value for
# the limit. You might want to set the default lower than the
# max, and explicitly set the maximum with a shell command for processes
# that regularly exceed the limit like INND.
#
options MAXDSIZ="(1024*1024*1024)"
options MAXSSIZ="(512*1024*1024)"
options DFLDSIZ="(512*1024*1024)"
#
# MAXMEM specifies the amount of RAM on the machine; if this is not
# specified, FreeBSD will first read the amount of memory from the CMOS
# RAM, so the amount of memory will initially be limited to 64MB or 16MB
# depending on the BIOS. If the BIOS reports 64MB, a memory probe will
# then attempt to detect the installed amount of RAM. If this probe
# fails to detect >64MB RAM you will have to use the MAXMEM option.
# The amount is in kilobytes, so for a machine with 128MB of RAM, it would
# be 131072 (128 * 1024).
#options MAXMEM="(1024*1024)"
options CPU_ENABLE_SSE
device apm
#
# Allow applications running in user space to control the Local Descriptor
# Table (LDT). This is required by some ports. Future versions of FreeBSD
# may require this option for some programs in the base system.
#
options USER_LDT #allow user-level control of i386 ldt
### mEm 20040316
### DO NOT USE PNPBIOS!!!!
### IT CAUSES THE KERNEL TO CRASH AT BOOT TIME!!!!
#####options PNPBIOS
#
# SMB bus
#
# System Management Bus support is provided by the 'smbus' device.
# Access to the SMBus device is via the 'smb' device (/dev/smb*),
# which is a child of the 'smbus' device.
#
# Supported devices:
# smb standard io through /dev/smb*
#
# Supported SMB interfaces:
# iicsmb I2C to SMB bridge with any iicbus interface
# bktr brooktree848 I2C hardware interface
# intpm Intel PIIX4 (82371AB, 82443MX) Power Management Unit
# alpm Acer Aladdin-IV/V/Pro2 Power Management Unit
# ichsmb Intel ICH SMBus controller chips (82801AA, 82801AB, 82801BA)
# viapm VIA VT82C586B,596,686A and VT8233 SMBus controllers
# amdpm AMD 756 Power Management Unit
#
device smbus # Bus support, required for smb below.
device intpm
device smb
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
- Previous message: Julian Elischer: "Re: USB2 device"
- In reply to: Julian Elischer: "Re: USB2 device"
- Next in thread: Julian Elischer: "Re: USB2 device"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
