From owner-freebsd-wireless@freebsd.org Sun Apr 21 07:19:44 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 702DE15849D7 for ; Sun, 21 Apr 2019 07:19:44 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 365B58EACC for ; Sun, 21 Apr 2019 07:19:42 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [188.174.55.23] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1hI6lH-0001NH-Qn; Sun, 21 Apr 2019 09:19:39 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id x3L7JcDB059227 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 21 Apr 2019 09:19:38 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id x3L7Jco3059226; Sun, 21 Apr 2019 09:19:38 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sun, 21 Apr 2019 09:19:38 +0200 From: Matthias Apitz To: freebsd-wireless@freebsd.org Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD Message-ID: <20190421071938.GA59008@c720-r342378> Reply-To: Matthias Apitz References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 13.0-CURRENT r342378 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.11.1 (2018-12-01) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 188.174.55.23 X-Rspamd-Queue-Id: 365B58EACC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.77 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[guru@unixarea.de]; HAS_XOIP(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-3.08)[ip: (-8.89), ipnet: 178.254.0.0/19(-3.62), asn: 42730(-2.87), country: DE(-0.01)]; HAS_XAW(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; MX_GOOD(-0.01)[cached: mail.unixarea.de]; NEURAL_HAM_SHORT(-0.98)[-0.979,0]; RCVD_IN_DNSWL_LOW(-0.10)[101.4.254.178.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[23.55.174.188.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; DMARC_NA(0.00)[unixarea.de]; AUTH_NA(1.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2019 07:19:44 -0000 El día sábado, abril 20, 2019 a las 02:16:49p. m. +0300, Serge Semenenko escribió: > Hi > > It works for me with such section in devd.conf > > attach 200 { > device-name "ubt[0-9]+"; > match "vendor" "0x0cf3"; > match "product" "0xe006"; > action "sleep 2 && /usr/sbin/ath3kfw -d $ugen && sleep 2 && /etc/rc.d/bluetooth quietstart $device-name"; > }; I have added the above lines to /etc/devd.conf, ofc with the vendor and product ID of my chip: $ usbconfig ... ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) and place the firmware in the directory where /usr/sbin/ath3kfw is looking for it, into /usr/share/firmware/ath3k/ar3k/ The problem remains: no device /dev/ubt0 gets created (and the attach rule does not apply. When I change 'attach 200' to 'notify 100', /usr/sbin/ath3kfw gets called and the firmware gets loaded into the chip. But nothing of BT does work. I think some of the nd_*.ko modules do not attach and due to this the device is not created. matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub N € I N zur EU! "Gegen das EU-Europa der Banken, Konzerne und Kriegstreiber. Für ein soziales und friedliches Europa der Völker." DKP