From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 16 19:39:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AEA837B401; Wed, 16 Jul 2003 19:39:15 -0700 (PDT) Received: from mail.ludost.net (tonib-gw.customer.0rbitel.net [195.24.39.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 933AE43F85; Wed, 16 Jul 2003 19:39:13 -0700 (PDT) (envelope-from maav@bastun.net) Received: from SABBATH (ozzy.ddns.cablebg.net [217.18.240.240]) by mail.ludost.net (Postfix) with ESMTP id D7B214C691; Thu, 17 Jul 2003 05:38:58 +0300 (EEST) Message-ID: <000701c34c0c$8a6b4430$020aa8c0@SABBATH> From: "Boris Georgiev" To: "william paul" References: <200307160000.RAA22276@huisne.wrs.com> Date: Thu, 17 Jul 2003 05:38:28 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 02:39:15 -0000 Hi Bill, I tested the driver with the new patch and everything works fine now. Thank you for your quick response. If you need more testing of this NIC, I can always cooperate. Boris Georgiev ----- Original Message ----- From: "william paul" To: "Boris Georgiev" Cc: ; ; ; Sent: Wednesday, July 16, 2003 3:00 AM Subject: Re: Broadcom NetXtreme BCM5705M support > Of all the gin joints in all the towns in all the world, Boris Georgiev > had to walk into mine and say: > > > Hi Bill, > > > > Sorry for the previous e-mail, but have in mind that I'm trying to cooperate > > by testing your drivers and > > I am not aware of the rules for declaring a hardware problem in the mailing > > lists. The only way I can send > > you the messages from the kernel is if I rewrite them from the console. > > I know that. But that's a small price to pay for free driver development. :) > > > Here is the information that you requested: > > > > bge0: mem > > 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 > > bge0: firmware handshake timed out > > bge0: RX CPU self-diagnostics failed! > > bge0: chip initialization failed > > device_probe_and_attach: bge0 attach returned 6 > > > > If you need more detailed information, I can send it to you on request. > > Ok, the firmware handshake does not really load any firmware. This just > checks that the firmware on the NIC has responded to a reset and is back > up and running. The error here is due to the fact that the firmware > initialization seems to take longer on the 5705, so the timeout has to > be increased. > > Thanks for a couple of other people, I have made changes to deal with > this. Please download the latest driver code from the same URL > (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the > problem with the timeout, as well as a few other things. >