From owner-freebsd-current@FreeBSD.ORG Fri Mar 2 22:02:46 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D22716A401 for ; Fri, 2 Mar 2007 22:02:46 +0000 (UTC) (envelope-from john@utzweb.net) Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5144813C4A5 for ; Fri, 2 Mar 2007 22:02:46 +0000 (UTC) (envelope-from john@utzweb.net) Received: from utzweb.net (localhost [127.0.0.1]) by marley.grokthis.net (Postfix) with ESMTP id A0C9FF102B; Fri, 2 Mar 2007 17:02:33 -0500 (EST) Received: from 69.93.78.27 (proxying for 199.201.237.2) (SquirrelMail authenticated user john-utzweb-net); by utzweb.net with HTTP; Fri, 2 Mar 2007 17:02:50 -0500 (EST) Message-ID: <53196.69.93.78.27.1172872970.squirrel@69.93.78.27> In-Reply-To: <20070302195855.GA28016@soaustin.net> References: <200703021442.l22Eg6QT058195@casselton.net> <45E84AD3.7010908@samsco.org> <20070302195855.GA28016@soaustin.net> Date: Fri, 2 Mar 2007 17:02:50 -0500 (EST) From: john@utzweb.net To: "Mark Linimon" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Mark Tinguely , current@freebsd.org Subject: Re: multisegment bus_dmamem_alloc() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 22:02:46 -0000 > On Fri, Mar 02, 2007 at 09:03:31AM -0700, Scott Long wrote: >> Looking at bktr, it's not at all clear to me why the author felt that >> FreeBSD didn't support bus_dmamem_alloc. because it didnt when he wrote it back in the 90's! IIRC he presented this on freebsd-multimedia around freebsd 2x > The bktr author has been gone from the project for several years, and the > code had been neglected for a while before that. The PRs against it > reflect > this (that's the only reason I know about this driver; I wound up > resetting > the PR assignments). that's hilarious. this os is getting old :-) > So this isn't a case of someone not following the standards, this is just > plain old bitrot. textbook example thereof, should be added to textbooks as an expository example :-) it's rather astounding that it's worked for this long; reminds me of the guy on the raft in 'The Cruel Sea' > With bugmeister hat on, I'd be glad to see someone pick > up this driver and fix it. me too! best of luck! > mcl > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >