Hello David, Hope things are going well. Just resubmitted the patch, which should (hopefully) be correct this time around.
On another note, I noticed a minor bug in the memory_dump (x) command, is the procedure for opening an issue much different from that of a patch? Best, Tripp On Sun, Jul 26, 2026 at 12:50 AM Tripp R <[email protected]> wrote: > > > --- > Implemented the xb (examine block) command to print the contents of a > block device to the console. > > It is effectively a clone of the x/xp commands (examine memory / examine > physical memory), having the same arguments for those commands, > albeit preceded by the name of a block driver. > > e.g. usage > xd floppy0 /510c 0 > > Signed-off-by: Tripp R <[email protected]> > --- > hmp-commands.hx | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/hmp-commands.hx b/hmp-commands.hx > index db63b58a47..26b7cadcf2 100644 > --- a/hmp-commands.hx > +++ b/hmp-commands.hx > @@ -481,7 +481,7 @@ ERST > .name = "xb", > .args_type = "device:s, fmt:/,addr:l", > .params = "device /fmt addr", > - .help = "block memory dump starting at 'addr'", > + .help = "block memory dump starting at 'addr', in units of > bytes.", > .cmd = hmp_block_dump, > }, > > > --- > base-commit: bcc42fe49f7aae8982604900e307d783615bc79c > change-id: 20260726-xbhmpcmd-e8c82287a035 > > Best regards, > -- > Tripp R <[email protected]> > >
