Re: Netgear MA401 pccard support? SOLVED
Not really solved but it works for me now. The bus memory allocation doesn't work. Both my pcic0 and fxp0 on pci2 got the same memory area, so I changed CARDBUS_SYS_RES_MEMORY_START (sys/pccard/pcic_pci.c) to a value that seemed to be free after looking thru dmesg after boot -v. In my case 0xd0208000 was good. Is it a bug? -- Mauritz Sundell, [EMAIL PROTECTED] - Original Message - From: Mauritz Sundell [EMAIL PROTECTED] To: M. Warner Losh [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, July 22, 2002 11:45 PM Subject: Re: Netgear MA401 pccard support? I still haven't got my Netgear MA401 working on my Compaq Evo N160 laptop using FreeBSD-5.0 but it works using FreeBSD-4.6. Now I wonder isn't it wrong that both pcic0 and fxp0 using the same memory area 0xd020? In 4.6 the pcic0 get 0x4400 (4.6-RELEASE) resp. 0x8800 (4.6-STABLE). Any ideas? I've tested patches, hints and kerneloptions found in other threads but nothing makes any difference. dmesg for 5.0-DP1 and 5.0-CURRENT (cvsuped several times from 27 june until today): pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcib2: device pcic0 requested decoded memory range 0xd020-0xd02f pccard0: PC Card bus (classic) on pcic0 pcic0: PCI Memory allocated: 0xd020 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 dmesg for 4.6-RELEASE: pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcic0: PCI Memory allocated: 0x4400 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card bus (classic) on pcic0 fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 dmesg for 4.6-CURRENT (cvsuped today): pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcic0: PCI Memory allocated: 0x8800 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card bus (classic) on pcic0 fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 -- Mauritz Sundell, [EMAIL PROTECTED] - Original Message - From: Mauritz Sundell [EMAIL PROTECTED] To: M. Warner Losh [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 10, 2002 11:02 AM Subject: Re: Netgear MA401 pccard support? - Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 10, 2002 7:05 AM Subject: Re: Netgear MA401 pccard support? In message: 046701c2279c$2878c4e0$0e81a8c0@gilgamesh Mauritz Sundell [EMAIL PROTECTED] writes: : I cant get my NETGEAR MA401 network pccard to work in CURRENT. Bummer. It works for other people. : I have a Compaq Evo N160 laptop. What kind of pccard/cardbus bridge do you have? TI1410 PCI-CardBus Bridge : Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated : This does not work at all at the moment. That's just for older ISA devices. Most PCI devices work great. : It did work under 4.6-RELEASE ( I have not tried 4.6-STABLE). Maybe sending a dmesg from -stable would help. Alternatively, you should be able to run OLDCARD on -current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Netgear MA401 pccard support? SOLVED
In message: 020601c23410$cdced300$0c81a8c0@gilgamesh Mauritz Sundell [EMAIL PROTECTED] writes: : Not really solved but it works for me now. : : The bus memory allocation doesn't work. : Both my pcic0 and fxp0 on pci2 got the same memory area, so I : changed CARDBUS_SYS_RES_MEMORY_START : (sys/pccard/pcic_pci.c) to a value that seemed to be free after : looking thru dmesg after boot -v. In my case 0xd0208000 was good. : : Is it a bug? Yes. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Netgear MA401 pccard support?
I still haven't got my Netgear MA401 working on my Compaq Evo N160 laptop using FreeBSD-5.0 but it works using FreeBSD-4.6. Now I wonder isn't it wrong that both pcic0 and fxp0 using the same memory area 0xd020? In 4.6 the pcic0 get 0x4400 (4.6-RELEASE) resp. 0x8800 (4.6-STABLE). Any ideas? I've tested patches, hints and kerneloptions found in other threads but nothing makes any difference. dmesg for 5.0-DP1 and 5.0-CURRENT (cvsuped several times from 27 june until today): pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcib2: device pcic0 requested decoded memory range 0xd020-0xd02f pccard0: PC Card bus (classic) on pcic0 pcic0: PCI Memory allocated: 0xd020 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 dmesg for 4.6-RELEASE: pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcic0: PCI Memory allocated: 0x4400 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card bus (classic) on pcic0 fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 dmesg for 4.6-CURRENT (cvsuped today): pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcic0: PCI Memory allocated: 0x8800 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card bus (classic) on pcic0 fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 -- Mauritz Sundell, [EMAIL PROTECTED] - Original Message - From: Mauritz Sundell [EMAIL PROTECTED] To: M. Warner Losh [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 10, 2002 11:02 AM Subject: Re: Netgear MA401 pccard support? - Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 10, 2002 7:05 AM Subject: Re: Netgear MA401 pccard support? In message: 046701c2279c$2878c4e0$0e81a8c0@gilgamesh Mauritz Sundell [EMAIL PROTECTED] writes: : I cant get my NETGEAR MA401 network pccard to work in CURRENT. Bummer. It works for other people. : I have a Compaq Evo N160 laptop. What kind of pccard/cardbus bridge do you have? TI1410 PCI-CardBus Bridge : Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated : This does not work at all at the moment. That's just for older ISA devices. Most PCI devices work great. : It did work under 4.6-RELEASE ( I have not tried 4.6-STABLE). Maybe sending a dmesg from -stable would help. Alternatively, you should be able to run OLDCARD on -current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Netgear MA401 pccard support?
- Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 10, 2002 7:05 AM Subject: Re: Netgear MA401 pccard support? In message: 046701c2279c$2878c4e0$0e81a8c0@gilgamesh Mauritz Sundell [EMAIL PROTECTED] writes: : I cant get my NETGEAR MA401 network pccard to work in CURRENT. Bummer. It works for other people. : I have a Compaq Evo N160 laptop. What kind of pccard/cardbus bridge do you have? TI1410 PCI-CardBus Bridge : Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated : This does not work at all at the moment. That's just for older ISA devices. Most PCI devices work great. : It did work under 4.6-RELEASE ( I have not tried 4.6-STABLE). Maybe sending a dmesg from -stable would help. Alternatively, you should be able to run OLDCARD on -current. Warner I hope my dmesgs only come once, I have tried to send them twice:) Here they are inline (with some badly placed newlines): (I have not tried STABLE) Below are: ** 4.6-RELEASE: dmesg * *** 5.0-NEWCARD: dmesg 5.0-OLDCARD: dmesg (boot -v) *** 5.0-OLDCARD: dmesg 5.0-OLDCARD: pciconf -lv *** ** 4.6-RELEASE: dmesg * Copyright (c) 1992-2002 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.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (999.16-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,MMX,FXSR,SSE real memory = 133562368 (130432K bytes) avail memory = 125050880 (122120K bytes) Preloaded elf kernel kernel at 0xc04d. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00fdf10 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: PCI to PCI bridge (vendor=8086 device=3576) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: ATI model 4c59 graphics accelerator at 0.0 irq 11 uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1840-0x185f irq 11 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) 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 82801CA/CAM (ICH3) USB controller USB-B port 0x1860-0x187f irq 10 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) 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 pcib2: PCI to PCI bridge (vendor=8086 device=2448) at device 30.0 on pci0 pci2: PCI bus on pcib2 pci2: unknown card (vendor=0x14f1, dev=0x2f00) at 4.0 pci2: unknown card (vendor=0x104c, dev=0x8023) at 5.0 pcic0: TI PCI-1410 PCI-CardBus Bridge irq 10 at device 6.0 on pci2 pcic0: PCI Memory allocated: 0x4400 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card bus (classic) on pcic0 fxp0: Intel Pro/100 Ethernet port 0x3000-0x303f mem 0xd020-0xd0200fff irq 9 at device 8.0 on pci2 fxp0: Ethernet address 00:02:a5:9c:51:e3 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=8086 device=248c) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 ATA100 controller port 0x1800-0x180f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 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=0x2483) at 31.3 irq 5 pci0: unknown card (vendor=0x8086, dev=0x2485) at 31.5 irq 5 orm0: Option ROMs at iomem 0xc-0xcdfff,0xdb000-0xdbfff,0xdc000-0xd on isa0 fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 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 Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 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 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/8 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ata1-slave: ATA
Netgear MA401 pccard support?
Hi I cant get my NETGEAR MA401 network pccard to work in CURRENT. I have a Compaq Evo N160 laptop. Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated This does not work at all at the moment. Does this mean that there is no way I can get my pccard to work in CURRENT, either using OLDCARD or NEWCARD? Has it ever worked in CURRENT? It did work under 4.6-RELEASE ( I have not tried 4.6-STABLE). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Netgear MA401 pccard support?
In message: 046701c2279c$2878c4e0$0e81a8c0@gilgamesh Mauritz Sundell [EMAIL PROTECTED] writes: : I cant get my NETGEAR MA401 network pccard to work in CURRENT. Bummer. It works for other people. : I have a Compaq Evo N160 laptop. What kind of pccard/cardbus bridge do you have? : Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated : This does not work at all at the moment. That's just for older ISA devices. Most PCI devices work great. : It did work under 4.6-RELEASE ( I have not tried 4.6-STABLE). Maybe sending a dmesg from -stable would help. Alternatively, you should be able to run OLDCARD on -current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PCCARD support
Where are we with getting PCCARD support, such as the 3COM MegaHertz (3CCFEM556 B) card in the mainstream distribution? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD support
On Sun, 23 Jan 2000, Forrest Aldrich wrote: Where are we with getting PCCARD support, such as the 3COM MegaHertz (3CCFEM556 B) card in the mainstream distribution? Can you use the output of 'pccardc dumpcis' to construct an entry for /etc/pccard.conf and try the 'ep' driver to see if it will work? I suspect it will. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD support
In message [EMAIL PROTECTED] Forrest Aldrich writes: : Where are we with getting PCCARD support, such as the : 3COM MegaHertz (3CCFEM556 B) card in the mainstream : distribution? Should be there already. If it isn't, then contact me and we'll talk. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD support
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Sun, 23 Jan 2000, Forrest Aldrich wrote: : Where are we with getting PCCARD support, such as the 3COM MegaHertz : (3CCFEM556 B) card in the mainstream distribution? : : Can you use the output of 'pccardc dumpcis' to construct an entry for : /etc/pccard.conf and try the 'ep' driver to see if it will work? : : I suspect it will. I suspect it will too, unless the 'B' changed the id number, in which case if_ep_pccard.c may need to be tweaked. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Pccard support still works with newbus, right?
I'm currently working on a driver for the Lucent WaveLAN/IEEE 802.11 PCMCIA adapter, as part of a project for the COMET lab people here at Columbia. Lucent has a PCMCIA and an ISA version of this adapter, however the ISA version is really just a PCMCIA card fitted into an add-in PCMCIA controller card that mounts in an ISA slot (i.e. something that lets you plug PCMCIA devices into a desktop host that doesn't have any built-in PCMCIA slots). This adapter card has a Vadem 469 chip on it which, fortunately, is supported by our current pccard code. The system I'm testing on is running 3.0-RELEASE and I'm reasonably confident my code will work with 3.1-RELEASE too. As it stands now, I can get the card probed and attached when I start pccardd, and everything seems peachy. What I need to know is if anybody has tested the pccard support in 4.0-CURRENT now that all the newbus stuff has been rolled in. If the pccard support for the x86 still works under 'emulation' using an ISA device shim, then that's fine. If not... well, then I suppoose _I'm_ the one who's going to end up testing it. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Pccard support still works with newbus, right?
On Sun, 18 Apr 1999, Bill Paul wrote: I'm currently working on a driver for the Lucent WaveLAN/IEEE 802.11 PCMCIA adapter, as part of a project for the COMET lab people here at Columbia. Lucent has a PCMCIA and an ISA version of this adapter, however the ISA version is really just a PCMCIA card fitted into an add-in PCMCIA controller card that mounts in an ISA slot (i.e. something that lets you plug PCMCIA devices into a desktop host that doesn't have any built-in PCMCIA slots). This adapter card has a Vadem 469 chip on it which, fortunately, is supported by our current pccard code. The system I'm testing on is running 3.0-RELEASE and I'm reasonably confident my code will work with 3.1-RELEASE too. As it stands now, I can get the card probed and attached when I start pccardd, and everything seems peachy. What I need to know is if anybody has tested the pccard support in 4.0-CURRENT now that all the newbus stuff has been rolled in. If the pccard support for the x86 still works under 'emulation' using an ISA device shim, then that's fine. If not... well, then I suppoose _I'm_ the one who's going to end up testing it. I think it works as well it did before but I haven't personally tested it. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Pccard support still works with newbus, right?
In message pine.bsf.4.05.9904181854010.85882-100...@herring.nlsystems.com Doug Rabson writes: : I think it works as well it did before but I haven't personally tested it. I have personally tested my new ata-flash support as well as my 3C589D card, both with a PC-Card Vadem 365 based ISA on my PPro 200. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message