From owner-freebsd-sparc64@FreeBSD.ORG Sun Aug 31 10:56:57 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA0F016A4BF for ; Sun, 31 Aug 2003 10:56:57 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id C580443FEC for ; Sun, 31 Aug 2003 10:56:56 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h7VHuuwO017325 for ; Sun, 31 Aug 2003 10:56:56 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h7VHup8a000889 for ; Sun, 31 Aug 2003 10:56:51 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h7VHupeQ000888 for sparc64@freebsd.org; Sun, 31 Aug 2003 10:56:51 -0700 (PDT) (envelope-from marcel) Date: Sun, 31 Aug 2003 10:56:51 -0700 From: Marcel Moolenaar To: sparc64@freebsd.org Message-ID: <20030831175651.GA858@dhcp01.pn.xcllnt.net> References: <20030829211641.GA628@athlon.pn.xcllnt.net> <20030831124536.GA679@timesink.dyndns.org> <20030831164510.GA570@dhcp01.pn.xcllnt.net> <20030831174015.GB679@timesink.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030831174015.GB679@timesink.dyndns.org> User-Agent: Mutt/1.5.4i Subject: Re: Q: resource range for SBus oddity X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2003 17:56:57 -0000 On Sun, Aug 31, 2003 at 07:40:15PM +0200, Thomas Moestl wrote: > > I assume this is just a firmware bug then; it is unlikely that there > is a factor by which we ought to multiply the sizes given in the > property, since for other devices they match exactly what is to be > expected by the documentation, and larger sizes would lead to > overlapping regions there. Ok, thanks. I know what to do now. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net