From: Marcel Holtmann <marcel@holtmann.org>
To: Till Harbaum <harbaum@beecon.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Little Hexdump-Patch for hcidump
Date: Thu, 26 Aug 2004 19:03:42 +0200 [thread overview]
Message-ID: <1093539822.2581.32.camel@pegasus> (raw)
In-Reply-To: <200408261844.20194.harbaum@beecon.de>
Hi Till,
> in every new release of hcidump i have been replacing the built-in
> hexdump routine with my own one (giving the address and ascii as well).
>
> Perhaps you want to use this replacement in hcidump/parser/parser.c
>
> The hex output is very useful for me and e.g. just being able to see ascii
> strings inside rfcomm payload is something i really often need.
>
> Feel free to include it into the public version if you like to ...
please send me a patch (diff -u) and adjust a little bit your coding
style to match the other sources of hcidump.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-26 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 12:45 [Bluez-devel] Bluez on Axis DevBoard 82 Peter Kjellerstedt
2004-08-26 16:44 ` [Bluez-devel] Little Hexdump-Patch for hcidump Till Harbaum
2004-08-26 17:03 ` Marcel Holtmann [this message]
2004-08-26 18:35 ` Till Harbaum
2004-08-26 19:20 ` Marcel Holtmann
[not found] ` <200408262230.37213.till@harbaum.org>
2004-08-26 22:26 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1093539822.2581.32.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=harbaum@beecon.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox