From owner-freebsd-alpha Sat Oct 24 16:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13723 for freebsd-alpha-outgoing; Sat, 24 Oct 1998 16:01:59 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13718 for ; Sat, 24 Oct 1998 16:01:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA28799; Sat, 24 Oct 1998 16:05:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810242305.QAA28799@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas Valentino Crimi cc: mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: PCI mapping error In-reply-to: Your message of "Sat, 24 Oct 1998 18:12:32 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 16:05:52 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Excerpts from mail: 24-Oct-98 Re: PCI mapping error by Matthew > Jacob@feral.com > > > >Which platform this is would be helpful. > > I've been working on an AlphaStation 200 4/233. On the PCI bus are > also ncr and de drivers, which are working just fine. Whoa, hold it right there. What vintage is your kernel? I have a 4/233 here that's seeing the "no PCI interrupt" symptoms with the onboard ethernet, so anything that will help narrow this down would be a benefit. > To answer one of Mike Smith's questions, va and pa are both set to > 0x88000000, I also double checked the mem-map register on the card at > one point. I'm going to be grabbing a PC with PCI support later on > tonight and see what pops up. Ok. That looks reasonable. > Oh, another note. Before I tried out the read/write functions, I > tried using direct memory access, this paniced the kernel: > manual retype: > > fatal kernel trap: > > trap entry = 0x2 (memory management fault) > a0 = 88400000 > a1 = 0x1 > a2 = 0x1 > ... > > If this is a more telling than read/write, I'll do a full register > dump and whatever else may help (show map gives another fault, unaligned > access) The point here is that I think you should be using the bus to map the aperture for you; you need talk to Doug about this. > On a note, this card worked under AlphaLinux-XWindows before I got to > thinking it should do more than just be an X display. I'm sure the card works; there's no reason to expect it not to. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message