From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BbLgT-0005v8-Ic for qemu-devel@nongnu.org; Fri, 18 Jun 2004 11:53:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BbLgQ-0005uP-DY for qemu-devel@nongnu.org; Fri, 18 Jun 2004 11:53:39 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BbLgQ-0005uM-Bd for qemu-devel@nongnu.org; Fri, 18 Jun 2004 11:53:38 -0400 Received: from [213.146.130.142] (helo=trantor.org.uk) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BbLey-0003cu-53 for qemu-devel@nongnu.org; Fri, 18 Jun 2004 11:52:08 -0400 From: Gianni Tedesco Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-vas8M4CVRekt+qQj3GX1" Date: Fri, 18 Jun 2004 16:45:00 +0100 Message-Id: <1087573500.3375.175.camel@sherbert> Mime-Version: 1.0 Subject: [Qemu-devel] [USB-OHCI]: Best way to access physical memory? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --=-vas8M4CVRekt+qQj3GX1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, The USB OHCI driver needs to access host physical memory (to access HCCA and endpoint descriptors). Should I just read/write directly in to the buffer pointed to by phys_ram_base, or is there a better way? Obviously, any I/O memory regions stuffed on the end of 'real' physical mem won't be accessible if I just go direct to phys_ram_base, but I doubt anyone relies on that feature... Fabrice, what do you think? --=20 // Gianni Tedesco (gianni at scaramanga dot co dot uk) lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import 8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D --=-vas8M4CVRekt+qQj3GX1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA0w38kbV2aYZGvn0RAjbjAKCFwM/c9r51zFdXGweToL3erfeaqwCcCmlD Vpe9h7NjKX/sJ8OVmhOjrSw= =5Aun -----END PGP SIGNATURE----- --=-vas8M4CVRekt+qQj3GX1--