From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] can't connect EPOX Keyboard BT-KB01B
Date: Mon, 31 Jul 2006 19:13:08 +0200 [thread overview]
Message-ID: <20060731171308.GD29916@suse.de> (raw)
In-Reply-To: <1154369825.4982.12.camel@aeonflux.holtmann.net>
Hi,
On Mon, Jul 31, 2006 at 08:17:05PM +0200, Marcel Holtmann wrote:
> Hi Nils,
> =
> > Probably make it as default for hcidump and let "-X" and "-V" turn it o=
ff?
> =
> it is too late for that :(
> =
> Maybe at some point when I rewrite hcidump, but I don't see that happen
> in the near future.
maybe something like that helps a bit:
Index: src/hcidump.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/bluez/hcidump/src/hcidump.c,v
retrieving revision 1.69
diff -u -p -r1.69 hcidump.c
--- src/hcidump.c 17 Jan 2006 18:45:06 -0000 1.69
+++ src/hcidump.c 31 Jul 2006 17:10:19 -0000
@@ -827,6 +827,12 @@ int main(int argc, char *argv[])
}
}
=
+ if (!(flags & DUMP_VERBOSE && flags & DUMP_EXT)) {
+ fprintf (stderr, "Warning: if you want to use this tool to report "
+ "a problem, you should at least\n"
+ "run \"hcidump -X -V\".\n");
+ }
+
argc -=3D optind;
argv +=3D optind;
optind =3D 0;
:-)
(not even compile-tested)
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-07-31 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 8:33 [Bluez-users] can't connect EPOX Keyboard BT-KB01B Wolfram Reda
2006-07-29 12:57 ` Marcel Holtmann
2006-07-31 14:21 ` Nils Faerber
2006-07-31 18:17 ` Marcel Holtmann
2006-07-31 17:13 ` Stefan Seyfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 7:46 Wolfram Reda
2006-07-27 17:30 ` Bearcat M. Sandor
2006-07-27 17:43 ` Nils Faerber
2006-07-27 18:50 ` Wolfram Reda
2006-07-27 20:16 ` Bearcat M. Sandor
2006-07-28 1:22 ` Marcel Holtmann
2006-07-28 3:26 ` Bearcat M. Sandor
2006-07-28 7:21 ` Marcel Holtmann
2006-07-28 9:39 ` Nils Faerber
2006-07-28 9:46 ` Marcel Holtmann
2006-07-28 16:48 ` Bearcat M. Sandor
2006-07-28 18:21 ` Ulisses Furquim
2006-07-28 18:38 ` Bearcat M. Sandor
2006-07-29 6:35 ` Bearcat M. Sandor
2006-07-26 21:13 Wolfram Reda
2006-07-28 1:23 ` 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=20060731171308.GD29916@suse.de \
--to=seife@suse.de \
--cc=bluez-users@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.