Date: Thu, 27 Oct 2005 00:06:48 +0800 From: Dinesh Nair <dinesh@alphaque.com> To: Scott Long <scottl@samsco.org> Cc: freebsd-hackers@freebsd.org Subject: Re: [Fwd: Re: use of bus_dmamap_sync] Message-ID: <435FA998.2050409@alphaque.com> In-Reply-To: <435FA6A9.4000600@samsco.org> References: <435EEC56.9080708@samsco.org> <435F428E.50609@alphaque.com> <200510261130.45506.jhb@freebsd.org> <435FA6A9.4000600@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/26/05 23:54 Scott Long said the following: > The value of the map is an implementation detail, which is why it's an > opaque typedef. Portable code should always assume that the map has > valid data. Now, specifically for i386, if you have a device with a right, so for portability's sake, bus_dmamap_sync should be used anyway. > twe), and you are not using PAE, then yes the map will be NULL and the > syncs will do nothing. Assuming that all three of these cases are false > is not good, though. well, they are in my situation, so obviously bus dma is not the cause of the problem i'm seeing. thanx to both scottl and jhb for the explanation. this throws a lot of light onto the handling of dma access to devices for me. -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?435FA998.2050409>