Re: Bluetooth stack for FreeBSD (Netgraph)
Tobias, > > After a very long delay (sorry!) I'm pleased to announce that I'm still > around > > and new a snapshot can be downloaded from > > kickass! I will try it out later today :) > > Here is the list of things I'm planing to do next: > > > > o Prepare patches for FreeBSD source tree > > o Write SDP server. For now continue use Linux BlueZ SDP server. > > o Add support for SCO (voice/video) links > > o Better rc scripts > > o Think about non-Netgraph portable version > > I could take over the rc-script part if it'd be any help for you and > if it's not too urgent. tag! you are it :) i just would like to take this opportunity and share with you some ideas for rc scripts. what i would like to see is the system that allows you to configure common parameters for all Bluetooth devices. then for each individual device user should be able to provide overrides (if needed). the examples of such overrides are: - switch role for incoming connections (write_node_role_switch HCI command) - default page_scan_mode and page_scan_period_mode - default packet mask (write_node_packet_mask HCI command) - visible device name (change_local_name HCI command) - should device be visible (write_scan_enable HCI command) - etc. the problem here is how to identify the device. the name of the device (i.e. ubt0, btccc0) might not be good enough. what it tells you is device type and instance. one idea is to use device BD_ADDR, i.e. the script will do something like # 1 - common part (for all devices) reset read_bd_addr (and save it) read_local_supported_features read_buffer_size # 2- use device BD_ADDR to select set of user overrides and apply them here # ... # 3- common part (for all devices) initialize i hope that make sense. i also think all Bluetooth start/stop scritps should be executed by devd(8), usdb(8) etc. when device is attached/detached. the other part of the rc scripts is the Bluetooth services, i.e. things like sdpd, rfcomm_pppd, OBEX server etc. one problem here is that user might want to run server application on specific BD_ADDR and in this case device with that BD_ADDR must be attached (otherwise server application would not start). perhaps the list of servers should be attached to BD_ADDR as well? Note that it is fine to run server on ANY address. the server would start even if there is no device attached. thanks, max __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bluetooth stack for FreeBSD (Netgraph)
On Mon, Sep 08, 2003 at 12:45:03PM -0700, Maksim Yevmenkin wrote: > After a very long delay (sorry!) I'm pleased to announce that I'm still around > and new a snapshot can be downloaded from kickass! I will try it out later today [snip of long interesting list of enhancments] > Here is the list of things I'm planing to do next: > > o Prepare patches for FreeBSD source tree > o Write SDP server. For now continue use Linux BlueZ SDP server. > o Add support for SCO (voice/video) links > o Better rc scripts > o Think about non-Netgraph portable version I could take over the rc-script part if it'd be any help for you and if it's not too urgent. greets, t. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bluetooth stack for FreeBSD (Netgraph)
On Mon, 8 Sep 2003, Maksim Yevmenkin wrote: > Dear Hackers, > > After a very long delay (sorry!) I'm pleased to announce that I'm still around > and new a snapshot can be downloaded from > > http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030908.tar.gz Max, many thanks from a happy FreeBSD Bluetooth user! I'm going to try the new snapshot as soon as possible. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bluetooth stack for FreeBSD (Netgraph)
Dear Hackers, After a very long delay (sorry!) I'm pleased to announce that I'm still around and new a snapshot can be downloaded from http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030908.tar.gz Here is quick summary: o ng_hci(4) and ng_l2cap(4) kernel modules were changed to fix issue with Netgraph timeouts. Under some conditions it was possible to access data structure that was already free()d. o ng_ubt(4) module was changed to fix compilation issue on -current. o Implemented new libsdp. Linux BlueZ developers did not agree to re-release their code under BSD style licence, so I had to write libsdp. o Added new sdpcontrol(8) utility. This is an analog of sdptool utility from Linux BlueZ SDP package. o rfcomm_sppd(1), rfcomm_pppd(8) and obexapp(1) were changed and now can obtain RFCOMM channel via SDP from the server. The user still has an option to specify RFCOMM channel by hand. o hccontorol(8) utility now has four new commands: Read/Write_Page_Scan_Mode and Read/Write_Page_Scan_Period_Mode. o hcsecd(8) daemon now saves link keys on the disk. It is now not required to pair devices every time. o Few man pages were updated to document the changes. o All ports were updated to recent versions. o All Makefile's were updated. IMPORTANT: if you are building snapshot then you have to use # make -DSNAPSHOT depend # make -DSNAPSHOT # make -DSNAPSHOT install commands. Also you MUST build and install src/lib/libbluetooth and src/lib/libsdp first. Here is the list of things I'm planing to do next: o Prepare patches for FreeBSD source tree o Write SDP server. For now continue use Linux BlueZ SDP server. o Add support for SCO (voice/video) links o Better rc scripts o Think about non-Netgraph portable version Please give it a try and let me know if it workds for you. thanks, max __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bluetooth stack for FreeBSD
On Wed, Jun 04, 2003 at 09:32:32AM -0700, Maksim Yevmenkin wrote: > Dear Hackers, > > Another release is available for download at > > http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030604.tar.gz > > I am regret to announce that this is probably the last release. > My company has announced that they will pull out of USA and i > will most likely loose my job. > > Unless i find another position, i will be forced to return > back home. If anyone knows/wants to hire a H1B slave please > drop me a e-mail. I will consider any position within USA > or even Europe. > > I am *really* sorry :( I will try to do my best and support > the code, but i can not make any promises at this point. Awww :-( Someone should probably make you a committer so you can just update the Bluetooth code in FreeBSD as you feel like. ;-) Hey, thanks for all the good bluetooth work! -- Hiten ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bluetooth stack for FreeBSD
Dear Hackers, Another release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030604.tar.gz I am regret to announce that this is probably the last release. My company has announced that they will pull out of USA and i will most likely loose my job. Unless i find another position, i will be forced to return back home. If anyone knows/wants to hire a H1B slave please drop me a e-mail. I will consider any position within USA or even Europe. I am *really* sorry :( I will try to do my best and support the code, but i can not make any promises at this point. Below is a quick summary of changes: - new libbluetooth(3) that has routines to convert between names and BD_ADDRs (bt_gethostbyname, bt_gethostbyaddr etc). the library also supports convertion between PSMs and PSM names (bt_getprotobyname, bt_getprotobynumber) all configuration is stored in /etc/bluetooth/hosts and /etc/bluetooth/protocols files. see man pages for details - all userspace tools were updated and now you can specify hostnames instead of BD_ADDRs NOTE: please remove old libbluetooth.a and bluetooth.h files in /usr/local/include and /usr/local/lib before upgrade. - all man pages were updated (per Ruslan Ermilov) - all Makefiles were updates (per Ruslan Ermilov) - new man pages were added (hcsecd.conf, bluetooth.hosts, bluetooth.protocols etc). - default location of the hcsecd.conf file is now in /etc/bluetooth instead of /usr/local/bluetooth. - minor fix to the RFCOMM module (set priority field in PN message as required by TS 07 spec). thanks, max __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bluetooth stack for FreeBSD
On Thu, Mar 06, 2003 at 11:41:23AM -0800, Maksim Yevmenkin wrote: > Hello Christian, > > [...] > > >Are there any undertakings on the way to update the bluetooth code > >in -CURRENT to a newer snapshot? > > As soon as I get at least few positive feedbacks from the testers > Julian will commit it :) I do not feel comfortable to commit the > code that has only been tested on the limited set of devices I have. > > So I'll ask this again. Please try the new code and let me know if > it works for you. Pretty please with two sugar lumps on top :) > > thanks, > max > Great news :-) However, I can't test the code at the moment. My cell phone is bluetooth capable, but I don't have a bluetooth card yet. I was just interested because the -CURRENT sources haven't been updated for some time :-) - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Re: Bluetooth stack for FreeBSD
yes as soon as we get some +ve feedback about it.. i.e. if it works for you let us know and af we don't hear anything -ve and do hear +ve, we'll commit it :-) (Or rather I'll commit it for Maksim). On Thu, 6 Mar 2003, Christian Brueffer wrote: > > Are there any undertakings on the way to update the bluetooth code > in -CURRENT to a newer snapshot? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Hello Christian, [...] Are there any undertakings on the way to update the bluetooth code in -CURRENT to a newer snapshot? As soon as I get at least few positive feedbacks from the testers Julian will commit it :) I do not feel comfortable to commit the code that has only been tested on the limited set of devices I have. So I'll ask this again. Please try the new code and let me know if it works for you. Pretty please with two sugar lumps on top :) thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Wed, Mar 05, 2003 at 03:24:10PM -0800, Maksim Yevmenkin wrote: > > Dear Hackers, > > I'm very pleased to announce that another release is available for > download at > > http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz > > The Bluetooth sockets layer has been cleaned up. People should not > see any WITNESS complains with new code. Locking issues have been > revisited and code in much better shape now, although it probably > is not 100% SMP ready just yet. The code should work on SMP system > anyway because sockets layer is still under Giant. Minor bug in > OpenOBEX library has been fixed and OPEX Put-Empty command now works. > Also ng_ubt(4) now supports Wireless Transceiver for Bluetooth from > Microsoft. Thanks to Dustin Boontheekul <[EMAIL PROTECTED]> > for testing. > > IMPORTANT! > > Due to changes in API userland tools must be in sync with the kernel. > People should install new include files, recompile and reinstall all > userland tools as part of upgrade. I'm sorry about that. > > IMPORTANT! > > New taskqueue_swi_giant has been introduces recently in FreeBSD. > The socket code has been converted to use it. If you system is > not recent you will need > > 1) upgrade to recent -current > or > 2) change taskqueue_swi_giant to taskqueue_swi and compile code. > > People are advised to upgrade and try the new code. Please do ask > question and submit success stories/bug reports to me. Please also > CC to one the FreeBSD mailing lists (mobile, net or current) for > archive purposes. > > thanks, > max > Are there any undertakings on the way to update the bluetooth code in -CURRENT to a newer snapshot? - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0.pgp Description: PGP signature
Bluetooth stack for FreeBSD
Dear Hackers, I'm very pleased to announce that another release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz The Bluetooth sockets layer has been cleaned up. People should not see any WITNESS complains with new code. Locking issues have been revisited and code in much better shape now, although it probably is not 100% SMP ready just yet. The code should work on SMP system anyway because sockets layer is still under Giant. Minor bug in OpenOBEX library has been fixed and OPEX Put-Empty command now works. Also ng_ubt(4) now supports Wireless Transceiver for Bluetooth from Microsoft. Thanks to Dustin Boontheekul <[EMAIL PROTECTED]> for testing. IMPORTANT! Due to changes in API userland tools must be in sync with the kernel. People should install new include files, recompile and reinstall all userland tools as part of upgrade. I'm sorry about that. IMPORTANT! New taskqueue_swi_giant has been introduces recently in FreeBSD. The socket code has been converted to use it. If you system is not recent you will need 1) upgrade to recent -current or 2) change taskqueue_swi_giant to taskqueue_swi and compile code. People are advised to upgrade and try the new code. Please do ask question and submit success stories/bug reports to me. Please also CC to one the FreeBSD mailing lists (mobile, net or current) for archive purposes. thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Dear Hackers, I'm very pleased to announce that another engineering release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030210.tar.gz Note: This release has new tree layout that matches FreeBSD source tree. Quick summary of changes - New in-kernel RFCOMM implementation with SOCK_STREAM interface. The old user space implementation (rfcommd-1.1) is no longer required and is not included in this release. - Support for RFCOMM based DUN and LAN profiles. Note: DUN profile required patch for PPP. The patch was submitted to Brian Somers for review. In the mean time contact me if you want it. - OBEX support. This release includes simple OpenOBEX library based (included) client/server application. It supports both Object Push and File Transfer profiles. It is now possible to get phone book, calendar, pictures etc. from your cell phone. - SDP port has been upgraded to 1.0rc3 - share/examples/netgraph/bluetooth now has sample script that will setup your Bluetooth devices. - Minor bug fixes As usual all comments, bug reports and success stories are appreciated :) thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Dear Hackers, The next snapshot is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20021119.tar.gz Below is a quick summary of changes o Minor fixes for various man pages o Due to copyright issues firmware file has been removed from BT3C driver. Users must obtain firmware from 3COM Windows driver and use BT3CFW utility. o BT3CFW firmware download utility has been added o Couple new HCI socket ioctl() that allows to control default packet type and link modes for the device. o HCI security daemon that manages link keys and PIN codes has been added. Now it is possible to pair Bluetooth devices and setup authenticated and encrypted connections. Tested with 3COM card/stack and Ericsson T68 cell phone. o Link key format in hccontrol(8) tool has been changed. It now matches link key format in hcsecd(8), i.e. hex string of up to 16 bytes. Please give a try and let me know if it works for you. thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Mon, Sep 23, 2002 at 09:33:02AM -0700, Maksim Yevmenkin wrote: > > There is still an issue with USB stack in FreeBSD. It > still uses #define USB_USE_SOFTINTR. This causes major > impact on USB device performance. A little while ago > i have sent a patch but it got no response. > I didn't see that. You can talk directly to me about it if you want. Joe -- "As far as the laws of mathematics refer to reality, they are not certain; and as far as they are certain, they do not refer to reality." - Albert Einstein, 1921 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Hackers, Several people have contacted me and offered help with testing and i'm very glad to announce that i have received few successful reports. There was a couple of problems however. The next snapshot is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020922.tar.gz Below is a quick summary of changes - New USB device IDs o TDK Bluetooth USB dongle o MSI MS-6967 Bluetooth USB dongle o Mitsumi Bluetooth USB dongle (*) - New ports o SDP has been updated to latest version 0.8 o hcidump - HCI packet analyzer v1.3 has been ported from Linux BlueZ stack - New features o Bluetooth raw HCI sockets now support SO_TIMESTAMP option o Bluetooth raw HCI sockets now can tell direction (incoming or outgoing) for every HCI packet - Bug fixes o RFCOMM issues has been resolved and now both Xircom and 3Com stacks work (tested with Windows2000). Also i received successful report about interoperability with Widcomm stack on Windows XP o L2CAP interoperability issues with Nokia phone should be fixed now (**) There is still an issue with USB stack in FreeBSD. It still uses #define USB_USE_SOFTINTR. This causes major impact on USB device performance. A little while ago i have sent a patch but it got no response. thanks, max (*) Device has been recognized but failed to respond. Need more information. (**) I've not received report back yet, but i think it should be fixed now. I do not have Nokia phone, but i tested the patch with all other stacks. Please contact me if you still have a problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
> Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. Fry's Electronics in the SF bayarea has a bunch of bluetooth gadgets. Go to www.outpost.com and search for 'bluetooth'. USB adapters, pcmcia card, printer adapter, connectors for Palm and iPAQ etc. The printer adapter looks just like a standard paraller port connector with a RJ11 or RJ45 socket on one side (you can hook up a serial cable to it too). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Am Di, 2002-09-10 um 19.48 schrieb Julian Elischer: > > > > On Tue, 10 Sep 2002, Chris Dillon wrote: > > > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > > > I still would like to hear from people. I'm extremely surprised that > > > FreeBSD community seems not interested in this at all. I got very > > > few replies from few people (Julian Elischer, Terry Lambert - > > > thanks!) and that's it. > > *SNIP* > > > Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. > > Until it becomes more common all we can say is > "hey FreeBSD is there ahead of the crowd" :-) > I'm very happy too, and I do have hardware (VAIO and a t68) but no time right now. I'll do some tests ASAP! Thanks, -Harry > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Julian, > On Tue, 10 Sep 2002, Chris Dillon wrote: > > > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > > > I still would like to hear from people. I'm extremely surprised that > > > FreeBSD community seems not interested in this at all. I got very > > > few replies from few people (Julian Elischer, Terry Lambert - > > > thanks!) and that's it. > > > > I'm very interested, as are some other people I know, but we just > > don't have any bluetooth hardware to use yet. Don't think people > > don't care and thanks for the good work. :-) > > Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. Please :-) May i suggest to look at www.compusa.com and search for Bluetooth. Then try to look for the nearest store that has it. Prices <= $100. Yes, it is more expensive then 802.11. Yes, you can not do a lot with it right now, but Microsoft and Apple already claim support for Bluetooth. Yes, i know, "claim" does not mean much :-) > Until it becomes more common all we can say is > "hey FreeBSD is there ahead of the crowd" :-) Linux had Bluetooth stuff for almost a year now. Or may be even longer. People in Europe try to use Linux with Bluetooth for all sort of stuff, access points, printers, headset, phones you name it. Some even run in on iPAQ and Sharp Zaurus. Is that common for you? :-) I'm not trying to troll. You anyone wants to discuss it further, please, please, please take it off the list. thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Tue, 10 Sep 2002, Chris Dillon wrote: > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > I still would like to hear from people. I'm extremely surprised that > > FreeBSD community seems not interested in this at all. I got very > > few replies from few people (Julian Elischer, Terry Lambert - > > thanks!) and that's it. > > I'm very interested, as are some other people I know, but we just > don't have any bluetooth hardware to use yet. Don't think people > don't care and thanks for the good work. :-) Yes. we are aware of the work and we are pleased that it is hapenning, but few of us have even SEEN any bluetooth stuff yet.. certainly in the US it's not yet being marketted a lot. Until it becomes more common all we can say is "hey FreeBSD is there ahead of the crowd" :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On 10-Sep-2002 M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Chris Dillon <[EMAIL PROTECTED]> writes: >: On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: >: >: > I still would like to hear from people. I'm extremely surprised that >: > FreeBSD community seems not interested in this at all. I got very >: > few replies from few people (Julian Elischer, Terry Lambert - >: > thanks!) and that's it. >: >: I'm very interested, as are some other people I know, but we just >: don't have any bluetooth hardware to use yet. Don't think people >: don't care and thanks for the good work. :-) > > I know I'm interested in bluetooth, but have no space cycles in which > to help someone get something like this into the shape needed to > integrate it into the tree. I contacted Maksim off list. I can get limited access to a Bluetooth qualification lab. (out of hours etc.) and will try and get his stack tested against a number of other solutions. Duncan -- Duncan Barclay | God smiles upon the little children, [EMAIL PROTECTED] | the alcoholics, and the permanently stoned. [EMAIL PROTECTED]| Steven King To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
In message: <[EMAIL PROTECTED]> Chris Dillon <[EMAIL PROTECTED]> writes: : On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: : : > I still would like to hear from people. I'm extremely surprised that : > FreeBSD community seems not interested in this at all. I got very : > few replies from few people (Julian Elischer, Terry Lambert - : > thanks!) and that's it. : : I'm very interested, as are some other people I know, but we just : don't have any bluetooth hardware to use yet. Don't think people : don't care and thanks for the good work. :-) I know I'm interested in bluetooth, but have no space cycles in which to help someone get something like this into the shape needed to integrate it into the tree. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
FUJIMOTO Kou wrote: > > Poul-Henning Kamp wrote: > > > > In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes: > > > > >I still would like to hear from people. I'm extremely > > >surprised that FreeBSD community seems not interested in > > >this at all. I got very few replies from few people > > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > > > Most of us probably doesn't have any bluetooth hardware... > > I have a BT PCMCIA card by IBM, a BT USB adapter by MITSUMI, IBM PCMCIA card is not supported this time. If you can get spec. i will write a driver for it. In the mean time can you send card CIS dump to me? MITSUMI USB adapter is likely to work. I think it is a CSR/Bluecore based product (i.e. similar to 3Com USB dongle). But you will need to give me VendorID and ProductID so i can add it to the list of supported devices in "ubt.c". Just load "ugen" driver plug USB dongle and note vendor and product IDs. you also can get the same information via "usbdevs". > a C413S BT mobile phone by Sony, and a BT adapter for Sony CLIE. > A communication between CLIE/C413S and PC does not work properly > with Windows OS. Mobile phone and CLIE work well, because no > Windows needed and it's a Sony-to-Sony connection! sorry, but i have no clue about Bluetooth phones and handhelds. you've got to try it. i will try to do my best in helping you. > Anyway, I am willing to be a tester and you could find more ones > in Japan, because there're dozens of Bluetooth PCs and devices. great! thanks a lot! max. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > I still would like to hear from people. I'm extremely surprised that > FreeBSD community seems not interested in this at all. I got very > few replies from few people (Julian Elischer, Terry Lambert - > thanks!) and that's it. I'm very interested, as are some other people I know, but we just don't have any bluetooth hardware to use yet. Don't think people don't care and thanks for the good work. :-) -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, ARM, and S/390 under development - http://www.freebsd.org No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes: > > >I still would like to hear from people. I'm extremely > >surprised that FreeBSD community seems not interested in > >this at all. I got very few replies from few people > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > Most of us probably doesn't have any bluetooth hardware... I have a BT PCMCIA card by IBM, a BT USB adapter by MITSUMI, a C413S BT mobile phone by Sony, and a BT adapter for Sony CLIE. A communication between CLIE/C413S and PC does not work properly with Windows OS. Mobile phone and CLIE work well, because no Windows needed and it's a Sony-to-Sony connection! Sony is eager to introduce BT and there're several models of VAIO notebooks that have built-in BT interfaces. Anyway, I am willing to be a tester and you could find more ones in Japan, because there're dozens of Bluetooth PCs and devices. -- FUJIMOTO Kou, Tokyo Denki University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Mon, Sep 09, 2002 at 07:36:51PM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes: > > >I still would like to hear from people. I'm extremely > >surprised that FreeBSD community seems not interested in > >this at all. I got very few replies from few people > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > Most of us probably doesn't have any bluetooth hardware... Yuip, at least I don't have for sure. :( -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes: >I still would like to hear from people. I'm extremely >surprised that FreeBSD community seems not interested in >this at all. I got very few replies from few people >(Julian Elischer, Terry Lambert - thanks!) and that's it. Most of us probably doesn't have any bluetooth hardware... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Hackers, I'm very pleased to announce that another engineering release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz This release features several major changes and includes support for H4 UART and H2 USB transport layers, Host Controller Interface (HCI), Link Layer Control and Adaptation Protocol (L2CAP) and Bluetooth sockets layer. It also comes with several user space utilities that can be used to configure and test Bluetooth devices. Also there are several man pages. o HCI and L2CAP code bug fixes o Bluetooth sockets layer now supports raw HCI and L2CAP sockets and SEQPACKET L2CAP sockets. o SDP is now supported. I ported BlueZ-sdp-0.7 daemon, configuration tool and user space library. I also did basic interoperability testing with Linux (BlueZ) and Windows 2000 (3COM and Xircom stacks). It seems to work just fine. o RFCOMM is now supported. I ported old BlueZ-rfcommd-1.1 (no longer supported by BlueZ) daemon. This daemon provides RFCOMM service via pseudo ttys. It is not very useful for legacy applications, but i managed to run PPP over Bluetooth. I also did some basic interoperability testing with Linux (works) and Windows 2000 (Xircom stack - works, 3COM stack - does not work - crc errors). Note: this code isn't in very good shape and needs more cleanup and fixing. It still has some bugs. I still would like to hear from people. I'm extremely surprised that FreeBSD community seems not interested in this at all. I got very few replies from few people (Julian Elischer, Terry Lambert - thanks!) and that's it. As usual, i would like to invite any interested individuals to join the project and help me. thanks, max p.s. NetBSD folks seem to started work on Bluetooth too. http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/dev/bluetooth/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Julian, > I was just discussing this with people here at USENIX and I'd like to > start the process for committing this. Oh, gee, thanks :) but, i'm not so sure about committing. There are several important bits and pieces that needed to be done. First of all, i do want to see properly tested code with all documentation in the tree. I cannot say this about current snapshots. Things that MUST be fixed *before* commiting (IMO) sorted by priority - Documentation, examples & man pages - Multiple control hooks for HCI/L2CAP nodes - HCI/L2CAP tools > Do you think it deserves a separate directory under netgraph, > or maybe a netbluetooth directory. I'd rather not put it under netbluetooth, because it is a Netgraph specific code. It probably makes sense to put it somewhere under netgraph directory. > the documentation needs to be made 'commit-ready' too, as well as some > examples ready to put in /usr/share/examples/netgraph. yeah, i know... i really should spend some time and write all documentation. thanks, max __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Hackers, Another developer snapshot is available at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020613.tar.gz This release is for -current DP1 only. I had to downgrade back to DP1 due to huge amount of changes in -current. Brief list of changes - Basic support for USB devices. I got myself a 3Com USB Bluetooth dongle (aka ToothBrush :) - Make everything GCC 3.X friendly. - Minor bug fixes As always, i would like to get some feedback. I'm very interested to hear from people who familiar with FreeBSD kernel, Netgraph, Bluetooth and/or USB. thanks, max __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
On Tue, 16 Apr 2002, Maksim Yevmenkin wrote: > > initially all nodes were WRITERs to "release the stack", but then i > changed my strategy and now i'm serializing data at the edge of graph. > for example both "bt3c" and "h4" nodes will NG_HOOK_FORCE_WRITER on > upstream hook. also i probably should should turn WRITER bit on "ctl" > hook for HCI node since it accepts data. L2CAP node accepts whole > L2CAP packet from upstream hook, so (i think) it should be fine unless > these packets gets re-ordered somehow. protocols that run over L2CAP > may not like it. > > is it possible that SMP Netgraph can re-order data? if so then sockets > node probably should turn WRITER bit on downstream hooks too. it is not likely that data is re-ordered, but remember that data may enter the graph from different edge nodes simultaneously on different processors so that a single node may be processing both incoming and outgoing data at the same time unless the node itself is marked as needing a writer lock. > > > NG_NODE_PRIVATE(NG_HOOK_NODE(hook)) > > can be saved if you store information relavant to a hook in it's own > > private data pointer.. > > In some nodes I store the same data in NG_HOOK_PRIVATE(hook) > > as is in NG_NODE_PRIVATE(node), just to save the dereference > > if it's going to be done per packet. Sometimes there are better things to > > store there however.. > > i'm sorry, but i'm not sure what do you mean here. i use such calls > in several places (connect, disconnect, rcvdata) to get to the node > private structure, but (i think) it just a macros that expanded to a > couple pointer accesses. It's not a serious comment. just that you should be aware that one can sometimes simplify code by using the per-hook private information as well. > > > /* Detach mbuf, discard item and process data */ > > NGI_GET_M(item, m); > > NG_FREE_ITEM(item); > > > > If there is any chance that you will need a new 'item' in a function or a > > child function, then it's worth keeping them around to save teh expense of > > re-allocating them.. > > > > I guess I shuld make a macro NG_FWD_DATA_HOOK() to make this easier to > > do.. > > you right. i should not destroy item and use NG_FWD_ITEM_HOOK where > required. > Netgraph is not an unchangeable work.. If you have comments on things that may mek it easier to do what you need then please let us (archie & me) know.. > again thank you for your comments, i'm looking forward to hear more :) > thanks, > max > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Julian,
thanks for the comments, as always i found them very useful :)
i have combined both e-mail into one and included my answers
inline.
> ng_btsocket.c: unmodified: line 674
> sbappendrecord(&pcb->so->so_snd, m);
> m = m_dup(m, M_TRYWAIT);
> if (m == NULL) {
> error = ENOBUFS;
> goto drop1;
> }
>
> you are m_dup'ing an mbuf you have given away to the socket layer.
> on an SMP system this may already be destroyed by the time
> you do the m_dup() in fact if the sbappendrecord() fails
> due to a full queue, it may already be invalid...
fixed. thanks.
> also all functions should be 'prototype format'
> e.g.
> static int
> ng_btsocket_peeraddr(so, nam)
> struct socket*so;
> struct sockaddr **nam;
> {
> should be:
> static int
> ng_btsocket_peeraddr(struct socket *so, struct sockaddr **nam)
> {
>
> also:
> __P() is now "deprecated" and should not be used in new code.
i should read style(9) more often. i fixed my code.
> Your idea of making a special bluetooth socket type, implemented by
> a Netgraph node is interesting. Maybe we should it easier to do this
> by extending the netgraph socket type with the ability to
> make sockets of arbitrary types... i.e. register a node type that acts
> as a 'subtype' of the 'socket' type, and inherrits generic
> socket behaviour, but allow the 'child type' to specify
> other parts to replace normal behaviour.. I guess we would need to see a
> few more cases of this done before we could deduce what is
> likely to be a good candidate for abstraction.
i must admit that current socket implementation is a mess :(
my original plan was to use Netgraph sockets only and then
write several user space libraries to perform actual connection.
of course that idea had its own disadvantages. so i wrote
sockets layer. i will try to clean up it a little bit (remove
mutexes etc.) and also there probably should be support for HCI
and raw L2CAP sockets as well.
> you ask:
> /*
> * XXX FIXME/VERIFY i assume here that "hook" is a pointer
> * to the local hook we have received message from. For
> * L2CAP messages "hook" is required.
> */
>
> This is true for 5.0
> in 4.x there is no such thing as an arrival hook for a message.
> You should however not assume that it is non-NULL. test it in
> normal running code.. not in a KASSERT.
fixed.
> ok, read a bit more:
>
> []
>
> Any node that changes it's internal state with reception of DATA
> (as opposed to control messages) should ensure that it by doing:
> NG_NODE_FORCE_WRITER(node);
>
> This is because in the default state, multiple data messages may
> (under SMP) be transitting the node at a time, as they
> only take out READER locks. If DATA can change some state variable or
> similar then this becomes unsafe, and they should be serialised.
> If only SOME data can do this, you have the option to takew reader-locks
> and only after confirming that a message is a writer, upgrade to a writer
> lock by 'requeueing' it as such. Alternatively teh sender can mark a
> packet as 'writer'.
initially all nodes were WRITERs to "release the stack", but then i
changed my strategy and now i'm serializing data at the edge of graph.
for example both "bt3c" and "h4" nodes will NG_HOOK_FORCE_WRITER on
upstream hook. also i probably should should turn WRITER bit on "ctl"
hook for HCI node since it accepts data. L2CAP node accepts whole
L2CAP packet from upstream hook, so (i think) it should be fine unless
these packets gets re-ordered somehow. protocols that run over L2CAP
may not like it.
is it possible that SMP Netgraph can re-order data? if so then sockets
node probably should turn WRITER bit on downstream hooks too.
> NG_NODE_PRIVATE(NG_HOOK_NODE(hook))
> can be saved if you store information relavant to a hook in it's own
> private data pointer..
> In some nodes I store the same data in NG_HOOK_PRIVATE(hook)
> as is in NG_NODE_PRIVATE(node), just to save the dereference
> if it's going to be done per packet. Sometimes there are better things to
> store there however..
i'm sorry, but i'm not sure what do you mean here. i use such calls
in several places (connect, disconnect, rcvdata) to get to the node
private structure, but (i think) it just a macros that expanded to a
couple pointer accesses.
> /* Detach mbuf, discard item and process data */
> NGI_GET_M(item, m);
> NG_FREE_ITEM(item);
>
> If there is any chance that you will need a new 'item' in a function or a
> child function, then it's worth keeping them around to save teh expense of
> re-allocating them..
>
> I guess I shuld make a macro NG_FWD_DATA_HOOK() to make this easier to
> do..
you right. i should not destroy item and use NG_FWD_ITEM_HOOK where
required.
again thank you for your comments, i'm looking forward to hear more :)
thanks,
max
To Unsubscribe: send mail to
Re: Bluetooth stack for FreeBSD
On Mon, 15 Apr 2002, Julian Elischer wrote: > > [out of time for now.. will read more later] > > Julian > ok, read a bit more: you say: 2) Locking/SMP External code now uses ng_send_fn to inject data into Netgraph, so it should be fine as long as Netgraph is SMP safe. Just need to verify it. yes this is correct While Netgraph is not completely SMP safe yet, this is only because there are several nodes that do not do what you do here. By doing it corectly here you have ensured that this will not be one of the nodes that needs to be reworked when this becomes important. (soon). Any node that changes it's internal state with reception of DATA (as opposed to control messages) should ensure that it by doing: NG_NODE_FORCE_WRITER(node); This is because in the default state, multiple data messages may (under SMP) be transitting the node at a time, as they only take out READER locks. If DATA can change some state variable or similar then this becomes unsafe, and they should be serialised. If only SOME data can do this, you have the option to takew reader-locks and only after confirming that a message is a writer, upgrade to a writer lock by 'requeueing' it as such. Alternatively teh sender can mark a packet as 'writer'. --- NG_NODE_PRIVATE(NG_HOOK_NODE(hook)) can be saved if you store information relavant to a hook in it's own private data pointer.. In some nodes I store the same data in NG_HOOK_PRIVATE(hook) as is in NG_NODE_PRIVATE(node), just to save the dereference if it's going to be done per packet. Sometimes there are better things to store there however.. --- /* Detach mbuf, discard item and process data */ NGI_GET_M(item, m); NG_FREE_ITEM(item); If there is any chance that you will need a new 'item' in a function or a child function, then it's worth keeping them around to save teh expense of re-allocating them.. I guess I shuld make a macro NG_FWD_DATA_HOOK() to make this easier to do.. -- > > > > On Mon, 15 Apr 2002, Maksim Yevmenkin wrote: > > > Folks, > > > > [probably should be cc'd to -mobile as well] > > > > An engineering release of Bluetooth stack for -current FreeBSD > > is available for download at > > > > http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020415.tar.gz > > > > i'm interested to hear from people who familiar with FreeBSD > > kernel, Netgraph and/or Bluetooth. all your questions/comments/ > > suggestions are accepted and greatly appreciated. this is my > > first Netgraph stack, so please don't me hard :) > > > > thanks, > > max > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bluetooth stack for FreeBSD
Hi...
I have been reading the (well actually, "looking at"
may be more acurate..
some minor comments..
ng_btsocket.c: unmodified: line 674
sbappendrecord(&pcb->so->so_snd, m);
m = m_dup(m, M_TRYWAIT);
if (m == NULL) {
error = ENOBUFS;
goto drop1;
}
you are m_dup'ing an mbuf you have given away to the socket layer.
on an SMP system this may already be destroyed by the time
you do the m_dup() in fact if the sbappendrecord() fails
due to a full queue, it may already be invalid...
(I think)
also all functions should be 'prototype format'
e.g.
static int
ng_btsocket_peeraddr(so, nam)
struct socket*so;
struct sockaddr **nam;
{
should be:
static int
ng_btsocket_peeraddr(struct socket *so, struct sockaddr **nam)
{
also:
__P() is now "deprecated" and should not be used in new code.
Your idea of making a special bluetooth socket type, implemented by
a Netgraph node is interesting. Maybe we should it easier to do this
by extending the netgraph socket type with the ability to
make sockets of arbitrary types... i.e. register a node type that acts
as a 'subtype' of the 'socket' type, and inherrits generic
socket behaviour, but allow the 'child type' to specify
other parts to replace normal behaviour.. I guess we would need to see a
few more cases of this done before we could deduce what is
likely to be a good candidate for abstraction.
you ask:
/*
* XXX FIXME/VERIFY i assume here that "hook" is a pointer
* to the local hook we have received message from. For
* L2CAP messages "hook" is required.
*/
This is true for 5.0
in 4.x there is no such thing as an arrival hook for a message.
You should however not assume that it is non-NULL. test it in
normal running code.. not in a KASSERT. There are transitional moments
(during shutdown for example) when a message may arrive without a hook,
in fact a malicious user might force that to happen at any time by
simply send ing that message directly to the ID of the node.
For messages passed by a neighbour via a hokk the hook field will be
filled in but there are other ways that you may get a message.
[out of time for now.. will read more later]
Julian
On Mon, 15 Apr 2002, Maksim Yevmenkin wrote:
> Folks,
>
> [probably should be cc'd to -mobile as well]
>
> An engineering release of Bluetooth stack for -current FreeBSD
> is available for download at
>
> http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020415.tar.gz
>
> i'm interested to hear from people who familiar with FreeBSD
> kernel, Netgraph and/or Bluetooth. all your questions/comments/
> suggestions are accepted and greatly appreciated. this is my
> first Netgraph stack, so please don't me hard :)
>
> thanks,
> max
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Folks, [probably should be cc'd to -mobile as well] An engineering release of Bluetooth stack for -current FreeBSD is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020415.tar.gz i'm interested to hear from people who familiar with FreeBSD kernel, Netgraph and/or Bluetooth. all your questions/comments/ suggestions are accepted and greatly appreciated. this is my first Netgraph stack, so please don't me hard :) thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
