From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 7 18:27:42 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19FF316A41F; Mon, 7 Nov 2005 18:27:42 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E7443D67; Mon, 7 Nov 2005 18:27:40 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA7IRQJ18890; Mon, 7 Nov 2005 13:27:27 -0500 Message-ID: <436F9C8B.1000300@savvis.net> Date: Mon, 07 Nov 2005 10:27:23 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yar Tikhiy References: <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051105113503.GA13863@comp.chem.msu.su> In-Reply-To: <20051105113503.GA13863@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 18:27:42 -0000 Yar Tikhiy wrote: > On Fri, Nov 04, 2005 at 02:26:53PM -0800, Maksim Yevmenkin wrote: > >>All, >> >>please find next revision of bluetooth-rc stuff at >> >>http://people.freebsd.org/~emax/bluetooth-rc-1.diff.txt >> >>in this revision i have moved all bluetooth configuration files under >>/etc/bluetooth. bluetooth.device.sample is now called 'default.conf' and >>file that contain device specific overrides called '$dev.conf' (i.e. >>'ubt0.conf'). >> >>so, '/etc/rc.d/bluetooth start $dev' does the following >> >>1) sets hardwired defaults (for backward compatibility) >> >>2) reads up /etc/bluetooth/default.conf (if any) >> >>3) reads up /etc/bluetooth/$dev.conf (if any) >> >>4) starts the stack >> >>even though /etc/bluetooth/{default,$dev}.conf are not exactly shell >>scripts they are still kinda like shell scripts :) these files should >>follow sh(1) syntax to set the variable, comments etc. >> >>the parser in bluetooth_read_conf() is very simple and value of a >>variable is still used in sh(1) eval. so one must be careful when >>editing these files. > > What about simplifying the inner parser code even more: > > case "$_line" in > ''|\#*) > ;; > *) > if expr "$_line" : "[a-zA-Z0-9_]*="; then > eval "${_namespace}${_line}" > else > ${logger} "Unable to parse line \"$_line\" in $_file" > return 1 > fi > ;; > esac sure. only need to if expr "$_line" : "[a-zA-Z0-9_]*=" > /dev/null 2>&1 ; then ... fi i do not really have any objection to this. since i already pass the value through eval i might as well pass the entire line. > BTW, couldn't just err() or warn() be used instead of ${logger}? i guess they could > And AFAIK stdin to a while loop can be redirected w/o enclosing > the loop in braces. sure, but it looked more clear (to me anyway) this way :) so does this look like something? http://people.freebsd.org/~emax/bluetooth-rc-2.diff.txt any other comments, suggestions, objections? please speak. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 7 20:01:01 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51DF716A420; Mon, 7 Nov 2005 20:01:01 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A1C43D5F; Mon, 7 Nov 2005 20:00:57 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jA7K0eHF007832; Mon, 7 Nov 2005 12:00:40 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jA7K0eqB007831; Mon, 7 Nov 2005 12:00:40 -0800 Date: Mon, 7 Nov 2005 12:00:40 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051107200040.GB29473@odin.ac.hmc.edu> References: <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DBIVS5p969aUjpLe" Content-Disposition: inline In-Reply-To: <436BE02D.2020404@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org, Yar Tikhiy Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 20:01:01 -0000 --DBIVS5p969aUjpLe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 04, 2005 at 02:26:53PM -0800, Maksim Yevmenkin wrote: > All, >=20 > please find next revision of bluetooth-rc stuff at >=20 > http://people.freebsd.org/~emax/bluetooth-rc-1.diff.txt >=20 > in this revision i have moved all bluetooth configuration files under=20 > /etc/bluetooth. bluetooth.device.sample is now called 'default.conf' and= =20 > file that contain device specific overrides called '$dev.conf' (i.e.=20 > 'ubt0.conf'). >=20 > so, '/etc/rc.d/bluetooth start $dev' does the following >=20 > 1) sets hardwired defaults (for backward compatibility) >=20 > 2) reads up /etc/bluetooth/default.conf (if any) I think /etc/defaults/bluetooth.device.conf might be better since we do have a defined location of default files and this will discourge people from messing with them. > 3) reads up /etc/bluetooth/$dev.conf (if any) > > 4) starts the stack >=20 > even though /etc/bluetooth/{default,$dev}.conf are not exactly shell=20 > scripts they are still kinda like shell scripts :) these files should=20 > follow sh(1) syntax to set the variable, comments etc. >=20 > the parser in bluetooth_read_conf() is very simple and value of a=20 > variable is still used in sh(1) eval. so one must be careful when=20 > editing these files. >=20 > is this looks like something? i also could write=20 > bluetooth.device.conf(5) man page that describes the parameters as well= =20 > as the syntax of the files. A bluetooth.device.conf(5) man page would be a good idea, though the example file is quite good. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --DBIVS5p969aUjpLe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDb7JnXY6L6fI4GtQRAuApAKC6XhPvWzU55oJk66DRUCx9qP7IfwCeNkkg qYfoTNfhx895GnVTkdp5aGY= =4m9P -----END PGP SIGNATURE----- --DBIVS5p969aUjpLe-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 07:01:08 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0224E16A41F for ; Tue, 8 Nov 2005 07:01:08 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB25D43D49 for ; Tue, 8 Nov 2005 07:01:06 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EZNTY-0000QT-SN; Tue, 08 Nov 2005 10:01:00 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <4353DBBC.2000508@savvis.net> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 08 Nov 2005 10:00:59 +0300 Message-Id: <1131433259.1164.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 07:01:08 -0000 =F7 =D0=CE, 17/10/2005 =D7 10:13 -0700, Maksim Yevmenkin =D0=C9=DB=C5=D4: > Panagiotis, >=20 > it appears i have missed your original email :( not a big problem - i > have found it in the archive. please read my comments inline. >=20 > >> I've been playing with integrating the bluetooth subsystem into our > >> rc.d infrastructure and I'd like to submit the results of my > >> efforts for review. My testing has been centered around my USB > >> bluetooth dongle and I know that it works, but I suppose other > >> bluetooth devices should work as well. I have taken the existing > >> rc.bluetooth script (that is not installed by default) and > >> converted it to rc.d, renaming it as 'bluetooth'. I also added a > >> couple of other scripts for hcsecd and sdpd, that are started from > >> bluetooth, but can also function independently, id so desired. > >> Finally I have added a devd configuration file that makes sure the > >> bluetooth script gets started on insertion and removal of the USB > >> dongle. >=20 > that is great. thanks for doing the work! it seems we have been working=20 > on this in parallel :) about a week ago i have committed (into -current)=20 > hcsecd(8) and sdpd(8) rc.d scripts. they are very similar to what you=20 > have done. please see >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/hcsecd >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/sdpd >=20 > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf >=20 > for more details. >=20 > >> With these changes, when I plug in my USB bluetooth dongle, all the > >> necessary initialization happens behind the scenes and I can start > >> using my bluetooth peripherals right away. When I unplug the dongle > >> all the services stop and the necessary shutdown operations are > >> performed on the bluetooth stack. There is still some work left, > >> like specifying different flags for sdpd & hcsecd, but the defaults > >> work fine. >=20 > that sounds just fine. once again - do not worry about hcsecd(8) and=20 > sdpd(8) scripts anymore - they are done. >=20 > >> In order to test this stuff you have to: > >>=20 > >> - copy bluetooth, hcsecd and sdpd into /etc/rc.d - copy ubt.conf > >> into /usr/local/etc/devd (creating it if necessary), or add its > >> contents to /etc/devd.conf - add a line in /etc/rc.conf with:=20 > >> bluetooth_enable=3D"YES" > >>=20 > >> In an eventual merge into the base system the devd configuration > >> should be merged into /etc/devd.conf and /etc/defaults/rc.conf > >> should contain the following line instead: bluetooth_enable=3D"NO" > >>=20 > >> I'd appreciate any comments you may have. >=20 > devd(8) configuration (ubt.conf) looks fine. i can merge this info=20 > devd.conf for you. hcsecd(8) and sdpd(8) already committed into=20 > -current. i have also created bluetooth section in the=20 > /etc/defaults/rc.conf file. >=20 > i have few comments about my original rc.bluetooth script. >=20 > 1) it probably should not load any kernel modules. the problem is that=20 > when one (or more) bluetooth kernel modules compiled into the kernel the=20 > kldstat(8) check may fail. this has to do with the way kldstat(8) prints=20 > the results and the way rc.bluetooth grep's through them. >=20 > 2) original rc.bluetooth is very rigid. things like device name, device=20 > class, etc. are hardwired into the script. so i'd like to have a bit of=20 > flexibility here, i.e. ability to specify per device >=20 > - device name (change_local_name) >=20 > - device class (write_class_of_device) >=20 > - should device be "visible"/discoverable by default (write_scan_enable) >=20 > - should device request authentication (write_authentication_enable) >=20 > - should device use encryption (write_encryption_enable) >=20 > - should device request role switch (write_node_role_switch) >=20 > and maybe few others. >=20 > 3) i'd like to have some way to execute a few hccontrol(8) commands=20 > after default setup was done. perhaps this could be done with some sort=20 > of bluetooth.local rc.d script that will be executed after main script.=20 > by default it should be empty. another way to do it is to have something=20 > along the bluetooth_extra_commands variable in rc.conf. >=20 > > Great ! It just works, Thank you. > >=20 > > I've added bthidd script (in attachment) to start human interface > > daemon (bt mouse in my case). After recent upgrade of 7-CURRENT I have do not working bthidd. Something bad on boot here. bthidd just not started or failed on boot. If I just turn off and then turn on USB bt dongle - it starts work. No any related messages in /var/log/messages. I have=20 bluetooth_enable=3D"YES" bthidd_enable=3D"YES" in /etc/rc.conf and=20 % cat /usr/local/etc/devd/ubt.conf=20 # When a USB Bluetooth dongle appears, start the bluetooth subsystem. attach 100 { device-name "ubt[0-9]+"; action "/etc/rc.d/bluetooth start $device-name"; }; detach 100 { device-name "ubt[0-9]+"; action "/etc/rc.d/bluetooth stop $device-name"; }; % Does anybody has working on boot bthidd with recent scripts ?=20 > thanks, > max --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 18:02:27 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5084916A41F for ; Tue, 8 Nov 2005 18:02:27 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBE9543D67 for ; Tue, 8 Nov 2005 18:02:26 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA8I2GJ17933; Tue, 8 Nov 2005 13:02:23 -0500 Message-ID: <4370E826.7090007@savvis.net> Date: Tue, 08 Nov 2005 10:02:14 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> In-Reply-To: <1131433259.1164.7.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 18:02:27 -0000 Vladimir, [...] > After recent upgrade of 7-CURRENT I have do not working bthidd. > > Something bad on boot here. bthidd just not started or failed on boot. > If I just turn off and then turn on USB bt dongle - it starts work. > > No any related messages in /var/log/messages. _nothing_ has changed in bluetooth code and i have _not_ committed any rc.d bluetooth scripts, so it must be something wrong with your setup. which bluetooth rc.d scripts are you using? original (posted by Panagiotis) or mine? [...] > Does anybody has working on boot bthidd with recent scripts ? once more bthidd(8) is _not_ connected to the build and _not_ installed by default. this is still work in progress. once bthid(8) is finished it will be connected to the build and installed by default. at this point we will integrate it into rc.d. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 18:13:17 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A9DA16A41F; Tue, 8 Nov 2005 18:13:17 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC5C643D49; Tue, 8 Nov 2005 18:13:16 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA8IDAJ18234; Tue, 8 Nov 2005 13:13:14 -0500 Message-ID: <4370EAB4.8090000@savvis.net> Date: Tue, 08 Nov 2005 10:13:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> In-Reply-To: <20051107200040.GB29473@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org, Yar Tikhiy , freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 18:13:17 -0000 Brooks, >>please find next revision of bluetooth-rc stuff at >> >>http://people.freebsd.org/~emax/bluetooth-rc-1.diff.txt >> >>in this revision i have moved all bluetooth configuration files under >>/etc/bluetooth. bluetooth.device.sample is now called 'default.conf' and >>file that contain device specific overrides called '$dev.conf' (i.e. >>'ubt0.conf'). >> >>so, '/etc/rc.d/bluetooth start $dev' does the following >> >>1) sets hardwired defaults (for backward compatibility) >> >>2) reads up /etc/bluetooth/default.conf (if any) > > I think /etc/defaults/bluetooth.device.conf might be better since we do > have a defined location of default files and this will discourge people > from messing with them. that is fine with me. i'm sorry this is taking so long :) now the last question: should we keep device specific files under /etc/bluetooth or just under /etc? right now i have devfs.rules, pccard.conf, periodic.conf and rc.conf under /etc/defaults. overrides for these go into /etc. another alternative (which probably no one is going to like) is to use /etc/bluetooth/defaults/device.conf (defaults) and /etc/bluetooth/$dev.conf files (overrides). >>3) reads up /etc/bluetooth/$dev.conf (if any) >> >>4) starts the stack >> >>even though /etc/bluetooth/{default,$dev}.conf are not exactly shell >>scripts they are still kinda like shell scripts :) these files should >>follow sh(1) syntax to set the variable, comments etc. >> >>the parser in bluetooth_read_conf() is very simple and value of a >>variable is still used in sh(1) eval. so one must be careful when >>editing these files. >> >>is this looks like something? i also could write >>bluetooth.device.conf(5) man page that describes the parameters as well >>as the syntax of the files. > > A bluetooth.device.conf(5) man page would be a good idea, though the > example file is quite good. agreed. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 18:32:13 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D925016A41F; Tue, 8 Nov 2005 18:32:13 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2CBA43D45; Tue, 8 Nov 2005 18:32:12 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jA8IW4ME041059; Tue, 8 Nov 2005 21:32:05 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jA8IW4PL041058; Tue, 8 Nov 2005 21:32:04 +0300 (MSK) (envelope-from yar) Date: Tue, 8 Nov 2005 21:32:04 +0300 From: Yar Tikhiy To: Maksim Yevmenkin Message-ID: <20051108183203.GA40364@comp.chem.msu.su> References: <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051105113503.GA13863@comp.chem.msu.su> <436F9C8B.1000300@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436F9C8B.1000300@savvis.net> User-Agent: Mutt/1.5.9i Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 18:32:14 -0000 On Mon, Nov 07, 2005 at 10:27:23AM -0800, Maksim Yevmenkin wrote: > Yar Tikhiy wrote: > > if expr "$_line" : "[a-zA-Z0-9_]*=" > /dev/null 2>&1 ; then > ... > fi > > i do not really have any objection to this. since i already pass the > value through eval i might as well pass the entire line. And so the users will be able to use basic sh(1) tricks in the lines. > >And AFAIK stdin to a while loop can be redirected w/o enclosing > >the loop in braces. > > sure, but it looked more clear (to me anyway) this way :) Hmmm, I'm unsure if it worked at all ;-) In sh(1) you need to place a ';' before '}' if there is no '\n' after the last command in braces. That is, the sh(1) syntax dictates that you can write { command1; command2; } or { command1 command2 } but not { command1 command2 } In the last case '}' will be passed as an argument to command2 and shell will croak on brace mismatch. For some reason '}' behaves like a command itself in sh(1), unlike ')'. -- Yar From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 18:47:19 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB55916A420; Tue, 8 Nov 2005 18:47:19 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 665A043D46; Tue, 8 Nov 2005 18:47:17 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA8Il2J19033; Tue, 8 Nov 2005 13:47:02 -0500 Message-ID: <4370F2A3.8060808@savvis.net> Date: Tue, 08 Nov 2005 10:46:59 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yar Tikhiy References: <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051105113503.GA13863@comp.chem.msu.su> <436F9C8B.1000300@savvis.net> <20051108183203.GA40364@comp.chem.msu.su> In-Reply-To: <20051108183203.GA40364@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 18:47:20 -0000 Yar, >>if expr "$_line" : "[a-zA-Z0-9_]*=" > /dev/null 2>&1 ; then >>... >>fi >> >>i do not really have any objection to this. since i already pass the >>value through eval i might as well pass the entire line. > > And so the users will be able to use basic sh(1) tricks in the lines. depending on one's position it may or may not be a good thing :) >>>And AFAIK stdin to a while loop can be redirected w/o enclosing >>>the loop in braces. >> >>sure, but it looked more clear (to me anyway) this way :) > > Hmmm, I'm unsure if it worked at all ;-) In sh(1) you need to > place a ';' before '}' if there is no '\n' after the last command > in braces. That is, the sh(1) syntax dictates that you can write it works. i tried these patches on my system. also there is a similar code in /etc/rc.subr (please see devfs_rulesets_from_file() function). but if it make sh(1) purists uncomfortable i certainly can change it :) thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 20:12:17 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E78D416A420 for ; Tue, 8 Nov 2005 20:12:16 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EBC043D46 for ; Tue, 8 Nov 2005 20:12:15 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EZZ24-0000Vj-T5; Tue, 08 Nov 2005 22:21:24 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <4370E826.7090007@savvis.net> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> <4370E826.7090007@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 08 Nov 2005 22:21:23 +0300 Message-Id: <1131477683.1231.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 20:12:17 -0000 =F7 =D7=D4, 08/11/2005 =D7 10:02 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: > Vladimir, >=20 > [...] >=20 > > After recent upgrade of 7-CURRENT I have do not working bthidd. > >=20 > > Something bad on boot here. bthidd just not started or failed on boot. > > If I just turn off and then turn on USB bt dongle - it starts work. > >=20 > > No any related messages in /var/log/messages. >=20 > _nothing_ has changed in bluetooth code and i have _not_ committed any=20 > rc.d bluetooth scripts, so it must be something wrong with your setup.=20 > which bluetooth rc.d scripts are you using? original (posted by=20 > Panagiotis) or mine? Original. Nothing changed in my setup except=20 make world && mergemaster Probably something wrong with drivers, I've notice that ng bluetooth mice is disconnected without any notice. Reconnecting usb bluetooth device lead to following error: ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0= x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) And after that error bt stack does not work until reboot, reconnecting dongle does not helps. Boot scenario was: booting ... ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0= x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 Timecounter "TSC" frequency 1686969804 Hz quality 800 ... Trying to mount root from ufs:/dev/ad0s4a WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() WARNING: attempt to net_add_domain(netgraph) after domainfinalize() ... there bthidd started but does not connect mice. I have turned on-board bt off, then on by notebook switch. kernel printed: ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfe= r will be submitted! ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer= will be submitted! ubt0: at uhub2 port 2 (addr 2) disconnected ubt0: detached ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0= x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3;= wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 kbd2 at vkbd0 BT mice start work here. after some hours of work it stop moving and l2pings also. Trying restart BT stack lead to error:=20 ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: ALPS UGX, rev 1.10/7.81, addr 2 ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0= x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) as all following tries It was much better before. (I am using this mice for long time). > [...] >=20 > > Does anybody has working on boot bthidd with recent scripts ?=20 >=20 > once more bthidd(8) is _not_ connected to the build and _not_ installed=20 > by default. this is still work in progress. once bthid(8) is finished it=20 > will be connected to the build and installed by default. at this point=20 > we will integrate it into rc.d. Ok, so we are talking only about posted here scripts. > thanks, > max --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 20:15:34 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C98D616A41F for ; Tue, 8 Nov 2005 20:15:34 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E5E43D49 for ; Tue, 8 Nov 2005 20:15:28 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EZZsH-0000NL-UO; Tue, 08 Nov 2005 23:15:21 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <1131477683.1231.12.camel@localhost> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> <4370E826.7090007@savvis.net> <1131477683.1231.12.camel@localhost> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 08 Nov 2005 23:15:21 +0300 Message-Id: <1131480921.1155.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 20:15:34 -0000 =F7 =D7=D4, 08/11/2005 =D7 22:21 +0300, Vladimir Grebenschikov =D0=C9=DB=C5= =D4: > =F7 =D7=D4, 08/11/2005 =D7 10:02 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: > > Vladimir, > >=20 > > [...] > >=20 > > > After recent upgrade of 7-CURRENT I have do not working bthidd. > > >=20 > > > Something bad on boot here. bthidd just not started or failed on boot= . > > > If I just turn off and then turn on USB bt dongle - it starts work. > > >=20 > > > No any related messages in /var/log/messages. > >=20 > > _nothing_ has changed in bluetooth code and i have _not_ committed any=20 > > rc.d bluetooth scripts, so it must be something wrong with your setup.=20 > > which bluetooth rc.d scripts are you using? original (posted by=20 > > Panagiotis) or mine? >=20 > Original. > Nothing changed in my setup except=20 > make world && mergemaster I have found the reason, it was really after make world After turning off console pixel-mode I've see: ... Starting devd. WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() bthidd not running? WARNING: attempt to net_add_domain(netgraph) after domainfinalize() BD_ADDR: 08:00:46:ca:e2:7a Features: 0xff 0xff 0xf 00 00 00 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 192 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 Starting bthidd. /libexec/ld-elf.so.1: Shared object "libbluetooth.so.1" not found, required= by " bthidd" ... After rebuilding bthidd and bthidcontrol it start work. But, I still does understand why it starts ok with manual start after boot. > Probably something wrong with drivers, I've notice that ng bluetooth > mice is disconnected without any notice. >=20 > Reconnecting usb bluetooth device lead to following error: > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x= 3; > wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) >=20 > And after that error bt stack does not work until reboot, reconnecting > dongle does not helps. >=20 > Boot scenario was: > booting > ... > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x= 3; > wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > Timecounter "TSC" frequency 1686969804 Hz quality 800 > ... > Trying to mount root from ufs:/dev/ad0s4a > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > ... > there bthidd started but does not connect mice. >=20 > I have turned on-board bt off, then on by notebook switch. > kernel printed: > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new x= fer will be submitted! > ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xf= er will be submitted! > ubt0: at uhub2 port 2 (addr 2) disconnected > ubt0: detached > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x= 3; wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > kbd2 at vkbd0 >=20 > BT mice start work here. > after some hours of work it stop moving and l2pings also. >=20 > Trying restart BT stack lead to error:=20 > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x= 3; > wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) >=20 > as all following tries >=20 > It was much better before. (I am using this mice for long time). >=20 >=20 > > [...] > >=20 > > > Does anybody has working on boot bthidd with recent scripts ?=20 > >=20 > > once more bthidd(8) is _not_ connected to the build and _not_ installed= =20 > > by default. this is still work in progress. once bthid(8) is finished i= t=20 > > will be connected to the build and installed by default. at this point=20 > > we will integrate it into rc.d. >=20 > Ok, so we are talking only about posted here scripts. >=20 > > thanks, > > max --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@swsoft.com From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 20:16:37 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 515E816A41F; Tue, 8 Nov 2005 20:16:37 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id E915743D46; Tue, 8 Nov 2005 20:16:36 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jA8KGLTI006201; Tue, 8 Nov 2005 12:16:21 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jA8KGKiF006200; Tue, 8 Nov 2005 12:16:20 -0800 Date: Tue, 8 Nov 2005 12:16:20 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051108201620.GD27091@odin.ac.hmc.edu> References: <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4370EAB4.8090000@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Brooks Davis , freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, Yar Tikhiy Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 20:16:37 -0000 On Tue, Nov 08, 2005 at 10:13:08AM -0800, Maksim Yevmenkin wrote: > Brooks, > > >>please find next revision of bluetooth-rc stuff at > >> > >>http://people.freebsd.org/~emax/bluetooth-rc-1.diff.txt > >> > >>in this revision i have moved all bluetooth configuration files under > >>/etc/bluetooth. bluetooth.device.sample is now called 'default.conf' and > >>file that contain device specific overrides called '$dev.conf' (i.e. > >>'ubt0.conf'). > >> > >>so, '/etc/rc.d/bluetooth start $dev' does the following > >> > >>1) sets hardwired defaults (for backward compatibility) > >> > >>2) reads up /etc/bluetooth/default.conf (if any) > > > >I think /etc/defaults/bluetooth.device.conf might be better since we do > >have a defined location of default files and this will discourge people > >from messing with them. > > that is fine with me. i'm sorry this is taking so long :) now the last > question: should we keep device specific files under /etc/bluetooth or > just under /etc? right now i have devfs.rules, pccard.conf, > periodic.conf and rc.conf under /etc/defaults. overrides for these go > into /etc. > > another alternative (which probably no one is going to like) is to use > /etc/bluetooth/defaults/device.conf (defaults) and > /etc/bluetooth/$dev.conf files (overrides). I think they should go in /etc/bluetooth/$dev.conf and the defults should go in /etc/defaults. The per-device files should not go directly in /etc because there is more that one of them. -- Brooks From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 21:27:22 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6919A16A41F for ; Tue, 8 Nov 2005 21:27:22 +0000 (GMT) (envelope-from cr0t@bk.ru) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAEB743D49 for ; Tue, 8 Nov 2005 21:27:15 +0000 (GMT) (envelope-from cr0t@bk.ru) Received: from [83.149.19.2] (port=22643 helo=freedot) by mx1.mail.ru with esmtp id 1EZazm-000OFj-00 for freebsd-bluetooth@freebsd.org; Wed, 09 Nov 2005 00:27:11 +0300 From: "freeman" To: Date: Wed, 9 Nov 2005 00:25:48 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcXkqhv+LMnnjK2pQV6jmqZQInr2fg== Message-Id: Subject: Windows 2003SE PDA LAN X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 21:27:22 -0000 Hi all! I have some troubles in configuration topic. I'm googling some docs about that and found some articles... But... Ok. My Bluetooth USB dongle found correct after kldload ng_ubt, and I have a ubt0 device. Then: - /etc/rc.bluetooth start ubt0 - configuring /etc/bluetooth/hcsecd.conf (basing man page) - hcsed - sdpd - configuring /etc/ppp.conf (like in man page) - rfcomm_pppd -C 1 -s 1 rfcomm-server Ok. Now on my PDA (iPAQ rx3715) I found on computer LAN PPP service. As I understand - in Palm OS we can connect to our host and there is no any questions about user and password. But when I try to connect to my computer - PDA show me the Login page (like on modem connection) and when I click OK it thinks some seconds and... There is no connection :((( Here is my ppp.log: Nov 8 01:06:20 freenout ppp[958]: Phase: Using interface: tun0 Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: Created in closed state Nov 8 01:06:20 freenout ppp[958]: Phase: PPP Started (direct mode). Nov 8 01:06:20 freenout ppp[958]: Phase: bundle: Establish Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: closed -> opening Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: Connected! Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: opening -> carrier Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: carrier -> lcp # at this point we have waiting some seconds and going down :((( Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: read (0): Got zero bytes Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: Disconnected! Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: Connect time: 10 secs: 24 octets in, 260 octets out Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: 4 packets in, 4 packets out Nov 8 01:06:30 freenout ppp[958]: Phase: total 28 bytes/sec, peak 29 bytes/sec on Tue Nov 8 01:06:25 2005 Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: lcp -> closed Nov 8 01:06:30 freenout ppp[958]: Phase: bundle: Dead Nov 8 01:06:30 freenout ppp[958]: Phase: PPP Terminated (normal). Is there anybody can help me? Thanks in advance... From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 21:38:19 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5170C16A41F for ; Tue, 8 Nov 2005 21:38:19 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 291CE43D53 for ; Tue, 8 Nov 2005 21:38:14 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA8LcCJ22889; Tue, 8 Nov 2005 16:38:12 -0500 Message-ID: <43711AC0.9020604@savvis.net> Date: Tue, 08 Nov 2005 13:38:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freeman References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Windows 2003SE PDA LAN X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 21:38:19 -0000 freeman wrote: > Hi all! > > I have some troubles in configuration topic. > > I'm googling some docs about that and found some articles... But... > > Ok. > My Bluetooth USB dongle found correct after kldload ng_ubt, and I have a > ubt0 device. > Then: > - /etc/rc.bluetooth start ubt0 > - configuring /etc/bluetooth/hcsecd.conf (basing man page) > - hcsed > - sdpd > - configuring /etc/ppp.conf (like in man page) > - rfcomm_pppd -C 1 -s 1 rfcomm-server ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ do you mean "rfcomm_pppd -C 1 -s -l rfcomm-server" ? > Ok. > > Now on my PDA (iPAQ rx3715) I found on computer LAN PPP service. As I > understand - in Palm OS we can connect to our host and there is no any > questions about user and password. But when I try to connect to my computer > - PDA show me the Login page (like on modem connection) and when I click OK > it thinks some seconds and... There is no connection :((( when it prompts for username/password just use blanks. > Here is my ppp.log: > Nov 8 01:06:20 freenout ppp[958]: Phase: Using interface: tun0 > Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: Created in closed state > Nov 8 01:06:20 freenout ppp[958]: Phase: PPP Started (direct mode). > Nov 8 01:06:20 freenout ppp[958]: Phase: bundle: Establish > Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: closed -> opening > Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: Connected! > Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: opening -> carrier > Nov 8 01:06:20 freenout ppp[958]: Phase: deflink: carrier -> lcp > # at this point we have waiting some seconds and going down :((( > Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: read (0): Got zero bytes > Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: Disconnected! > Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: Connect time: 10 secs: 24 > octets in, 260 octets out > Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: 4 packets in, 4 packets > out > Nov 8 01:06:30 freenout ppp[958]: Phase: total 28 bytes/sec, peak 29 > bytes/sec on Tue Nov 8 01:06:25 2005 > Nov 8 01:06:30 freenout ppp[958]: Phase: deflink: lcp -> closed > Nov 8 01:06:30 freenout ppp[958]: Phase: bundle: Dead > Nov 8 01:06:30 freenout ppp[958]: Phase: PPP Terminated (normal). > > Is there anybody can help me? most likely your pda assumes it connects to microsoft-style ras server. if there is no option on your pda to change it to unix/ppp-style server then try the following default: set log Phase Chat LCP IPCP CCP tun command rfcomm-server: # fake ras server enable force-scripts set dial "CLIENT CLIENTSERVER" # default config from rfcomm_pppd(8) man page enable lqr accept lqr set timeout 0 disable iface-alias set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 # Do not use PPP authentication. Assume that # Bluetooth connection was authenticated already deny pap disable pap deny chap disable chap thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 8 23:57:54 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D88216A41F; Tue, 8 Nov 2005 23:57:54 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1D6143D45; Tue, 8 Nov 2005 23:57:53 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA8NvpJ26205; Tue, 8 Nov 2005 18:57:52 -0500 Message-ID: <43713B7D.7090405@savvis.net> Date: Tue, 08 Nov 2005 15:57:49 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org References: <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> In-Reply-To: <20051108201620.GD27091@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Brooks Davis , Yar Tikhiy Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 23:57:54 -0000 All, please find next revision of bluetooth-rc stuff at http://people.freebsd.org/~emax/bluetooth-rc-3.diff.txt in this revision i have moved default bluetooth.device.conf configuration file under /etc/defaults. device specific overrides are under /etc/bluetooth and called '$dev.conf'. the rest if quite the same, so /etc/rc.d/bluetooth start "foo" 1) sets hardwired defaults (for backward compatibility) 2) reads /etc/defaults/bluetooth.device.conf (if any) 3) reads /etc/bluetooth/foo.conf i also removed offending { } in while loop stdin redirection. if this is acceptable then i will commit this and start working on bluetooth.device.conf(5) man page and handbook chapter updates. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 06:39:03 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F3416A426; Wed, 9 Nov 2005 06:39:02 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECD2F43D46; Wed, 9 Nov 2005 06:39:00 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jA96csl3007323; Wed, 9 Nov 2005 09:38:54 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jA96cml2007313; Wed, 9 Nov 2005 09:38:48 +0300 (MSK) (envelope-from yar) Date: Wed, 9 Nov 2005 09:38:47 +0300 From: Yar Tikhiy To: Maksim Yevmenkin Message-ID: <20051109063847.GB4605@comp.chem.msu.su> References: <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> <43713B7D.7090405@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43713B7D.7090405@savvis.net> User-Agent: Mutt/1.5.9i Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 06:39:03 -0000 On Tue, Nov 08, 2005 at 03:57:49PM -0800, Maksim Yevmenkin wrote: > > i also removed offending { } in while loop stdin redirection. if this is Thanks! The handling of {} seems to be one of gray corners in sh(1) syntax if it works as in the initial version of your script. Another one I've noticed is the case operator. Your line was like this: case $line in and it still worked for $line containing IFS chars. sh(1) seems to put double quotes aroung the word passed to case implicitly. While such things may seem to make sh(1) coding a tad easier, I'm afraid they shouldn't be relied upon. -- Yar From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 17:30:20 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD6C116A41F; Wed, 9 Nov 2005 17:30:20 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B8143D46; Wed, 9 Nov 2005 17:30:20 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA9HUEJ13785; Wed, 9 Nov 2005 12:30:14 -0500 Message-ID: <43723223.3030802@savvis.net> Date: Wed, 09 Nov 2005 09:30:11 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org References: <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> <43713B7D.7090405@savvis.net> <20051109063847.GB4605@comp.chem.msu.su> In-Reply-To: <20051109063847.GB4605@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Brooks Davis , Yar Tikhiy Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 17:30:21 -0000 All, >>i also removed offending { } in while loop stdin redirection. if this is > > Thanks! The handling of {} seems to be one of gray corners in sh(1) > syntax if it works as in the initial version of your script. Another > one I've noticed is the case operator. Your line was like this: > > case $line in > > and it still worked for $line containing IFS chars. sh(1) seems > to put double quotes aroung the word passed to case implicitly. > While such things may seem to make sh(1) coding a tad easier, I'm > afraid they shouldn't be relied upon. ok, do we agree that http://people.freebsd.org/~emax/bluetooth-rc-4.diff.txt looks fine? i have added double quotes around variables in case statements. any other comments, suggestions, objections? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 17:38:44 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1151616A420 for ; Wed, 9 Nov 2005 17:38:44 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22FB843D4C for ; Wed, 9 Nov 2005 17:38:43 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA9HceJ13945; Wed, 9 Nov 2005 12:38:41 -0500 Message-ID: <4372341F.1020702@savvis.net> Date: Wed, 09 Nov 2005 09:38:39 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vladimir Grebenschikov References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> <4370E826.7090007@savvis.net> <1131477683.1231.12.camel@localhost> <1131480921.1155.5.camel@localhost> In-Reply-To: <1131480921.1155.5.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 17:38:44 -0000 Vladimir, > I have found the reason, it was really after make world > After turning off console pixel-mode I've see: [...] > /libexec/ld-elf.so.1: Shared object "libbluetooth.so.1" not found, required by " > bthidd" ok > After rebuilding bthidd and bthidcontrol it start work. > But, I still does understand why it starts ok with manual start after boot. > >>Probably something wrong with drivers, I've notice that ng bluetooth >>mice is disconnected without any notice. >> >>Reconnecting usb bluetooth device lead to following error: >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) the drivers have not changed for a long time. perhaps something wrong with usb? the message above clearly says that driver was attempting to start interrupt transfer, but it failed (with strange NOMEM error). >>And after that error bt stack does not work until reboot, reconnecting >>dongle does not helps. >> >>Boot scenario was: >>booting >>... >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>Timecounter "TSC" frequency 1686969804 Hz quality 800 >>... >>Trying to mount root from ufs:/dev/ad0s4a >>WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >>WARNING: attempt to net_add_domain(netgraph) after domainfinalize() >>... >>there bthidd started but does not connect mice. >> >>I have turned on-board bt off, then on by notebook switch. >>kernel printed: >>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! >>ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! >>ubt0: at uhub2 port 2 (addr 2) disconnected >>ubt0: detached >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 >>kbd2 at vkbd0 >> >>BT mice start work here. >>after some hours of work it stop moving and l2pings also. >> >>Trying restart BT stack lead to error: >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) again you get all sorts of errors back from usb. this is _not_ driver's fault. i have to check what NOMEM really means and get back to you. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 19:16:57 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 106EB16A41F; Wed, 9 Nov 2005 19:16:57 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B3D943D5A; Wed, 9 Nov 2005 19:16:54 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jA9JGRr5009953; Wed, 9 Nov 2005 11:16:27 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jA9JGQO0009952; Wed, 9 Nov 2005 11:16:26 -0800 Date: Wed, 9 Nov 2005 11:16:26 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051109191626.GG12837@odin.ac.hmc.edu> References: <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> <43713B7D.7090405@savvis.net> <20051109063847.GB4605@comp.chem.msu.su> <43723223.3030802@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3xoW37o/FfUZJwQG" Content-Disposition: inline In-Reply-To: <43723223.3030802@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, Yar Tikhiy , freebsd-rc@freebsd.org, Brooks Davis Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 19:16:57 -0000 --3xoW37o/FfUZJwQG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 09, 2005 at 09:30:11AM -0800, Maksim Yevmenkin wrote: > All, >=20 > >>i also removed offending { } in while loop stdin redirection. if this i= s=20 > > > >Thanks! The handling of {} seems to be one of gray corners in sh(1) > >syntax if it works as in the initial version of your script. Another > >one I've noticed is the case operator. Your line was like this: > > > > case $line in > > > >and it still worked for $line containing IFS chars. sh(1) seems > >to put double quotes aroung the word passed to case implicitly. > >While such things may seem to make sh(1) coding a tad easier, I'm > >afraid they shouldn't be relied upon. >=20 > ok, do we agree that >=20 > http://people.freebsd.org/~emax/bluetooth-rc-4.diff.txt >=20 > looks fine? i have added double quotes around variables in case=20 > statements. any other comments, suggestions, objections? Looks good to me. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --3xoW37o/FfUZJwQG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDcksJXY6L6fI4GtQRAu1vAJwI9dpAevBjTnUPmsAGssO7BFn2hwCfTUdT 2GJN/jRcIDBUvBDDJ4U7zK4= =bjUp -----END PGP SIGNATURE----- --3xoW37o/FfUZJwQG-- From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 22:03:03 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1643016A41F; Wed, 9 Nov 2005 22:03:03 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4334843D45; Wed, 9 Nov 2005 22:03:02 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jA9M2saK094480; Thu, 10 Nov 2005 01:02:54 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jA9M2okQ094476; Thu, 10 Nov 2005 01:02:50 +0300 (MSK) (envelope-from yar) Date: Thu, 10 Nov 2005 01:02:50 +0300 From: Yar Tikhiy To: Maksim Yevmenkin Message-ID: <20051109220250.GA91874@comp.chem.msu.su> References: <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> <20051107200040.GB29473@odin.ac.hmc.edu> <4370EAB4.8090000@savvis.net> <20051108201620.GD27091@odin.ac.hmc.edu> <43713B7D.7090405@savvis.net> <20051109063847.GB4605@comp.chem.msu.su> <43723223.3030802@savvis.net> <20051109191626.GG12837@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051109191626.GG12837@odin.ac.hmc.edu> User-Agent: Mutt/1.5.9i Cc: Brooks Davis , freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 22:03:03 -0000 On Wed, Nov 09, 2005 at 11:16:26AM -0800, Brooks Davis wrote: > On Wed, Nov 09, 2005 at 09:30:11AM -0800, Maksim Yevmenkin wrote: > > All, > > > > >>i also removed offending { } in while loop stdin redirection. if this is > > > > > >Thanks! The handling of {} seems to be one of gray corners in sh(1) > > >syntax if it works as in the initial version of your script. Another > > >one I've noticed is the case operator. Your line was like this: > > > > > > case $line in > > > > > >and it still worked for $line containing IFS chars. sh(1) seems > > >to put double quotes aroung the word passed to case implicitly. > > >While such things may seem to make sh(1) coding a tad easier, I'm > > >afraid they shouldn't be relied upon. > > > > ok, do we agree that > > > > http://people.freebsd.org/~emax/bluetooth-rc-4.diff.txt > > > > looks fine? i have added double quotes around variables in case > > statements. any other comments, suggestions, objections? > > Looks good to me. To me, too (as good as it can look to a person who has never used bluetooth :-) I think it should be a good beginning. -- Yar From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 10 06:52:05 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4312F16A41F for ; Thu, 10 Nov 2005 06:52:05 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE0DE43D46 for ; Thu, 10 Nov 2005 06:52:04 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EZv6r-0000RP-SV; Wed, 09 Nov 2005 21:55:49 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <4372341F.1020702@savvis.net> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> <4370E826.7090007@savvis.net> <1131477683.1231.12.camel@localhost> <1131480921.1155.5.camel@localhost> <4372341F.1020702@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Wed, 09 Nov 2005 21:55:47 +0300 Message-Id: <1131562547.1181.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 06:52:05 -0000 =F7 =D3=D2, 09/11/2005 =D7 09:38 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: > Vladimir, > >>Reconnecting usb bluetooth device lead to following error: > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D= 0x3; > >>wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) >=20 > the drivers have not changed for a long time. perhaps something wrong=20 > with usb? the message above clearly says that driver was attempting to=20 > start interrupt transfer, but it failed (with strange NOMEM error). >=20 > >>And after that error bt stack does not work until reboot, reconnecting > >>dongle does not helps. > >> > >>Boot scenario was: > >>booting > >>... > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D= 0x3; > >>wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > >>Timecounter "TSC" frequency 1686969804 Hz quality 800 > >>... > >>Trying to mount root from ufs:/dev/ad0s4a > >>WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > >>WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > >>... > >>there bthidd started but does not connect mice. > >> > >>I have turned on-board bt off, then on by notebook switch. > >>kernel printed: > >>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new= xfer will be submitted! > >>ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new = xfer will be submitted! > >>ubt0: at uhub2 port 2 (addr 2) disconnected > >>ubt0: detached > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D= 0x3; wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > >>kbd2 at vkbd0 > >> > >>BT mice start work here. > >>after some hours of work it stop moving and l2pings also. > >> > >>Trying restart BT stack lead to error:=20 > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 > >>ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out= =3D0x2 > >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D= 0x3; > >>wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 > >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) >=20 > again you get all sorts of errors back from usb. this is _not_ driver's=20 > fault. i have to check what NOMEM really means and get back to you. Actually under "driver" I mean any in-kernel code (usb, locks, newbus, etc) Effect is stable, after each boot it works few hours and then fails. > thanks, > max --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@swsoft.com From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 11 23:08:35 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2FAD16A41F; Fri, 11 Nov 2005 23:08:35 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6871743D45; Fri, 11 Nov 2005 23:08:35 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jABN8XJ29208; Fri, 11 Nov 2005 18:08:33 -0500 Message-ID: <4375246E.3050303@savvis.net> Date: Fri, 11 Nov 2005 15:08:30 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> In-Reply-To: <1129491219.1616.18.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Warner Losh Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2005 23:08:36 -0000 All, does anyone have any objections to the /etc/devd.conf patch located at http://people.freebsd.org/~emax/devd.conf.diff.txt this patch will add support for a usb bluetooth dongles to devd(8). also while i'm here where do we stick firmware files by default? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 11 23:41:30 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0198116A41F; Fri, 11 Nov 2005 23:41:30 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F7AB43D9F; Fri, 11 Nov 2005 23:41:12 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jABNefxf013899; Fri, 11 Nov 2005 15:40:41 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jABNefmL013898; Fri, 11 Nov 2005 15:40:41 -0800 Date: Fri, 11 Nov 2005 15:40:41 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051111234041.GA10648@odin.ac.hmc.edu> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <4375246E.3050303@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, Warner Losh Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2005 23:41:30 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 11, 2005 at 03:08:30PM -0800, Maksim Yevmenkin wrote: > All, >=20 > does anyone have any objections to the /etc/devd.conf patch located at >=20 > http://people.freebsd.org/~emax/devd.conf.diff.txt >=20 > this patch will add support for a usb bluetooth dongles to devd(8). Looks fine. > also while i'm here where do we stick firmware files by default? I don't see an obvious location. Somewhere under /usr/libdata or /usr/share seems logical to me. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDdSv4XY6L6fI4GtQRAmXDAKDIULgY4HeXDcU0tWRcVPtbC54UYACgy6wF UaW2t70f5EJ81+RdGXu2k6M= =e9NU -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 11 23:52:20 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F36D16A41F; Fri, 11 Nov 2005 23:52:20 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B0D643D53; Fri, 11 Nov 2005 23:52:20 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jABNoPmN078816; Fri, 11 Nov 2005 16:50:25 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 11 Nov 2005 16:51:03 -0700 (MST) Message-Id: <20051111.165103.110975378.imp@bsdimp.com> To: maksim.yevmenkin@savvis.net From: "M. Warner Losh" In-Reply-To: <4375246E.3050303@savvis.net> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 11 Nov 2005 16:50:25 -0700 (MST) Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2005 23:52:20 -0000 In message: <4375246E.3050303@savvis.net> Maksim Yevmenkin writes: : does anyone have any objections to the /etc/devd.conf patch located at : : http://people.freebsd.org/~emax/devd.conf.diff.txt : : this patch will add support for a usb bluetooth dongles to devd(8). That looks fine to me. : also while i'm here where do we stick firmware files by default? /usr/share seems most logical to me, but suffers from the 'can't load firmware until after /usr is mounted' issue. For most firmware, this is a minor issue... Warner From owner-freebsd-bluetooth@FreeBSD.ORG Sat Nov 12 00:09:37 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 048BB16A41F; Sat, 12 Nov 2005 00:09:37 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id F056443D69; Sat, 12 Nov 2005 00:09:33 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jAC09UfE018377; Fri, 11 Nov 2005 16:09:30 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jAC09TUR018376; Fri, 11 Nov 2005 16:09:29 -0800 Date: Fri, 11 Nov 2005 16:09:29 -0800 From: Brooks Davis To: "M. Warner Losh" Message-ID: <20051112000929.GB10648@odin.ac.hmc.edu> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oC1+HKm2/end4ao3" Content-Disposition: inline In-Reply-To: <20051111.165103.110975378.imp@bsdimp.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 00:09:37 -0000 --oC1+HKm2/end4ao3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 11, 2005 at 04:51:03PM -0700, M. Warner Losh wrote: > In message: <4375246E.3050303@savvis.net> > Maksim Yevmenkin writes: > : does anyone have any objections to the /etc/devd.conf patch located at > :=20 > : http://people.freebsd.org/~emax/devd.conf.diff.txt > :=20 > : this patch will add support for a usb bluetooth dongles to devd(8). >=20 > That looks fine to me. >=20 > : also while i'm here where do we stick firmware files by default? >=20 > /usr/share seems most logical to me, but suffers from the 'can't load > firmware until after /usr is mounted' issue. For most firmware, this > is a minor issue... It's also not an issue in practice for most installations since /usr is local and gets mounted quite early. It's only when /usr is NFS and not part of / that you usually get into trouble. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --oC1+HKm2/end4ao3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDdTK5XY6L6fI4GtQRAsonAKCygm7sNVIsRZMo7nwlkGARPwk9rQCgqIXY YL/DSALY13B3O0KnipjOErc= =mv3s -----END PGP SIGNATURE----- --oC1+HKm2/end4ao3-- From owner-freebsd-bluetooth@FreeBSD.ORG Sat Nov 12 00:27:24 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F13516A41F; Sat, 12 Nov 2005 00:27:24 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB89143D45; Sat, 12 Nov 2005 00:27:23 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id CCD9919F2C; Fri, 11 Nov 2005 16:33:43 -0800 (PST) From: "Darren Pilgrim" To: "'M. Warner Losh'" , Date: Fri, 11 Nov 2005 16:27:16 -0800 Message-ID: <001201c5e71f$d9435c40$652a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <20051111.165103.110975378.imp@bsdimp.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: RE: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 00:27:24 -0000 From: Warner Losh > In message: <4375246E.3050303@savvis.net> > Maksim Yevmenkin writes: > : also while i'm here where do we stick firmware files by default? > > /usr/share seems most logical to me, but suffers from the 'can't load > firmware until after /usr is mounted' issue. For most firmware, this > is a minor issue... I put firmware in /boot/firmware/ in keeping with the concept that the kernel and driver bits are all under /boot. A firmware package is really just a hardware-side driver, so why not keep it with the rest of the drivers? Just my 0.020 metric dollars. From owner-freebsd-bluetooth@FreeBSD.ORG Sat Nov 12 03:57:18 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D8C16A41F; Sat, 12 Nov 2005 03:57:18 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id F170843D45; Sat, 12 Nov 2005 03:57:17 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051112035717.JHJG16334.mta10.adelphia.net@[192.168.1.254]>; Fri, 11 Nov 2005 22:57:17 -0500 Message-ID: <4375681B.6030808@savvis.net> Date: Fri, 11 Nov 2005 19:57:15 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> In-Reply-To: <20051112000929.GB10648@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Brooks Davis , "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 03:57:18 -0000 Brooks Davis wrote: > On Fri, Nov 11, 2005 at 04:51:03PM -0700, M. Warner Losh wrote: > >>In message: <4375246E.3050303@savvis.net> >> Maksim Yevmenkin writes: >>: does anyone have any objections to the /etc/devd.conf patch located at >>: >>: http://people.freebsd.org/~emax/devd.conf.diff.txt >>: >>: this patch will add support for a usb bluetooth dongles to devd(8). >> >>That looks fine to me. good. thanks for review. i have committed the patch. >>: also while i'm here where do we stick firmware files by default? >> >>/usr/share seems most logical to me, but suffers from the 'can't load >>firmware until after /usr is mounted' issue. For most firmware, this >>is a minor issue... > > It's also not an issue in practice for most installations since /usr is > local and gets mounted quite early. It's only when /usr is NFS and not > part of / that you usually get into trouble. let me just some more details. in this particular case i'm interested where to put firmware files for bluetooth devices. in particular 1) 3com bluetooth pccard v1 2) broadcom bcm2033 chip based usb bluetooth devices (belkin, d-link, etc.) in both cases firmware files are _not_ loadable modules. they are just files in vendor specific format. tools are provided (bt3cfw(8) and bcmfw(8)) to load firmware into device. what i would like to do is to add a couple more sections into the /etc/devd.conf to handle these devices. those sections can even be commented out because we cannot include firmware into the distribution. it is up to the user to find firmware and put it in the right place. so, should i create /usr/share/firmware directory or just use /usr/share? is it better to have common place for firmware files or have each driver/tool define its own place? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Nov 12 17:55:47 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B8ED16A41F; Sat, 12 Nov 2005 17:55:47 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19EBE43D45; Sat, 12 Nov 2005 17:55:47 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jACHtfMh018800; Sat, 12 Nov 2005 09:55:41 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jACHtfrw018798; Sat, 12 Nov 2005 09:55:41 -0800 Date: Sat, 12 Nov 2005 09:55:41 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051112175541.GA18302@odin.ac.hmc.edu> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> <4375681B.6030808@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <4375681B.6030808@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, Brooks Davis , freebsd-rc@freebsd.org, "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 17:55:47 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 11, 2005 at 07:57:15PM -0800, Maksim Yevmenkin wrote: > Brooks Davis wrote: >=20 > >On Fri, Nov 11, 2005 at 04:51:03PM -0700, M. Warner Losh wrote: > > > >>In message: <4375246E.3050303@savvis.net> > >> Maksim Yevmenkin writes: > >>: does anyone have any objections to the /etc/devd.conf patch located at > >>:=20 > >>: http://people.freebsd.org/~emax/devd.conf.diff.txt > >>:=20 > >>: this patch will add support for a usb bluetooth dongles to devd(8). > >> > >>That looks fine to me. >=20 > good. thanks for review. i have committed the patch. >=20 > >>: also while i'm here where do we stick firmware files by default? > >> > >>/usr/share seems most logical to me, but suffers from the 'can't load > >>firmware until after /usr is mounted' issue. For most firmware, this > >>is a minor issue... > > > >It's also not an issue in practice for most installations since /usr is > >local and gets mounted quite early. It's only when /usr is NFS and not > >part of / that you usually get into trouble. >=20 > let me just some more details. in this particular case i'm interested=20 > where to put firmware files for bluetooth devices. in particular >=20 > 1) 3com bluetooth pccard v1 >=20 > 2) broadcom bcm2033 chip based usb bluetooth devices (belkin, d-link, etc= .) >=20 > in both cases firmware files are _not_ loadable modules. they are just=20 > files in vendor specific format. tools are provided (bt3cfw(8) and=20 > bcmfw(8)) to load firmware into device. >=20 > what i would like to do is to add a couple more sections into the=20 > /etc/devd.conf to handle these devices. those sections can even be=20 > commented out because we cannot include firmware into the distribution.= =20 > it is up to the user to find firmware and put it in the right place. >=20 > so, should i create /usr/share/firmware directory or just use=20 > /usr/share? is it better to have common place for firmware files or have= =20 > each driver/tool define its own place? Instead, I would suggest creating a port that installs the firmware and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDdiybXY6L6fI4GtQRAvKuAJ93GkaxQj4pXuHU2va1klVu3WilhwCfRhMT tAEEBXeVbodoNmEqVvw+Zw4= =Qu5e -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe-- From owner-freebsd-bluetooth@FreeBSD.ORG Sat Nov 12 22:12:11 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FA0816A41F; Sat, 12 Nov 2005 22:12:11 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta4.adelphia.net (mta4.adelphia.net [68.168.78.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4CB443D45; Sat, 12 Nov 2005 22:12:10 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051112220825.QKQI3200.mta9.adelphia.net@[192.168.1.254]>; Sat, 12 Nov 2005 17:08:25 -0500 Message-ID: <437667D4.5030205@savvis.net> Date: Sat, 12 Nov 2005 14:08:20 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> <4375681B.6030808@savvis.net> <20051112175541.GA18302@odin.ac.hmc.edu> In-Reply-To: <20051112175541.GA18302@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2005 22:12:11 -0000 Brooks, [...] >>>>: does anyone have any objections to the /etc/devd.conf patch located at >>>>: >>>>: http://people.freebsd.org/~emax/devd.conf.diff.txt >>>>: >>>>: this patch will add support for a usb bluetooth dongles to devd(8). >>>> >>>>That looks fine to me. >> >>good. thanks for review. i have committed the patch. >> >> >>>>: also while i'm here where do we stick firmware files by default? >>>> >>>>/usr/share seems most logical to me, but suffers from the 'can't load >>>>firmware until after /usr is mounted' issue. For most firmware, this >>>>is a minor issue... >>> >>>It's also not an issue in practice for most installations since /usr is >>>local and gets mounted quite early. It's only when /usr is NFS and not >>>part of / that you usually get into trouble. >> >>let me just some more details. in this particular case i'm interested >>where to put firmware files for bluetooth devices. in particular >> >>1) 3com bluetooth pccard v1 >> >>2) broadcom bcm2033 chip based usb bluetooth devices (belkin, d-link, etc.) >> >>in both cases firmware files are _not_ loadable modules. they are just >>files in vendor specific format. tools are provided (bt3cfw(8) and >>bcmfw(8)) to load firmware into device. >> >>what i would like to do is to add a couple more sections into the >>/etc/devd.conf to handle these devices. those sections can even be >>commented out because we cannot include firmware into the distribution. >>it is up to the user to find firmware and put it in the right place. >> >>so, should i create /usr/share/firmware directory or just use >>/usr/share? is it better to have common place for firmware files or have >>each driver/tool define its own place? > > Instead, I would suggest creating a port that installs the firmware > and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. ok. that sounds fine to me. does anyone have experience with this like this? i mean do i have to contact 3com and broadcom and obtain some sort of permission for this? how does this work? linux bluez has rpm that contains firmware. it seems like they have contacted broadcom, because they have firmware files in their cvs http://cvs.sourceforge.net/viewcvs.py/bluez/firmware/broadcom/ can i legally get those files and include them into freebsd port's collection? if this is going to lead to too much corporate brouhaha then perhaps i should leave it as it is. bcmfw(8) and bt3cfw(8) man pages already tell users where they can get the firmware. thanks, max