delete target dbug/picobug/dink32/m32r/mon2000 ?

delete target dbug/picobug/dink32/m32r/mon2000 ?

[Pedro Alves]

All of these targets use gdb/monitor.c, which has bit rotted
years ago (I'd guess around ~6), and nobody seems to
have noticed.

I propose deleting them (along with monitor.c):

| target         | source               |
|----------------+----------------------|
| target dbug    | gdb/dbug-rom.c       |
| target picobug | gdb/microblaze-rom.c |
| target dink32  | gdb/dink32-rom.c     |
| target m32r    | gdb/m32r-rom.c       |
| target mon2000 | gdb/m32r-rom.c       |

Thanks,
Pedro Alves

Re: delete target dbug/picobug/dink32/m32r/mon2000 ?

[Stan Shebs]

On Wed, Jul 8, 2015 at 11:45 AM, Pedro Alves <palves@redhat.com> wrote:
> All of these targets use gdb/monitor.c, which has bit rotted
> years ago (I'd guess around ~6), and nobody seems to
> have noticed.
>
> I propose deleting them (along with monitor.c):
>
> | target         | source               |
> |----------------+----------------------|
> | target dbug    | gdb/dbug-rom.c       |
> | target picobug | gdb/microblaze-rom.c |
> | target dink32  | gdb/dink32-rom.c     |
> | target m32r    | gdb/m32r-rom.c       |
> | target mon2000 | gdb/m32r-rom.c       |


I agree, that's an infrastructure whose time has come and gone.  (Not
much call for traditional ROM monitors when one can just as easily
boot to a real OS instead!) We would see references to people using
monitor backends from time to time, but I haven't seen any mentions
(with either new or old GDBs) in several years.

Stan

Re: delete target dbug/picobug/dink32/m32r/mon2000 ?

[Joel Sherrill]

DINK32 was/is a free ROM monitor from Motorola
(now Freescale). I am not sure it is is available
or not. I haven't seen it in years personally.

I would expect microblaze-rom.c to be the newest user
of these.

I agree these are very likely dead.

--joel

On 7/8/2015 1:45 PM, Pedro Alves wrote:
> All of these targets use gdb/monitor.c, which has bit rotted
> years ago (I'd guess around ~6), and nobody seems to
> have noticed.
>
> I propose deleting them (along with monitor.c):
>
> | target         | source               |
> |----------------+----------------------|
> | target dbug    | gdb/dbug-rom.c       |
> | target picobug | gdb/microblaze-rom.c |
> | target dink32  | gdb/dink32-rom.c     |
> | target m32r    | gdb/m32r-rom.c       |
> | target mon2000 | gdb/m32r-rom.c       |
>
> Thanks,
> Pedro Alves
>

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

Re: delete target dbug/picobug/dink32/m32r/mon2000 ?

[Pedro Alves]

On 07/08/2015 08:09 PM, Joel Sherrill wrote:
> DINK32 was/is a free ROM monitor from Motorola
> (now Freescale). I am not sure it is is available
> or not. I haven't seen it in years personally.

Thanks.

> 
> I would expect microblaze-rom.c to be the newest user
> of these.

Yeah, seems like it, added in 2009.

TBC, I'm not suggesting to remove any architecture support.
It should still be fine to debug microblaze, m68k/CF, etc.
with "target remote".

> I agree these are very likely dead.

Thanks,
Pedro Alves

Re: delete target dbug/picobug/dink32/m32r/mon2000 ?

[Stan Shebs]

On Wed, Jul 8, 2015 at 12:09 PM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
> DINK32 was/is a free ROM monitor from Motorola
> (now Freescale). I am not sure it is is available
> or not. I haven't seen it in years personally.

Freescale still has it:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=DINK32&nodeId=0152109D3F

But I didn't see anything newer than 2010.

(The real truth of the situation is that I added the dink32 support
somewhat hastily in 1997, we were demo'ing PPC hardware at ESC that
year...)

Stan

Re: delete target dbug/picobug/dink32/m32r/mon2000 ?

[Michael Eager]

On 07/08/2015 12:26 PM, Pedro Alves wrote:
> On 07/08/2015 08:09 PM, Joel Sherrill wrote:
>> DINK32 was/is a free ROM monitor from Motorola
>> (now Freescale). I am not sure it is is available
>> or not. I haven't seen it in years personally.
>
> Thanks.
>
>>
>> I would expect microblaze-rom.c to be the newest user
>> of these.
>
> Yeah, seems like it, added in 2009.

Although I added microblaze-rom.c in 2009, it was something
I received from Xilinx and I know nothing about it.  I don't
know if anyone has used it.  Offhand, it looks like cruft --
there are register names which don't exist on the MicroBlaze
processor.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077