From owner-freebsd-drivers@FreeBSD.ORG Sun Feb 24 03:54:32 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85C0916A404 for ; Sun, 24 Feb 2008 03:54:32 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-72-87-39-191.ptldor.fios.verizon.net [72.87.39.191]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8A813C45A for ; Sun, 24 Feb 2008 03:54:32 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.2/8.13.8) with ESMTP id m1O3sV00001687 for ; Sat, 23 Feb 2008 19:54:31 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.2/8.14.1/Submit) with UUCP id m1O3sVOe001683 for freebsd-drivers@freebsd.org; Sat, 23 Feb 2008 19:54:31 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id DAA13602; Sun, 24 Feb 2008 03:52:47 GMT Message-Id: <200802240352.DAA13602@sopwith.solgatos.com> To: freebsd-drivers@freebsd.org Date: Sat, 23 Feb 2008 19:52:47 +0000 From: Dieter Subject: AMD/ATI GPU docs part 3 now available X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 03:54:32 -0000 ATI has released part 3 of the GPU docs. 3D for R300,400,500 (3D for R600 coming soon.) "The 3D programming documentation today is 300 pages and is made up of a programming guide and register specifications. Among the areas covered in this 3D guide are the command processor, vertex shaders, fragment shaders, Hyper-Z, and the various 3D registers." Docs are available here: http://ati.amd.com/developer/open_gpu_documentation.html http://www.x.org/docs/AMD/ Some commentary here: http://www.phoronix.com/scan.php?page=article&item=amd_tcore_release&num=1 From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 09:46:37 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B1F316A401 for ; Mon, 25 Feb 2008 09:46:37 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from in.niksun.com (210.18.76.166.sify.net [210.18.76.166]) by mx1.freebsd.org (Postfix) with ESMTP id DE1F413C461 for ; Mon, 25 Feb 2008 09:46:36 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from sharadc.in.niksun.com (unknown [10.60.5.27]) by in.niksun.com (Postfix) with ESMTP id 164045D33 for ; Mon, 25 Feb 2008 15:04:35 +0530 (IST) From: Sharad Chandra Organization: NIKSUN To: freebsd-drivers@freebsd.org Date: Mon, 25 Feb 2008 14:43:00 +0530 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200802251443.00541.sharadc@in.niksun.com> Subject: Start Fire nic card. X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 09:46:37 -0000 Hi, =A0=A0=A0=A0=A0=A0=A0=A0How does dual port star fire nic card time stamps? = Is the sheduling=20 round robin. if it is, there can be chances, a frame comes later than other= =20 can get lesser timestamp. =2D- Thanks Sharad Chandra From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 09:54:56 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B5C716A404 for ; Mon, 25 Feb 2008 09:54:56 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from mellanox.co.il (mail.mellanox.co.il [194.90.237.43]) by mx1.freebsd.org (Postfix) with ESMTP id 4474313C4D3 for ; Mon, 25 Feb 2008 09:54:54 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from Internal Mail-Server by MTLPINE1 (envelope-from yoniy@mellanox.co.il) with SMTP; 25 Feb 2008 11:28:13 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 25 Feb 2008 11:28:12 +0200 Message-ID: <6C2C79E72C305246B504CBA17B5500C9036413C6@mtlexch01.mtl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Capturing dmesg upon system crash on 6.3 Thread-Index: Ach3kL3hQymFtKb+RFyNrd/MD5v0KA== From: "Yehonatan Yossef" To: , , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 09:54:56 -0000 Hello, =20 I'm a freebsd newbee, trying to port an ethernet driver from Linux to FreeBSD 6.3. I'm facing a system reboot upon loading of the driver, and I could use a tool for capturing dmesg upon system crash (such as netconsole on Linux). =20 Can anyone link me to an appropriate tool? Sorry for sending this to three mailing lists, but I don't really know which one is active and relevant to this question. =20 =20 Cheers, =20 Yehonatan Yossef Mellanox Technologies INC Office: +972-4-9097200 ext. 301=20 Cell: +972-54-2345031 (yonyossef@skype ) =20 From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 13:41:08 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7784316A401 for ; Mon, 25 Feb 2008 13:41:08 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from mellanox.co.il (mail.mellanox.co.il [194.90.237.43]) by mx1.freebsd.org (Postfix) with ESMTP id 9085B13C469 for ; Mon, 25 Feb 2008 13:41:06 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from Internal Mail-Server by MTLPINE1 (envelope-from yoniy@mellanox.co.il) with SMTP; 25 Feb 2008 15:41:04 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 25 Feb 2008 15:41:03 +0200 Message-ID: <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Capturing dmesg upon system crash on 6.3 Thread-Index: Ach3slrKKlU2fL/eQ7CFr8XBDYAPYAAADarg From: "Yehonatan Yossef" To: Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org Subject: RE: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 13:41:08 -0000 I'm looking into the syslogd capabilities at the moment, it might be enough. I've tried following the serial console setup you've pointed, but when I added the 'console=3D"comconsole"' to loader.conf the OS hanged during boot time, had to re-install the system. I'm currently porting Mellanox ethernet driver, InfiniBand will be probably next. Mail me outside this list if you're interested in InfiniBand. Yehonatan Yossef Mellanox Technologies INC Office: +972-4-9097200 ext. 301=20 Cell: +972-54-2345031 (yonyossef@skype) =20 > -----Original Message----- > From: rea-fbsd@codelabs.ru [mailto:rea-fbsd@codelabs.ru]=20 > Sent: Monday, February 25, 2008 3:29 PM > To: Yehonatan Yossef > Cc: freebsd-questions@freebsd.org; freebsd-net@freebsd.org;=20 > freebsd-drivers@freebsd.org > Subject: Re: Capturing dmesg upon system crash on 6.3 >=20 > Yehonatan, good day. >=20 > Mon, Feb 25, 2008 at 11:28:12AM +0200, Yehonatan Yossef wrote: > > I'm a freebsd newbee, trying to port an ethernet driver=20 > from Linux to=20 > > FreeBSD 6.3. > > I'm facing a system reboot upon loading of the driver, and=20 > I could use=20 > > a tool for capturing dmesg upon system crash (such as netconsole on=20 > > Linux). >=20 > May be serial console will help you? > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/seri > alconsole-setup.html >=20 > Out of curiosity: are you porting some InfiniBand drivers to FreeBSD? > -- > Eygene >=20 From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 13:47:58 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE4616A410; Mon, 25 Feb 2008 13:47:58 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id C668913C4D3; Mon, 25 Feb 2008 13:47:57 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=ZiR3USzPOmH7Wa42pRI4z+UfDGcmmi7vK93T2BFoi6DrwpJJG1QT4XuxR8M/AZG7zZo3E5ydcllZ70vw9T8DBuF4KIltSpQldHoByBWXpNLlSGGAQ4MQu2gOBrxgBu6GaBdbNQaMeCBbDA8qbgBCSkABJ5ilOQjGH99FYOgdqqo=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JTdNr-0005nc-Gz; Mon, 25 Feb 2008 16:28:44 +0300 Date: Mon, 25 Feb 2008 16:28:42 +0300 From: Eygene Ryabinkin To: Yehonatan Yossef Message-ID: References: <6C2C79E72C305246B504CBA17B5500C9036413C6@mtlexch01.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <6C2C79E72C305246B504CBA17B5500C9036413C6@mtlexch01.mtl.com> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 13:47:58 -0000 Yehonatan, good day. Mon, Feb 25, 2008 at 11:28:12AM +0200, Yehonatan Yossef wrote: > I'm a freebsd newbee, trying to port an ethernet driver from Linux to > FreeBSD 6.3. > I'm facing a system reboot upon loading of the driver, and I could use a > tool for capturing dmesg upon system crash (such as netconsole on > Linux). May be serial console will help you? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html Out of curiosity: are you porting some InfiniBand drivers to FreeBSD? -- Eygene From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 13:57:57 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F137616A411; Mon, 25 Feb 2008 13:57:57 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A610C13C45B; Mon, 25 Feb 2008 13:57:57 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=OK3YfrIe3y6pdzfhWyCX68UPwMR1l2AW3glAyeuQbx7vSmcXEQ1N7K9u6BK2fOXS3bCP0EkEDCAzdkDnbg9P0PM+ZN6WSoIoy3Jft/xed2xgUTa/ja2uLy5AkKV8MUY3k9nLkBnX45D9W0IUv1QLWYRxdOm9Y6pNbKRfUMgOEcA=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JTdq7-0005xn-Op; Mon, 25 Feb 2008 16:57:56 +0300 Date: Mon, 25 Feb 2008 16:57:54 +0300 From: Eygene Ryabinkin To: Yehonatan Yossef Message-ID: References: <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 13:57:58 -0000 Mon, Feb 25, 2008 at 03:41:03PM +0200, Yehonatan Yossef wrote: > I'm looking into the syslogd capabilities at the moment, it might be > enough. Syslog can die too early to spot everything. But your mileage may vary. > I've tried following the serial console setup you've pointed, but when I > added the 'console="comconsole"' to loader.conf the OS hanged during > boot time, had to re-install the system. You mean that nothing were seen on the other end of the serial cable? I had not used serial console in FreeBSD for a while, so maybe others can tell if the Handbook is still correct? And if the only change that was made to make the OS hang was the change in the loader.conf, then you could just use LiveFS CD and edit loader.conf at your system -- there is no point in wasting time reinstalling the whole system. -- Eygene From owner-freebsd-drivers@FreeBSD.ORG Mon Feb 25 17:41:14 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DA4316A405 for ; Mon, 25 Feb 2008 17:41:14 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-72-87-39-191.ptldor.fios.verizon.net [72.87.39.191]) by mx1.freebsd.org (Postfix) with ESMTP id E353313C468 for ; Mon, 25 Feb 2008 17:41:08 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.2/8.13.8) with ESMTP id m1PHf8ou024797; Mon, 25 Feb 2008 09:41:08 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.2/8.14.1/Submit) with UUCP id m1PHf8rk024793; Mon, 25 Feb 2008 09:41:08 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id RAA00030; Mon, 25 Feb 2008 17:39:31 GMT Message-Id: <200802251739.RAA00030@sopwith.solgatos.com> To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org In-reply-to: Your message of "Mon, 25 Feb 2008 15:41:03 +0200." <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> Date: Mon, 25 Feb 2008 09:39:31 +0000 From: Dieter Cc: Subject: Re: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 17:41:14 -0000 > I'm looking into the syslogd capabilities at the moment, it might be > enough. > I've tried following the serial console setup you've pointed, but when I > added the 'console=3D"comconsole"' to loader.conf the OS hanged during > boot time, had to re-install the system. I assume the info you need is not getting captured in /var/log? Perhaps your system needs a firmware setting changed to use a RS-232 console? I assume it is not waiting for a control line, e.g. carrier detect, to go high? Some systems have buggy firmware and still read from the ps2 keyboard even though they are printing to the RS-232 console. If all else fails there is the aim a video camera at the screen method. :-( From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 26 01:03:44 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4884316A402 for ; Tue, 26 Feb 2008 01:03:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id 17E9D13C45E for ; Tue, 26 Feb 2008 01:03:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so1151244wfa.7 for ; Mon, 25 Feb 2008 17:03:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=r6PdXJIHtiTy+uZwDDhuxSUnMUuPWQRRH6agOZsu2c0=; b=ojWEV+hmou6sHfyEHqluCXE7B2X7clddDTN+L1Na18c6lo/iRoc0bmFZSmEygHEplfh5mI9sV+81OaGRPtU+VdxzRMYWdQltF3xTqdONS7eBcKyYS58NTW6noMWj72USgjxGHIdLr8rBM1OAieigkPwuhhynvykJdpBkbURa+Vg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=UozHtl6ckMrhtRXxXVwc4trsg5r7ChCeGbT70UDwjiDBO8bejxIJoTSOcduPiyoIFOCl1Hg7TKmbXDOHIfqc6rjyMn43tyetxzLeLAbBsJqmtiV2HFu5tCTcGscqs5vaeSjWIE6/ODBsnI+6VzoDLFKMT4Lrk2gPDd3c2MYhuc8= Received: by 10.142.240.9 with SMTP id n9mr3012535wfh.79.1203987823591; Mon, 25 Feb 2008 17:03:43 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 24sm10418734wff.10.2008.02.25.17.03.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Feb 2008 17:03:42 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m1Q13biG048047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2008 10:03:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m1Q13Y5E048046; Tue, 26 Feb 2008 10:03:34 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 26 Feb 2008 10:03:34 +0900 From: Pyun YongHyeon To: Sharad Chandra Message-ID: <20080226010334.GA47750@cdnetworks.co.kr> References: <200802251443.00541.sharadc@in.niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200802251443.00541.sharadc@in.niksun.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-drivers@freebsd.org Subject: Re: Start Fire nic card. X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 01:03:44 -0000 On Mon, Feb 25, 2008 at 02:43:00PM +0530, Sharad Chandra wrote: > Hi, > > ????????How does dual port star fire nic card time stamps? Is the sheduling > round robin. if it is, there can be chances, a frame comes later than other > can get lesser timestamp. > The Adaptec AIC-6915(aka StarFire) supports timestamps in its Tx/Rx descriptor format. So you can get a timestamp for each transmitted/received frames. The timestamp is based on an internal 32bit CurrentTimer register(0.8us resolution). ATM sf(4) does not use these timestamps in descriptor format so you have to change decriptor format to include the timestamp and initialize CurrentTimer register prior to get timestamps. But there is no easy to pass these timestamp information to upper layer so you may have to add special ioctls into the driver to get these information. See Adaptec AIC-6915 datasheet for more information. In order to get correct timestamp on Dual/Quad ports Starfire NICs you may have to to set CurrentTimer register of all ports with the same value to synchronize the timer value. -- Regards, Pyun YongHyeon From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 26 11:50:44 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDD410658B2 for ; Tue, 26 Feb 2008 11:50:43 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by mx1.freebsd.org (Postfix) with ESMTP id AF9C1140F85 for ; Tue, 26 Feb 2008 10:43:50 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by fk-out-0910.google.com with SMTP id b27so2669072fka.11 for ; Tue, 26 Feb 2008 02:43:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; bh=RIXDXCNpQuCG8Op6L0vF1b1UNRUS6C/qsCiaIIXWQmI=; b=gqwZJC5cShlas9RR17/jnsAVBnfui1fw7gtITdWw2wKfaFjbMpZhL1GNLZ6CwQ9L9zZkmwUhsHEmgDrrHIebT5lBhjxlZYiL2DsNLK8Dy6SG4kJ+TTT2EpOWWme4cXtjeJn0+dbyO07+vKcd26JppLBlMqQipP+4+4Nb4J7KsK0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=hqMXKJmrFoYeOJwfQJgd+teP1jNGoTFgd000vgdypVdjWbLGy9kj7RU88XjJnzREKRFjgJjjmokdhwe8qJ5tW5LKyVKpsrey1LaUtBPIKpbLfvDhZ4XZQRekEFoUc7SUybR2l5ASf8nUTwg0Bx5cnKLwtRGF34OBWR1R8Q28XuA= Received: by 10.82.123.16 with SMTP id v16mr8509064buc.36.1204022628237; Tue, 26 Feb 2008 02:43:48 -0800 (PST) Received: from ?127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTPS id j8sm5195517gvb.7.2008.02.26.02.43.46 (version=SSLv3 cipher=RC4-MD5); Tue, 26 Feb 2008 02:43:47 -0800 (PST) From: Tom Evans To: Yehonatan Yossef In-Reply-To: <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> References: <6C2C79E72C305246B504CBA17B5500C903641642@mtlexch01.mtl.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-PQXXfntwCv4BEZPFMnFN" Date: Tue, 26 Feb 2008 10:43:45 +0000 Message-Id: <1204022625.2126.118.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-net@freebsd.org, rea-fbsd@codelabs.ru, freebsd-questions@freebsd.org, freebsd-drivers@freebsd.org Subject: RE: Capturing dmesg upon system crash on 6.3 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 11:50:45 -0000 --=-PQXXfntwCv4BEZPFMnFN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-02-25 at 15:41 +0200, Yehonatan Yossef wrote: > I'm looking into the syslogd capabilities at the moment, it might be > enough. > I've tried following the serial console setup you've pointed, but when I > added the 'console=3D"comconsole"' to loader.conf the OS hanged during > boot time, had to re-install the system. >=20 > I'm currently porting Mellanox ethernet driver, InfiniBand will be > probably next. Mail me outside this list if you're interested in > InfiniBand. >=20 The OS probably didnt hang, you told it to send all its output to comconsole (ie serial port) and not display anything. This might look as though it has hung. Try (in /boot/loader.conf): boot_multicons=3D"YES" console=3D"vidconsole,comconsole" to output to both of them. Also, set the correct tty on your serial console with something like (in /etc/ttys): ttyd0 "/usr/libexec/getty std.9600" vt100 off secure There will be a ttyd0 line already. All of this is in the various handbooks. Cheers Tom --=-PQXXfntwCv4BEZPFMnFN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHw+1elcRvFfyds/cRAtRAAKCcRdEnyODeavqpNgdO8hxzoOrtuACfQ5dJ qetwCxmSmOtOqzanF+UjPJc= =dSpX -----END PGP SIGNATURE----- --=-PQXXfntwCv4BEZPFMnFN--