Date: Fri, 07 Sep 2001 17:24:40 -0600 From: Warner Losh <imp@harmony.village.org> To: Bruce Evans <bde@zeta.org.au> Cc: John Baldwin <jhb@FreeBSD.ORG>, Julian Elischer <julian@vicor-nb.com>, current@FreeBSD.ORG Subject: Re: RFC: hack volatile bzero and bcopy Message-ID: <200109072324.f87NOeh65478@harmony.village.org> In-Reply-To: Your message of "Fri, 07 Sep 2001 20:55:11 %2B1000." <20010907203306.J38152-100000@alphplex.bde.org> References: <20010907203306.J38152-100000@alphplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010907203306.J38152-100000@alphplex.bde.org> Bruce Evans writes: : In the case of if_ie.c and bcopy(), bcopy() is not suitable for copying : memory that doesn't behave like RAM. Some optimized versions of it : do out of order and/or repeated copies. This might be very bad for : volatile device memory. I think rewriting if_ie.c to use bus_space : would make most of the warnings go away automatically. Right. bus_space_read/write_N likely should be used instead. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109072324.f87NOeh65478>