I was having serious issues with the HW of my former development machine where I started all the Bluetooth development(AMD K6-2 500MHz). NIC working but no Sound, freezing.. etc. So from the last code production I was dealing with Hardware around home to get something better. The current one was totally discarded. The first time I tried to build connecting the motherboard connectors the scene was:
- " Not working... but seems there is an orange debug LED informing about... oh oh.... this isn't a led but a burning resistor!!!!"
But well seems working, the resistor belonged to the sound system(although output works), I suspect was the joystick port. An AMD 1,3GHz 256RAM, not a big thing, even being my best machine, it does not contain even 4GB of hard disk joining 3 hard drives so getting whole Haiku tree is already impossible.
So this is the result of the testing/debug. At the moment after plugging the Bluetooth dongle as you can see the device is published in the devfs tree, not much, but took same time than writing this post, which make me feel happy about the code written till the moment, because these hooks are the core part of the driver.
Need to point that this is just a driver, there is a stack protocol waiting to be on the top of this driver (4 protocols to consider it as a basic bluetooth stack) HCI, L2CAP, RFCOMM, SDP). So whats this driver supporting? just usb-bluetooth dongles, nothing more. If you want to to use a bluetooth keyboard. I think the profile needed to be implemented is called BT-HID or similar.
Transfer files from your mobile phone? I think you need 2 more protocols (FP, OBEX) which rely on top of RFCOMM.
Bad news?
In other words... can we use the gtalk features of gmail in your browser with just a NIC driver? there are some things in the middle :) starting with a good browser...
Oh yeah... the soruces are safe... in the HD, a USB stick, some mail.... and of course, in the floopy.
No hay comentarios:
Publicar un comentario