Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 Feb 2009 10:01:03 -0800
From:      Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To:        Iain Hibbert <plunky@rya-online.net>
Cc:        "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org>
Subject:   Re: libhci
Message-ID:  <bb4a86c70902051001j53f52e3dhb2e80e393b936f16@mail.gmail.com>
In-Reply-To: <1233845167.798942.24919.nullmailer@galant.ukfsn.org>
References:  <1233365217.00068654.1233354838@10.7.7.3> <4988DCCC.80201@mavhome.dp.ua> <bb4a86c70902031622hdc5231g1c9ce33f17842a1e@mail.gmail.com> <4988EBAC.3080202@mavhome.dp.ua> <bb4a86c70902031731q83bf261s49e5812a3c208f81@mail.gmail.com> <1233758519.360141.162.nullmailer@galant.ukfsn.org> <bb4a86c70902041000t26ad9b66q94a32ff37cfb7f4b@mail.gmail.com> <1233845167.798942.24919.nullmailer@galant.ukfsn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 5, 2009 at 6:46 AM, Iain Hibbert <plunky@rya-online.net> wrote:
> On Wed, 4 Feb 2009, Maksim Yevmenkin wrote:
>
>> int hci_inquiry(...)
>>
>> and all the way down to the end of the file :) basically map dev_id to
>> unit numbers, i.e. dev_id 0 is "ubt0" node, etc.
>
> Well, I really dislike that dev_id method to start with. But anyway, I
> think they are working on a new API that is somewhat higher level and more
> related to the dbus access.

of course they are :) its linux :) they always working on something
new and improved :)

anyway, what would you suggest to use instead of dev_id? device name
(i.e. ubt0)? anything else? cant use bd_addr because (in freebsd at
least) device has to be "initialized" before bd_addr is known.

> Also, I think that looking at that code, it was written in the beginning
> and is full of 'good ideas' that somebody might want to use, but in
> reality much of it has no need to be in a shared library.
>
> hci_inquiry() is perhaps the only function that really needs to have a
> generic cross platform API and it would be nice if it was oriented towards
> application level rather than tied to a lower layer implementation.  I do
> not know what kind of API the Microsoft (Widcom?) or Apple stacks expose
> to applications for this, but I suspect they would be a better place to
> start.

i will take a look at ms api. but surely we have ability to send and
receive hci commands/events and enumerate all radios in the system in
addition to inquiry, dont you think?

thanks,
max



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70902051001j53f52e3dhb2e80e393b936f16>