Date: Thu, 10 Jul 2008 13:54:03 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: David Christensen <davidch@broadcom.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems Message-ID: <20080710035403.GZ62764@server.vk2pj.dyndns.org> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> References: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--yr/DzoowOgTDcSCF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jul-09 18:00:45 -0700, David Christensen <davidch@broadcom.com> wro= te: >I have some debugging code in my network driver and I'd like >to print out the physical address of a memory block. What's >the right way to use a printf() that works on both 32 and 64 >bit platforms? %p - see printf(3) or printf(9) --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --yr/DzoowOgTDcSCF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh1h9sACgkQ/opHv/APuIfsqgCfZuR8fkl3i8jj6asBMlghk1OE TR4AnRlSz2E6QiE3qPGvPHQLg8UytjK6 =CSXz -----END PGP SIGNATURE----- --yr/DzoowOgTDcSCF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080710035403.GZ62764>