From owner-freebsd-arm@FreeBSD.ORG Tue Mar 17 16:04:48 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8ECDA66D; Tue, 17 Mar 2015 16:04:48 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i190.relay.mailchannels.net [162.253.144.72]) by mx1.freebsd.org (Postfix) with ESMTP id 5E19E1EB; Tue, 17 Mar 2015 16:04:46 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (ip-10-33-12-218.us-west-2.compute.internal [10.33.12.218]) by relay.mailchannels.net (Postfix) with ESMTPA id 20706529D; Tue, 17 Mar 2015 16:04:30 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (smtp5.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Tue, 17 Mar 2015 16:04:36 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426608276274:350221930 X-MC-Ingress-Time: 1426608276274 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YXtym-000854-9E; Tue, 17 Mar 2015 16:04:28 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2HG4OZg025906; Tue, 17 Mar 2015 10:04:24 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18CkHqb0oBAQJYi4seBDKko Message-ID: <1426608264.25614.13.camel@freebsd.org> Subject: Re: hexdumping /dev/mem From: Ian Lepore To: Stanislav Sedov Date: Tue, 17 Mar 2015 10:04:24 -0600 In-Reply-To: <8033BAE2-9D21-4DB3-AEE9-727B1F3CE9C7@freebsd.org> References: <29227F8C-4A83-4C95-9CD2-BA14E797A882@sbcglobal.net> <8033BAE2-9D21-4DB3-AEE9-727B1F3CE9C7@freebsd.org> Content-Type: text/plain; charset="iso-2022-jp" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-arm@freebsd.org, =?ISO-8859-1?Q?Mat=EDas?= Perret Cantoni X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 16:04:48 -0000 On Mon, 2015-03-16 at 16:41 -0700, Stanislav Sedov wrote: > > On Mar 16, 2015, at 3:58 PM, Matas Perret Cantoni wrote: > > > > I couldn't find any man page for "kdb" or "db", and the help command > > of db didn't help much. > > The only relevant manual pages are ddb(4) and ddb(8), I’m afraid. > But they have plenty of information. Nothing on devmap though. > show devmap and show physmem are arm-specific commands I added a while back, but didn't document anywhere except in the builtin help display. Accessing device registers from ddb is possible because the access is all within the kernel (unlike with /dev/[k]mem where the pages have to be mapped into user space, which can't be done safely on arm). But you still have to be careful about what other device drivers might be doing with the same registers (if there are drivers attached for that hardware). -- Ian