Date: Sun, 17 May 2009 11:20:48 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: libhci update Message-ID: <1242555649.223847.3574.nullmailer@galant.ukfsn.org> In-Reply-To: <bb4a86c70905151021u2a42dd29m2edce0a011aba838@mail.gmail.com> References: <E1Lv5La-00058x-HH@smtpbarns01> <bb4a86c70904211651m6127745ao9d4f26c91e428994@mail.gmail.com> <1240386569.369073.696.nullmailer@galant.ukfsn.org> <bb4a86c70904220909j5d047ce6x6260bd2e87b5b7bd@mail.gmail.com> <1242294653.314348.1748.nullmailer@galant.ukfsn.org> <bb4a86c70905140926n488cb2b5x5f5530e01d70bd66@mail.gmail.com> <1242322384.832849.4269.nullmailer@galant.ukfsn.org> <bb4a86c70905141140u2b1662fdrf528c157d5fe7c2e@mail.gmail.com> <1242328962.345875.22296.nullmailer@galant.ukfsn.org> <1242335731.252131.19040.nullmailer@galant.ukfsn.org> <bb4a86c70905151021u2a42dd29m2edce0a011aba838@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Max, more queries - in bt_devany_cb() you should perhaps make sure that the device is an enabled one? - I'm thinking that bt_devopen() should have an options argument, in order to pre-set any options such as TIMESTAMP, DIRECTION etc (even NBIO) which will get around the differences in API for that (BlueZ had a weird thing with not supporting SOL_SOCKET, SO_TIMESTAMP even though Linux does I don't know if they fixed it yet) - in bt_devinquiry() we accept (dev == NULL) to mean any device, should that happen in bt_devopen() too? - along this line I wonder if it is possible open a promiscuous socket (eg as used by hcidump) instead of any particular device? (could be dev==NULL I guess, or a PROMISCUOUS option?) I'm not sure how Linux works but on NetBSD you must explicitly bind to 00:00:00:00:00:00 to get that behaviour (IIRC FreeBSD gives it to you by default but I was paranoid :) regards, iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1242555649.223847.3574.nullmailer>