* [PATCH] Remove doc on OpenRISC 1000
@ 2013-03-18 3:45 Yao Qi
[not found] ` <1363700147.23712.277.camel@laria>
2013-03-22 1:40 ` Yao Qi
0 siblings, 2 replies; 6+ messages in thread
From: Yao Qi @ 2013-03-18 3:45 UTC (permalink / raw)
To: gdb-patches
Hi,
I happen to see the doc on "OpenRISC 1000" today, but it is not supported
in FSF GDB. This patch is to remove the doc bits.
The doc patch was approved in this thread
http://sourceware.org/ml/gdb-patches/2002-09/msg00573.html
but I don't find when the c code (such as or1k-tdep.c) was approved and
committed.
The OpenRISC stuff still exists in "GDB Internals", but I leave them
there as it is still useful.
Is it OK?
gdb/doc:
2013-03-18 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Embedded Processors): Remove menu item "OpenRISC 1000".
(OpenRISC 1000): Remove.
---
gdb/doc/gdb.texinfo | 115 ---------------------------------------------------
1 files changed, 0 insertions(+), 115 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c92b667..7a4751c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -19862,7 +19862,6 @@ acceptable commands.
* M68K:: Motorola M68K
* MicroBlaze:: Xilinx MicroBlaze
* MIPS Embedded:: MIPS Embedded
-* OpenRISC 1000:: OpenRisc 1000
* PowerPC Embedded:: PowerPC Embedded
* PA:: HP PA Embedded
* Sparclet:: Tsqware Sparclet
@@ -20336,120 +20335,6 @@ This command allows sending an arbitrary @var{command} string to the
monitor. The monitor must be in debug mode for this to work.
@end table
-@node OpenRISC 1000
-@subsection OpenRISC 1000
-@cindex OpenRISC 1000
-
-@cindex or1k boards
-See OR1k Architecture document (@uref{www.opencores.org}) for more information
-about platform and commands.
-
-@table @code
-
-@kindex target jtag
-@item target jtag jtag://@var{host}:@var{port}
-
-Connects to remote JTAG server.
-JTAG remote server can be either an or1ksim or JTAG server,
-connected via parallel port to the board.
-
-Example: @code{target jtag jtag://localhost:9999}
-
-@kindex or1ksim
-@item or1ksim @var{command}
-If connected to @code{or1ksim} OpenRISC 1000 Architectural
-Simulator, proprietary commands can be executed.
-
-@kindex info or1k spr
-@item info or1k spr
-Displays spr groups.
-
-@item info or1k spr @var{group}
-@itemx info or1k spr @var{groupno}
-Displays register names in selected group.
-
-@item info or1k spr @var{group} @var{register}
-@itemx info or1k spr @var{register}
-@itemx info or1k spr @var{groupno} @var{registerno}
-@itemx info or1k spr @var{registerno}
-Shows information about specified spr register.
-
-@kindex spr
-@item spr @var{group} @var{register} @var{value}
-@itemx spr @var{register @var{value}}
-@itemx spr @var{groupno} @var{registerno @var{value}}
-@itemx spr @var{registerno @var{value}}
-Writes @var{value} to specified spr register.
-@end table
-
-Some implementations of OpenRISC 1000 Architecture also have hardware trace.
-It is very similar to @value{GDBN} trace, except it does not interfere with normal
-program execution and is thus much faster. Hardware breakpoints/watchpoint
-triggers can be set using:
-@table @code
-@item $LEA/$LDATA
-Load effective address/data
-@item $SEA/$SDATA
-Store effective address/data
-@item $AEA/$ADATA
-Access effective address ($SEA or $LEA) or data ($SDATA/$LDATA)
-@item $FETCH
-Fetch data
-@end table
-
-When triggered, it can capture low level data, like: @code{PC}, @code{LSEA},
-@code{LDATA}, @code{SDATA}, @code{READSPR}, @code{WRITESPR}, @code{INSTR}.
-
-@code{htrace} commands:
-@cindex OpenRISC 1000 htrace
-@table @code
-@kindex hwatch
-@item hwatch @var{conditional}
-Set hardware watchpoint on combination of Load/Store Effective Address(es)
-or Data. For example:
-
-@code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)}
-
-@code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)}
-
-@kindex htrace
-@item htrace info
-Display information about current HW trace configuration.
-
-@item htrace trigger @var{conditional}
-Set starting criteria for HW trace.
-
-@item htrace qualifier @var{conditional}
-Set acquisition qualifier for HW trace.
-
-@item htrace stop @var{conditional}
-Set HW trace stopping criteria.
-
-@item htrace record [@var{data}]*
-Selects the data to be recorded, when qualifier is met and HW trace was
-triggered.
-
-@item htrace enable
-@itemx htrace disable
-Enables/disables the HW trace.
-
-@item htrace rewind [@var{filename}]
-Clears currently recorded trace data.
-
-If filename is specified, new trace file is made and any newly collected data
-will be written there.
-
-@item htrace print [@var{start} [@var{len}]]
-Prints trace buffer, using current record configuration.
-
-@item htrace mode continuous
-Set continuous trace mode.
-
-@item htrace mode suspend
-Set suspend trace mode.
-
-@end table
-
@node PowerPC Embedded
@subsection PowerPC Embedded
--
1.7.7.6
^ permalink raw reply [flat|nested] 6+ messages in thread[parent not found: <1363700147.23712.277.camel@laria>]
* Re: [PATCH] Remove doc on OpenRISC 1000
[not found] ` <1363700147.23712.277.camel@laria>
@ 2013-03-20 10:10 ` Yao Qi
2013-03-20 13:33 ` Pedro Alves
0 siblings, 1 reply; 6+ messages in thread
From: Yao Qi @ 2013-03-20 10:10 UTC (permalink / raw)
To: jeremy.bennett; +Cc: gdb-patches, Franck Jullien
[My mail sent yesterday didn't show in the mail archive, so send it again.]
On 03/19/2013 09:35 PM, Jeremy Bennett wrote:
> It is quite likely the GDB code for OpenRISC 1000 was never submitted.
> The whole GNU tool chain was developed around 2000-2002, but only
> binutils ever committed its code. The tool chain is still widely used
> and maintained atwww.opencores.org.
Hi Jeremy,
The patch was submitted in the link I gave in my first mail, but only
the doc bit was approved and committed. I can't tell why the non-doc
bits were not approved.
>
> I've copied Franck Jullien, who is the most active developer of the
> OpenRISC GDB port at present (I was in the past). The alternative to
> deleting the documentation is to submit the port.
If the port can be submitted soon (in 2~3 months maybe?), I am fine to
keep the doc there, because it has been there for 10 years. Otherwise,
I prefer to remove them first, personally.
--
Yao (é½å°§)
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] Remove doc on OpenRISC 1000
2013-03-20 10:10 ` Yao Qi
@ 2013-03-20 13:33 ` Pedro Alves
2013-03-21 12:24 ` Franck Jullien
0 siblings, 1 reply; 6+ messages in thread
From: Pedro Alves @ 2013-03-20 13:33 UTC (permalink / raw)
To: Yao Qi; +Cc: jeremy.bennett, gdb-patches, Franck Jullien
On 03/20/2013 09:35 AM, Yao Qi wrote:
> [My mail sent yesterday didn't show in the mail archive, so send it again.]
>
> On 03/19/2013 09:35 PM, Jeremy Bennett wrote:
>> It is quite likely the GDB code for OpenRISC 1000 was never submitted.
>> The whole GNU tool chain was developed around 2000-2002, but only
>> binutils ever committed its code. The tool chain is still widely used
>> and maintained atwww.opencores.org.
>
> Hi Jeremy,
> The patch was submitted in the link I gave in my first mail, but only
> the doc bit was approved and committed. I can't tell why the non-doc
> bits were not approved.
>
>>
>> I've copied Franck Jullien, who is the most active developer of the
>> OpenRISC GDB port at present (I was in the past). The alternative to
>> deleting the documentation is to submit the port.
>
> If the port can be submitted soon (in 2~3 months maybe?), I am fine to
> keep the doc there, because it has been there for 10 years. Otherwise,
> I prefer to remove them first, personally.
I'd prefer removing them from our tree too (and not wait).
10 years have passed, and lots of non-"target remote" targets have
been yanked from the tree meanwhile -- I'm not familiar with OpenRISC,
but it's arguable whether we want a new "target jtag" nowadays,
compared to using the remote target (against something that talks jtag),
and perhaps we have better mechanisms for "info or1k spr" today
too (I don't know what that actually does).
I think starting from scratch with a clean submission, that
includes the corresponding docs would make a lot of sense.
--
Pedro Alves
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Remove doc on OpenRISC 1000
2013-03-20 13:33 ` Pedro Alves
@ 2013-03-21 12:24 ` Franck Jullien
2013-03-21 19:49 ` Jeremy Bennett
0 siblings, 1 reply; 6+ messages in thread
From: Franck Jullien @ 2013-03-21 12:24 UTC (permalink / raw)
To: Pedro Alves; +Cc: Yao Qi, jeremy.bennett, gdb-patches
2013/3/20 Pedro Alves <palves@redhat.com>:
> On 03/20/2013 09:35 AM, Yao Qi wrote:
>> [My mail sent yesterday didn't show in the mail archive, so send it again.]
>>
>> On 03/19/2013 09:35 PM, Jeremy Bennett wrote:
>>> It is quite likely the GDB code for OpenRISC 1000 was never submitted.
>>> The whole GNU tool chain was developed around 2000-2002, but only
>>> binutils ever committed its code. The tool chain is still widely used
>>> and maintained atwww.opencores.org.
>>
>> Hi Jeremy,
>> The patch was submitted in the link I gave in my first mail, but only
>> the doc bit was approved and committed. I can't tell why the non-doc
>> bits were not approved.
>>
>>>
>>> I've copied Franck Jullien, who is the most active developer of the
>>> OpenRISC GDB port at present (I was in the past). The alternative to
>>> deleting the documentation is to submit the port.
>>
>> If the port can be submitted soon (in 2~3 months maybe?), I am fine to
>> keep the doc there, because it has been there for 10 years. Otherwise,
>> I prefer to remove them first, personally.
>
> I'd prefer removing them from our tree too (and not wait).
> 10 years have passed, and lots of non-"target remote" targets have
> been yanked from the tree meanwhile -- I'm not familiar with OpenRISC,
> but it's arguable whether we want a new "target jtag" nowadays,
> compared to using the remote target (against something that talks jtag),
> and perhaps we have better mechanisms for "info or1k spr" today
> too (I don't know what that actually does).
>
> I think starting from scratch with a clean submission, that
> includes the corresponding docs would make a lot of sense.
>
> --
> Pedro Alves
>
Hi,
Our OpenRISC port is not ready yet. So, I think you're right.
You can remove the old openrisc documentation and we'll
start from scratch with a clean submission.
Franck.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Remove doc on OpenRISC 1000
2013-03-21 12:24 ` Franck Jullien
@ 2013-03-21 19:49 ` Jeremy Bennett
0 siblings, 0 replies; 6+ messages in thread
From: Jeremy Bennett @ 2013-03-21 19:49 UTC (permalink / raw)
To: gdb-patches
On 21/03/13 12:01, Franck Jullien wrote:
> 2013/3/20 Pedro Alves <palves@redhat.com>:
>> On 03/20/2013 09:35 AM, Yao Qi wrote:
>>> [My mail sent yesterday didn't show in the mail archive, so send it again.]
>>>
>>> On 03/19/2013 09:35 PM, Jeremy Bennett wrote:
>>>> It is quite likely the GDB code for OpenRISC 1000 was never submitted.
>>>> The whole GNU tool chain was developed around 2000-2002, but only
>>>> binutils ever committed its code. The tool chain is still widely used
>>>> and maintained atwww.opencores.org.
>>>
>>> Hi Jeremy,
>>> The patch was submitted in the link I gave in my first mail, but only
>>> the doc bit was approved and committed. I can't tell why the non-doc
>>> bits were not approved.
>>>
>>>>
>>>> I've copied Franck Jullien, who is the most active developer of the
>>>> OpenRISC GDB port at present (I was in the past). The alternative to
>>>> deleting the documentation is to submit the port.
>>>
>>> If the port can be submitted soon (in 2~3 months maybe?), I am fine to
>>> keep the doc there, because it has been there for 10 years. Otherwise,
>>> I prefer to remove them first, personally.
>>
>> I'd prefer removing them from our tree too (and not wait).
>> 10 years have passed, and lots of non-"target remote" targets have
>> been yanked from the tree meanwhile -- I'm not familiar with OpenRISC,
>> but it's arguable whether we want a new "target jtag" nowadays,
>> compared to using the remote target (against something that talks jtag),
>> and perhaps we have better mechanisms for "info or1k spr" today
>> too (I don't know what that actually does).
>>
>> I think starting from scratch with a clean submission, that
>> includes the corresponding docs would make a lot of sense.
>>
>> --
>> Pedro Alves
>>
>
> Hi,
>
> Our OpenRISC port is not ready yet. So, I think you're right.
> You can remove the old openrisc documentation and we'll
> start from scratch with a clean submission.
>
In the light of Pedro and Franck's comments, I agree. We should start
from scratch. The documentation doesn't even reflect reality -
proprietary JTAG interface has long gone from OpenRISC GDB. It has used
standard Remote Serial Protocol for a long time.
Jeremy
--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeId: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
Twitter: @embecosm
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Remove doc on OpenRISC 1000
2013-03-18 3:45 [PATCH] Remove doc on OpenRISC 1000 Yao Qi
[not found] ` <1363700147.23712.277.camel@laria>
@ 2013-03-22 1:40 ` Yao Qi
1 sibling, 0 replies; 6+ messages in thread
From: Yao Qi @ 2013-03-22 1:40 UTC (permalink / raw)
To: gdb-patches
On 03/18/2013 11:09 AM, Yao Qi wrote:
> gdb/doc:
>
> 2013-03-18 Yao Qi<yao@codesourcery.com>
>
> * gdb.texinfo (Embedded Processors): Remove menu item "OpenRISC 1000".
> (OpenRISC 1000): Remove.
Committed.
--
Yao (é½å°§)
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-03-22 1:00 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-18 3:45 [PATCH] Remove doc on OpenRISC 1000 Yao Qi
[not found] ` <1363700147.23712.277.camel@laria>
2013-03-20 10:10 ` Yao Qi
2013-03-20 13:33 ` Pedro Alves
2013-03-21 12:24 ` Franck Jullien
2013-03-21 19:49 ` Jeremy Bennett
2013-03-22 1:40 ` Yao Qi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox