From owner-freebsd-emulation@FreeBSD.ORG Tue May 2 04:28:38 2006 Return-Path: X-Original-To: freebsd-emulation@freebsd.org Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D599B16A402 for ; Tue, 2 May 2006 04:28:38 +0000 (UTC) (envelope-from garrison@mail.ru) Received: from umail.ru (umail.ru [195.34.32.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F9943D48 for ; Tue, 2 May 2006 04:28:37 +0000 (GMT) (envelope-from garrison@mail.ru) Received: from [85.140.126.221] (HELO skyserv) by umail.ru (CommuniGate Pro SMTP 4.2b6) with ESMTP-TLS id 665949643; Tue, 02 May 2006 08:28:36 +0400 Received: from localhost ([127.0.0.1]) by skyserv with esmtp (Exim 4.61) (envelope-from ) id 1FamV1-0000Qi-Ja; Tue, 02 May 2006 08:28:35 +0400 Message-ID: <4456DFF3.5080207@mail.ru> Date: Tue, 02 May 2006 08:28:35 +0400 From: Igor Kovalenko User-Agent: Mail/News 1.5 (X11/20060319) MIME-Version: 1.0 To: qemu-devel@nongnu.org, qemu-l@jelal.kn-bremen.de, freebsd-emulation@freebsd.org References: <20060427203718.GA15953@saturn.kn-bremen.de> <445241DE.9020909@mail.ru> <20060428221142.GA11504@saturn.kn-bremen.de> <44530C50.6040902@mail.ru> <20060430004646.GA70632@saturn.kn-bremen.de> In-Reply-To: <20060430004646.GA70632@saturn.kn-bremen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: playing with qemu's 8139 nic and FreeBSD (loopback mode missing?) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 04:28:38 -0000 Juergen Lock wrote: > > Thanks, that seems to get the rl driver going. Now to fix C+ mode > (re driver) change the #if 0 in my patch to #if 1... > Well actually that requires a bit more: implementing on-board timer. freebsd if_re.c driver loopback test sequence passes if packet is received AND timeout occur; the latter cannot happen because of missing timer support. Then, driver tries to set up on-board timer for various reasons and may not work without timer. -- Kind regards, Igor V. Kovalenko