From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth Date: Thu, 25 May 2017 19:05:40 +0200 Message-ID: <20170525170540.GF3085@amd> References: <78B1501A-B9AD-4C6E-A481-26F647AA2BCE@goldelico.com> <0D94BEA0-F98D-48F6-9DDC-99F932AE7834@goldelico.com> <889E8F7F-FC0F-490E-B924-D04D9F4D3402@goldelico.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sDKAb4OeUBrWWL6P" Return-path: Content-Disposition: inline In-Reply-To: <889E8F7F-FC0F-490E-B924-D04D9F4D3402@goldelico.com> Sender: linux-kernel-owner@vger.kernel.org To: "H. Nikolaus Schaller" Cc: Rob Herring , Mark Rutland , =?iso-8859-1?Q?Beno=EEt?= Cousson , Tony Lindgren , Russell King , Thierry Reding , Jonathan Cameron , Maxime Ripard , Jarkko Sakkinen , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-omap , Discussions about the Letux Kernel , kernel@pyra-handheld.com, Marcel Holtmann List-Id: devicetree@vger.kernel.org --sDKAb4OeUBrWWL6P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > You don't need hciattach. All userspace has to do for kernel BT > > drivers is "hciconfig hci0 up|down". >=20 > Hm. Well: >=20 > root@letux:~# hciconfig hci0 up > Can't get device info: No such device > root@letux:~# >=20 > I wonder how I can tell hciconfig about the UART port if not by running h= ciattach /dev/ttyBT0? You should not have to tell hciconfig about ttyBT0. Kernel should automatically setup hci0<->ttyBT0 connection during boot, based on the device tree. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --sDKAb4OeUBrWWL6P Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlknDuQACgkQMOfwapXb+vLfygCglwuirnlxs5N9xPDBEzgZCPoM ao0AnRVwl260eN43zizM2TXLywWfwLM/ =ULag -----END PGP SIGNATURE----- --sDKAb4OeUBrWWL6P--