From owner-freebsd-drivers@FreeBSD.ORG Mon Aug 21 10:49:19 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 211F716A4E1 for ; Mon, 21 Aug 2006 10:49:19 +0000 (UTC) (envelope-from namaskar_alok@yahoo.co.in) Received: from web8905.mail.in.yahoo.com (web8905.mail.in.yahoo.com [203.84.221.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 2AA0943D77 for ; Mon, 21 Aug 2006 10:49:14 +0000 (GMT) (envelope-from namaskar_alok@yahoo.co.in) Received: (qmail 3901 invoked by uid 60001); 21 Aug 2006 10:49:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Cqp+ONY8DOFU1s/MorIL+16QUcoKTmbfYbHrnuXDjO4NMaJapuaD11sucSQNVQrvyQAEjiz3ah8khTfQsK6xZVVQPpnoiZoImqG9amoglrwafD+0dcNh/82Ym9H5BvyRzRny9Hb9XKmftlVJMF5RQA/wLYe4GnVcMyjRjGR6RQQ= ; Message-ID: <20060821104912.3899.qmail@web8905.mail.in.yahoo.com> Received: from [220.225.33.101] by web8905.mail.in.yahoo.com via HTTP; Mon, 21 Aug 2006 03:49:12 PDT Date: Mon, 21 Aug 2006 03:49:12 -0700 (PDT) From: Alok Barsode To: freebsd-drivers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Device configuration and Structure 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, 21 Aug 2006 10:49:19 -0000 Hi all, I wanted to know how r memory-mapped devices configured during initialization? Like for example if i have a PCI ethernet card,which is attached to the PCI bus.The PCI bus will probe the attached device, call all the associated drivers (in the driver list in devclass pcibus)during autoconf and associate a driver which bids the max,But what if i have a onboard memory-mapped ethernet controller? what bus will it attach itself to? I am developing a device driver for a onboard memory mapped ethernet controller. Thanks, Alok. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-drivers@FreeBSD.ORG Mon Aug 21 16:49:07 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B1C316A4E7 for ; Mon, 21 Aug 2006 16:49:07 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F94643D76 for ; Mon, 21 Aug 2006 16:49:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k7LGlFgH022441; Mon, 21 Aug 2006 10:47:16 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 21 Aug 2006 10:47:20 -0600 (MDT) Message-Id: <20060821.104720.-432838016.imp@bsdimp.com> To: namaskar_alok@yahoo.co.in From: "M. Warner Losh" In-Reply-To: <20060821104912.3899.qmail@web8905.mail.in.yahoo.com> References: <20060821104912.3899.qmail@web8905.mail.in.yahoo.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 21 Aug 2006 10:47:16 -0600 (MDT) Cc: freebsd-drivers@freebsd.org Subject: Re: Device configuration and Structure 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, 21 Aug 2006 16:49:07 -0000 In message: <20060821104912.3899.qmail@web8905.mail.in.yahoo.com> Alok Barsode writes: : I wanted to know how r memory-mapped devices : configured during initialization? : : Like for example if i have a PCI ethernet card,which : is attached to the PCI bus.The PCI bus will probe the : attached device, call all the associated drivers (in : the driver list in devclass pcibus)during autoconf and : associate a driver which bids the max,But what if i : have a onboard memory-mapped ethernet controller? what : bus will it attach itself to? If this device is just hanging out in memory space, and isn't on the PCI bus, then you'll need to arrange via some other means to have it probed/attached. On the AT91RM9200 port that I just did enumerated all the devices I knew the CPU had in the atmelarm bus driver with known resources. This was all hard coded. I plan on migrating to using a hinted scheme shortly so that we can support other members of the arm9 at91 family. This sounds like an embedded box of some flavor, so you may need to do this. If this is a x86 box, then you can just list a hint on the ISA bus, just like you would for any other ISA device. This is a small lie, but likely not a fatal one. The only issue becomes how to route the interrupt. Does that help? Warner : I am developing a device driver for a onboard memory : mapped ethernet controller. : : Thanks, : Alok. : : __________________________________________________ : Do You Yahoo!? : Tired of spam? Yahoo! Mail has the best spam protection around : http://mail.yahoo.com : _______________________________________________ : freebsd-drivers@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" : : From owner-freebsd-drivers@FreeBSD.ORG Tue Aug 22 12:07:59 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA06D16A4DD for ; Tue, 22 Aug 2006 12:07:59 +0000 (UTC) (envelope-from Jim.Skon@mvnu.edu) Received: from alderaan.mvnu.edu (alderaan.mvnu.edu [149.143.2.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B91443D69 for ; Tue, 22 Aug 2006 12:07:58 +0000 (GMT) (envelope-from Jim.Skon@mvnu.edu) Received: from nzrnet.mvnu.edu ([149.143.207.202]) by alderaan.mvnu.edu (8.12.8/8.12.8) with ESMTP id k7MC7uZh012792 for ; Tue, 22 Aug 2006 08:07:56 -0400 (EDT) Received: from NZR_MTA-MTA by nzrnet.mvnu.edu with Novell_GroupWise; Tue, 22 Aug 2006 08:07:51 -0400 Message-Id: <44EABB35020000FC00000D46@nzrnet.mvnu.edu> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Tue, 22 Aug 2006 08:07:17 -0400 From: "Jim Skon" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Problem with high bandwidth callouts 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, 22 Aug 2006 12:07:59 -0000 Hello, I have been developing a modification to the 802.11 driver to support a version of PCF (polling mode). The AP part of this solution depends on several active callouts to time the operation of the protocol. The problem I am having is that after several hours of stress testing (pushing the system at maximum bandwidth), the system appears to start losing set callouts. The callouts are still active, and past due, but are never called. I have already done similar implementations in the netbsd and linux environments, and have never had such a problem. Note that I am setting callouts (only 3) at a rate in the 100's per second, so a lot is going on. Has anyone ever had such a problem? Thanks! Jim Skon Professor of Computer Science Mount Vernon Nazarene University James Skon, Ph.D. Computer Science Department Chair Professor of Computer Science (740) 392-6868 x 3224 Mount Vernon Nazarene University EMAIL: skon@mvnu.edu www.mvnu.edu From owner-freebsd-drivers@FreeBSD.ORG Tue Aug 22 15:02:19 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F347B16A4DA for ; Tue, 22 Aug 2006 15:02:18 +0000 (UTC) (envelope-from Jim.Skon@mvnu.edu) Received: from alderaan.mvnu.edu (alderaan.mvnu.edu [149.143.2.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98CEE43D46 for ; Tue, 22 Aug 2006 15:02:18 +0000 (GMT) (envelope-from Jim.Skon@mvnu.edu) Received: from nzrnet.mvnu.edu ([149.143.207.202]) by alderaan.mvnu.edu (8.12.8/8.12.8) with ESMTP id k7MF2FZh014782 for ; Tue, 22 Aug 2006 11:02:16 -0400 (EDT) Received: from NZR_MTA-MTA by nzrnet.mvnu.edu with Novell_GroupWise; Tue, 22 Aug 2006 11:02:11 -0400 Message-Id: <44EAE420020000FC00000D5A@nzrnet.mvnu.edu> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Tue, 22 Aug 2006 11:01:51 -0400 From: "Jim Skon" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Problems with dropped callouts 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, 22 Aug 2006 15:02:19 -0000 Hello, I have been developing a modification to the 802.11 driver to support a version of PCF (polling mode). The AP part of this solution depends on several active callouts to time the operation of the protocol. The problem I am having is that after several hours of stress testing (pushing the system at maximum bandwidth), the system appears to start losing set callouts. The callouts are still active, and past due, but are never called. I have already done similar implementations in the netbsd and linux environments, and have never had such a problem. Note that I am setting callouts (only 3) at a rate in the 100's per second, so a lot is going on. Has anyone ever had such a problem? Thanks! Jim Skon Professor of Computer Science Mount Vernon Nazarene University James Skon, Ph.D. Computer Science Department Chair Professor of Computer Science (740) 392-6868 x 3224 Mount Vernon Nazarene University EMAIL: skon@mvnu.edu www.mvnu.edu From owner-freebsd-drivers@FreeBSD.ORG Tue Aug 22 20:00:50 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F8D16A4DA for ; Tue, 22 Aug 2006 20:00:50 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1E3343D46 for ; Tue, 22 Aug 2006 20:00:49 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k7MK0jCP048886; Tue, 22 Aug 2006 16:00:46 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Tue, 22 Aug 2006 14:50:32 -0400 User-Agent: KMail/1.9.1 References: <44EAE420020000FC00000D5A@nzrnet.mvnu.edu> In-Reply-To: <44EAE420020000FC00000D5A@nzrnet.mvnu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608221450.32537.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 22 Aug 2006 16:00:46 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1708/Tue Aug 22 08:43:00 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jim Skon Subject: Re: Problems with dropped callouts 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, 22 Aug 2006 20:00:50 -0000 On Tuesday 22 August 2006 11:01, Jim Skon wrote: > Hello, > > I have been developing a modification to the 802.11 driver to support a > version of PCF (polling mode). The AP part of this solution depends on > several active callouts to time the operation of the protocol. The > problem I am having is that after several hours of stress testing > (pushing the system at maximum bandwidth), the system appears to start > losing set callouts. The callouts are still active, and past due, but > are never called. > > I have already done similar implementations in the netbsd and linux > environments, and have never had such a problem. > > Note that I am setting callouts (only 3) at a rate in the 100's per > second, so a lot is going on. > > Has anyone ever had such a problem? I'm not aware of anyone else having this problem (yet). If you generate a core dump, can you see the callouts on the calloutwheels? -- John Baldwin