From owner-freebsd-drivers@FreeBSD.ORG Wed Apr 2 02:08:02 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 60D5B106566B for ; Wed, 2 Apr 2008 02:08:02 +0000 (UTC) (envelope-from demetrioussharpe@netscape.net) Received: from imo-m19.mx.aol.com (imo-m19.mx.aol.com [64.12.137.11]) by mx1.freebsd.org (Postfix) with ESMTP id EAA3F8FC14 for ; Wed, 2 Apr 2008 02:08:01 +0000 (UTC) (envelope-from demetrioussharpe@netscape.net) Received: from demetrioussharpe@netscape.net by imo-m19.mx.aol.com (mail_out_v38_r9.3.) id n.d18.25933856 (57869); Tue, 1 Apr 2008 21:57:42 -0400 (EDT) Received: from FWM-D16 (fwm-d16.webmail.aol.com [205.188.160.208]) by air-ia01.mail.aol.com (v121.4) with ESMTP id MAILINIA13-e20d47f2e81626; Tue, 01 Apr 2008 21:57:42 -0400 To: freebsd-drivers@freebsd.org, tech@openbsd.org, tech-x11@netbsd.org Date: Tue, 01 Apr 2008 21:57:42 -0400 X-MB-Message-Source: WebUI X-AOL-IP: 71.51.47.48 X-MB-Message-Type: User MIME-Version: 1.0 From: demetrioussharpe@netscape.net X-Mailer: AIM WebMail 35304-STANDARD Received: from 71.51.47.48 by FWM-D16.sysops.aol.com (205.188.160.208) with HTTP (WebMailUI); Tue, 01 Apr 2008 21:57:42 -0400 Message-Id: <8CA627C12AFD996-2F0-1804@FWM-D16.sysops.aol.com> X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: agpgart driver 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: Wed, 02 Apr 2008 02:08:02 -0000 Hello, My name is Dee Sharpe.? I am currently researching the *BSD agpgart driver as well as the one from Linux and any other OS's driver that I can find.? From reading the source code agp.c, it seems as though agp_generic_bind_memory() allocates memory from the OS.? Why is this the case?? Shouldn't this function be solely focused on binding the memory that is provided in the agp_memory structure?? Also, shouldn't agp_generic_alloc_memory() be the only part of the driver that worries about memory allocation?? I am asking these questions out of interest and I'm looking for understanding, because I would like to port your driver to Syllable.? Syllable has a relatively primitive memory management system, so a lot of the techniques used by the *BSD OS's will not be usable by us.? Also, any help or guidance that you can give me to help me bring this driver to life is greatly appreciated. -Dee Sharpe P.S.? This email was sent to mailing lists belonging to FreeBSD, OpenBSD, and NetBSD.