From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21471-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 22189 invoked by alias); 9 May 2005 22:39:37 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 22143 invoked from network); 9 May 2005 22:39:29 -0000
Received: from unknown (HELO sccrmhc11.comcast.net) (204.127.202.55)
  by sourceware.org with SMTP; 9 May 2005 22:39:29 -0000
Received: from [10.0.1.2] (c-24-61-199-96.hsd1.nh.comcast.net[24.61.199.96])
          by comcast.net (sccrmhc11) with SMTP
          id <20050509223927011002231ue>; Mon, 9 May 2005 22:39:28 +0000
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Mon, 09 May 2005 22:39:00 -0000
Subject: Re: RFC: Available registers as a target property
From: Paul Schlie <schlie@comcast.net>
To: Chris Zankel <zankel@tensilica.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	<gdb@sources.redhat.com>
Message-ID: <BEA55EDD.A18C%schlie@comcast.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-SW-Source: 2005-05/txt/msg00126.txt.bz2

> Chris Zankel <zankel@tensilica.com> writes:
> I am wondering if it would also make sense to support the other way around and
> let GDB tell the target about the processor/register configuration. A scenario
> for this would be where GDB talks to an OCD daemon (=target) that controls the
> processor via JTAG. The daemon wouldn't need to know everything about the
> processor configuration.

Would seem sensible to consider, especially coming from a company with a
better perspective on the requirements of "configurable" processors than
most?