From owner-freebsd-hackers Fri Feb 26 7:18:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id CF18E14FA5 for ; Fri, 26 Feb 1999 07:18:34 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id KAA20037; Fri, 26 Feb 1999 10:19:46 -0500 (EST) Message-Id: <199902261519.KAA20037@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 26 Feb 1999 10:28:26 -0500 To: Ted Faber From: Dennis Subject: Re: PCI Card Failures in 3.1 Cc: hackers@freebsd.org, se@mi.uni-koeln.de In-Reply-To: <199902260201.SAA03524@boreas.isi.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:01 PM 2/25/99 -0800, you wrote: >-----BEGIN PGP SIGNED MESSAGE----- > > >Dennis wrote: >> >>Can anyone point me at info on what changed, specifically for pci devices, >>in 3.0 vs 2.2? A bullet list would help greatly. VM mapping? > >I'm having a similar problem (a PCI ethernet device that worked under >2.2.7 won't work under 3.0) and I think it might be due to the changes >in pci_map_port(). Under 2.2.7 there's some code in pci_map_port() >that apparently enables intermediate bridges, but I don't see the same >functionality in the pci_map_port in the PCI compatibility code. I've >sent some mail to Stefan about this, but he's apparently swamped. If >anyone else can take a look at the PCI code and confirm my diagnosis >and provide me a workaround or a patch, I'd really appreciate it. It >may also be causing you a problem, too. > >I'd patch it myself, but without a PCI spec, that code looks pretty >daunting... We had problems in 2.2 with PCI shared memory not working properly, but this is a much bigger problem. One or our PCI cards works, and the other doesnt for no apparent reason. The one that doesnt work is a bus master, and it cant seem to write to system memory. All of the registers read the correct values, so its either that the physical addresses arent right or the card cant access the memory. What card are you haveing problems with, and what are the symptoms? Does it detect the card? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message