From owner-freebsd-hackers Tue Apr 13 14:31:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 32499151C2 for ; Tue, 13 Apr 1999 14:31:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01257; Tue, 13 Apr 1999 14:27:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904132127.OAA01257@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Cc: hackers@freebsd.org Subject: Re: PCI burst determination In-reply-to: Your message of "Tue, 13 Apr 1999 09:21:20 EDT." <199904131427.KAA03942@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Apr 1999 14:27:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there a way to determine the max burst of the PCI bridge on the > MB for controller optimization? I dont see a fuction...is it stored > somewhere? PCI is arbitrated with a latency timer, so there is no maximum burst length per se. As for limitations in the bridge chipset, you're probably going to want to look up the documentation for the individual bridges. However, having said, that, as a general rule with PCI bursting "longer is better". -- \\ 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-hackers" in the body of the message