From owner-freebsd-sparc64@FreeBSD.ORG Mon Feb 23 18:15:36 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B096106566B for ; Mon, 23 Feb 2009 18:15:36 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 12A3D8FC08 for ; Mon, 23 Feb 2009 18:15:35 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n1NIFYuG006144; Mon, 23 Feb 2009 19:15:34 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n1NIFYnb006143; Mon, 23 Feb 2009 19:15:34 +0100 (CET) (envelope-from marius) Date: Mon, 23 Feb 2009 19:15:34 +0100 From: Marius Strobl To: John Baldwin Message-ID: <20090223181534.GB46006@alchemy.franken.de> References: <1233668470.1364.45.camel@main.lerwick.hopto.org> <499B5520.3040801@kasimir.com> <20090222170230.GB69979@alchemy.franken.de> <200902230905.23149.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902230905.23149.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: can anyone make available the whole usIII source tree from perforce please X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 18:15:36 -0000 On Mon, Feb 23, 2009 at 09:05:22AM -0500, John Baldwin wrote: > On Sunday 22 February 2009 12:02:30 pm Marius Strobl wrote: > > On Wed, Feb 18, 2009 at 01:24:00AM +0100, Florian Smeets wrote: > > > On 04.02.2009 15:16 Uhr, Craig Butler wrote: > > > >Hi Marius, > > > > > > > >Thanks for all your hard work and pointers so far. I have compiled and > > > >installed the new kernel (cas is statically compiled in). Unfortunately > > > >its panic'ing on boot with the following; > > > > > > > >cas0: at device 10.0 on pci0 > > > >panic: trap: memory address not aligned > > > >cpuid = 0 > > > >Uptime: 1s > > > > > > > > > > FWIW, i compiled a kernel with these changes and the cards probe fine. > > > > > > cas0: mem 0x2000000-0x21fffff at > > > device 0.0 on pci1 > > > miibus1: on cas0 > > > cas0: 16kB RX FIFO, 9kB TX FIFO > > > cas0: Ethernet address: 00:03:ba:XX:XX:XX > > > cas0: [ITHREAD] > > > cas1: mem 0x2400000-0x25fffff at > > > device 1.0 on pci1 > > > miibus2: on cas1 > > > cas1: 16kB RX FIFO, 9kB TX FIFO > > > cas1: Ethernet address: 00:03:ba:XX:XX:XX > > > cas1: [ITHREAD] > > > > > > I don't have a cable connected yet, as the machine is remote, but I'll > > > be sure to test it soon. > > > > > > > FYI, the above panic likely isn't a problem of cas(4) but > > arises from the fact that the resource of that NIC starts > > at 0 according to its BAR, which is somewhat uncommon but > > nevertheless should work yet seems to trigger a bug at > > some other level. > > The PCI bus driver assumes a BAR of 0 is an invalid resource. There are many > systems that use 0 to disable a BAR. I have no idea if "0" is a magic value > to disable an individual BAR in the PCI spec itself, however. > I'm aware of the former, my understanding of the pci(4) code is that it won't pre-allocate such a resource but modulo bugs treats it normally when a driver allocates it though. I've found no indication in the PCI specs that 0 would be a magic value here. It also matches what the firmware has assigned to the device according to the OFW device tree. If the 0 here actually indicates a disabled BAR than this isn't exactly obvious to me as there would be better means in OFW to disable a device... Marius