This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 26 12:06:20 2024 Received: from spaans.ds9a.nl (adsl-xs4all.ds9a.nl [213.84.159.51]) by kylie.puddingonline.com (8.11.6/8.11.6) with SMTP id g8IHXPX28445 for ; Wed, 18 Sep 2002 19:33:25 +0200 Received: (qmail 6072 invoked from network); 18 Sep 2002 06:34:34 -0000 Received: from unknown (HELO spaans.ds9a.nl) (3ffe:8280:10:360:202:44ff:fe2a:a1dd) by mayo.ipv6.ds9a.nl with SMTP; 18 Sep 2002 06:34:34 -0000 Received: (qmail 5071 invoked by uid 1000); 17 Sep 2002 20:03:29 -0000 Received: (maildatabase); juh Received: (qmail 19151 invoked by alias); 20 Feb 2001 14:14:20 -0000 Received: (qmail 19148 invoked from network); 20 Feb 2001 14:14:19 -0000 Received: from vger.kernel.org (199.183.24.194) by spaans-smp.ds9a.tudelft.nl with SMTP; 20 Feb 2001 14:14:19 -0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Feb 2001 09:13:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Feb 2001 09:13:15 -0500 Received: from kxmail.berlin.de ([195.243.105.30]:14216 "EHLO kxmail.berlin.de") by vger.kernel.org with ESMTP id ; Tue, 20 Feb 2001 09:13:00 -0500 Received: from berlin.de ([212.169.150.196]) by kxmail.berlin.de (InterMail vK.4.03.02.00 201-232-124 license fe348d0cbfe748edc21620d019afaec9) with ESMTP id <20010220141256.TQOJ885.kxmail@berlin.de> for ; Message-Id: <3A927AE9.CE3B88F9@berlin.de> Date: Tue, 20 Feb 2001 15:10:49 +0100 From: Norbert Roos X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-7 i686) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: Probs with PCI bus master DMA to user space References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org Jeff Garzik wrote: > > But the buffers are usually allocated with malloc() by any application > > which wants to use my driver.. otherwise my driver would have to offer a > > malloc-like function, but I can hardly force the application to use my > > own malloc function. > > If you are writing the driver, sure you can. ?? The application is doing something like fd = open("/dev/mydriver"); buf = malloc(); fill_buffer_with_data(buf);  write(fd,buf); And now i should tell the programmer not to use malloc() but my special driver-malloc? Or do you mean something different? Norbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/