In the past I got to know that motivation comes by streams,
I did not worry too much, and said to myself that it was just a matter of
waiting for the next stream. The problem is that it has been near 2 years of
non activity, awaiting for one of those streams to come.
Real life temptations, and the increasing responsibilities
during these years, have eclipsed the free
time. I always had backup plan, but the Economical situation in my country has
made think about having another back-up plan, of the backup plan.
And a third reason is some property I just acquired to accomplish
a life dream, which is taking all of the creativity remaining on me. It is a piece of
land in the mountain, with a ruin house where I am trying to build my little own
paradise. Much in the style of Frank Herbert (Dune writer), coexisting with nature and
environment converting a dry and abandoned place in such little paradise. This
is also explanation why this blog might change radically its topic.
Back in third quarter of 2006 after leaving yellowTAB and
Germany, kind of decided to leave the BeOS scene, but then I was back 1 year
later in 2007, writing a Bluetooth Stack. So it could happen again, I have been
and I will keep subscribed in mail lists, follow the news, reply questions and
offer all support I can. I’ll be around as I was up to now, just not likely
developing.
L2cap under network/protocols/l2cap: Provides socket interface to have l2cap channels. L2CAP offers connection oriented and connectionless sockets. But bluetooth stack as this point has no interchangeability with TCP/IP, A Higher level Bluetooth profile must be implemented
HCI under src/add-ons/kernel/bluetooth : Here we have 2 modules, one for handling global bluetooth data structures such as connection handles and L2cap channels, and frames
H2generic under src/add-ons/kernel/drivers/ bluetoothThe USB driver, implementing the H2 transport
Bluetooth kit under src/kit/bluetoothC++ implementation based on JSR82 apiBluetooth Server under src/servers/bluetoothBasically handling opened devices (local connected fisically in our system) and forwaring kit calls to them
Bluetooth Preferences under src/preferences/bluetooth
Configuration using the kit
Test applications under src/tests/kits/bluetooth
There is a small prototype component which is not here documented below
src/add-ons/bluetooth/ ResetLocalDevice. Its intention was to be an add-on of bluetooth preferences, So that new HCI commands could be customized by users or external developers. I did not like at the end the idea, I did not find the flexibility I wanted.
Whoever is interested can contact me and I can share more documentation such as roadmaps and TODOs.
Thank you all