Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

we grabbed old parts off the shelf

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

patched z80dasm to add support for z180 extended instructions needed to disassemble project rom

   * What was the outcome of this action?

a complete diassembly in less than a day and mild astonishment

   * What outcome did you expect instead?

much more work

*** End of the template - remove these template lines ***

Dear Ben,

thanks for your patch! I've merged it upstream with some changes.

I've made the output of Z180 instructions optional (it's now hidden
behind a command-line flag). One of the features of z80dasm is that its
output can be directly fed into z80asm to produce the same binary again.
Your original patch unfortunately broke that, since a Z80 assembler
doesn't know about Z180 instructions.

See "z180" branch in git repo at

https://www.tablix.org/~avian/git/z80dasm.git

What Z180 assembler do you use? I want to test the output of the patched
z80dasm against it.

Best regards
Tomaž

Hi Tomaž,

what is the status of this bug?

Am Sun, Mar 14, 2021 at 01:59:20PM +0100 schrieb Tomaž Šolc:

This repository vanished.  There is a repository at Github

https://github.com/lvitals/z80dasm/

which has a single commit and the codebase is the showing lots of
similarities, more files in src/ but no Makefile.*  I guess its some
older code.

Kind regards
   Andreas.

Dear Andreas,

Ben's patch has been merged with some refactoring into z80dasm 1.2.0
which was released around March 2023 and available from my website until
it went offline.

As far as I remember I never heard back from Ben so z180 functionaly has
only been tested as far as I could do it myself without a working
assembler to compare against.

Looking at git history I also did some work on getting 1.2.0 into Debian
back then, like fixing the build issue (#1105573). But then things happened.

Yes, it's a long story.

I still have everything that was on that server.

I do wish to bring some parts of my website back online, but with all
that's going on I can't say when or if I will be able to get to it.

I have no knowledge of this repository. This is not me.

Judging by the NEWS file it looks like someone uploaded the 1.2.0 source
.tar.gz release to github. I haven't checked if it has any other changes
on top of that.

Best regards
Tomaž

Dear Tomaž,

thank you for your answer.

Am Thu, Jul 23, 2026 at 10:13:50AM +0200 schrieb Tomaž Šolc:

This status update is helpful.  Thank you.  I would be very happy if we
could migrate the Debian packaging to salsa.debian.org.  This is
independent for what new home you might decide for your upstream code.

Good to know.

Using codeberg, gitlab or github coming to mind to simplify hosting it
on your own.

Thank you for the clarification.

Not sure whether you want to talk to that someone.  Some real Git
repository with the development history would probably be helpful.

I would like to follow this todo list:

  1. You create some new home with a downloadable tarball (either on
     those hosting platform or your own site)
  2. I would volunteer to create a Debian *packaging* Git on
     salsa.debian.org and will grant you push permissions.
     That way we can collaborative work on the Debian packaging.

What do you think?

Kind regards
    Andreas.

Dear Tomaž,

this is a kind ping asking for news about the latest upstream source.
It would be great to learn about your schedule.

Kind regards
    Andreas.

Am Thu, Jul 23, 2026 at 11:36:18AM +0200 schrieb Andreas Tille: