Date: Fri, 2 Mar 2007 17:02:50 -0500 (EST) From: john@utzweb.net To: "Mark Linimon" <linimon@lonesome.com> Cc: Mark Tinguely <tinguely@casselton.net>, current@freebsd.org Subject: Re: multisegment bus_dmamem_alloc() 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53196.69.93.78.27.1172872970.squirrel>