From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sivasakthi7@outlook.com>
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ozlabs.org (Postfix) with ESMTPS id CB54114008E
 for <linuxppc-dev@ozlabs.org>; Tue, 22 Apr 2014 23:00:28 +1000 (EST)
Received: from tom.nabble.com ([192.168.236.105])
 by sam.nabble.com with esmtp (Exim 4.72)
 (envelope-from <sivasakthi7@outlook.com>) id 1Wca2a-0000Gk-SV
 for linuxppc-dev@ozlabs.org; Tue, 22 Apr 2014 05:43:12 -0700
Date: Tue, 22 Apr 2014 05:43:12 -0700 (PDT)
From: shiva7 <sivasakthi7@outlook.com>
To: linuxppc-dev@ozlabs.org
Message-ID: <1398170592855-81732.post@n7.nabble.com>
In-Reply-To: <5167457E.1050205@genband.com>
References: <5167457E.1050205@genband.com>
Subject: Re: questions on CONFIG_PPC_ADV_DEBUG_REGS, DBCR0_BRT, and
 DBCR0_ACTIVE_EVENTS
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/linuxppc-dev/>
List-Post: <mailto:linuxppc-dev@lists.ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=subscribe>

I have the same question as like above posted by Mr. Chirs. 

Could someone help to understand why the debug BRT bit not handled in debug
context sys call? Intentional or need volunteer to finish up this part :)



--
View this message in context: http://linuxppc.10917.n7.nabble.com/questions-on-CONFIG-PPC-ADV-DEBUG-REGS-DBCR0-BRT-and-DBCR0-ACTIVE-EVENTS-tp70147p81732.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.