Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-06-06 Thread H. Nikolaus Schaller
Hi Rob, thanks for all the comments. > Am 25.05.2017 um 14:48 schrieb Rob Herring : > > On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 15:10 schrieb Rob Herring : >>> >>> +Marcel >>

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-06-06 Thread H. Nikolaus Schaller
Hi Rob, thanks for all the comments. > Am 25.05.2017 um 14:48 schrieb Rob Herring : > > On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 15:10 schrieb Rob Herring : >>> >>> +Marcel >> >> Good! >> >> Hm. Well: >> >> root@letux:~# hciconfig

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-25 Thread Pavel Machek
Hi! > > You don't need hciattach. All userspace has to do for kernel BT > > drivers is "hciconfig hci0 up|down". > > Hm. Well: > > root@letux:~# hciconfig hci0 up > Can't get device info: No such device > root@letux:~# > > I wonder how I can tell hciconfig about the UART port if not by running

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-25 Thread Pavel Machek
Hi! > > You don't need hciattach. All userspace has to do for kernel BT > > drivers is "hciconfig hci0 up|down". > > Hm. Well: > > root@letux:~# hciconfig hci0 up > Can't get device info: No such device > root@letux:~# > > I wonder how I can tell hciconfig about the UART port if not by running

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-25 Thread Rob Herring
On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 15:10 schrieb Rob Herring : >> >> +Marcel > > Good! > >> >> On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller >> wrote: >>> Hi Rob, >>>

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-25 Thread Rob Herring
On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 15:10 schrieb Rob Herring : >> >> +Marcel > > Good! > >> >> On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller >> wrote: >>> Hi Rob, >>> Am 23.05.2017 um 14:28 schrieb Rob Herring :

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 15:10 schrieb Rob Herring : > > +Marcel Good! > > On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 14:28 schrieb Rob Herring : >>> >>> On Tue, May 23,

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 15:10 schrieb Rob Herring : > > +Marcel Good! > > On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 14:28 schrieb Rob Herring : >>> >>> On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller >>> wrote: Hi

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread Rob Herring
+Marcel On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 14:28 schrieb Rob Herring : >> >> On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller >> wrote: >>> Hi Rob, >>> Am 23.05.2017

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread Rob Herring
+Marcel On Tue, May 23, 2017 at 7:48 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 14:28 schrieb Rob Herring : >> >> On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller >> wrote: >>> Hi Rob, >>> Am 23.05.2017 um 04:26 schrieb Rob Herring : On Sun, May 21,

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 14:28 schrieb Rob Herring : > > On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 04:26 schrieb Rob Herring : >>> >>> On Sun, May 21, 2017 at 5:44 AM, H.

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 14:28 schrieb Rob Herring : > > On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 04:26 schrieb Rob Herring : >>> >>> On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller >>> wrote: Since our proposed API was

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread Rob Herring
On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 04:26 schrieb Rob Herring : >> >> On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller >> wrote: >>> Since our proposed API was not

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-23 Thread Rob Herring
On Tue, May 23, 2017 at 12:43 AM, H. Nikolaus Schaller wrote: > Hi Rob, > >> Am 23.05.2017 um 04:26 schrieb Rob Herring : >> >> On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller >> wrote: >>> Since our proposed API was not acceptable and the new serdev API has >>> arrived in 4.11 kernels,

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-22 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 04:26 schrieb Rob Herring : > > On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller > wrote: >> Since our proposed API was not acceptable and the new serdev API has arrived >> in 4.11 kernels, >> we finally took the

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-22 Thread H. Nikolaus Schaller
Hi Rob, > Am 23.05.2017 um 04:26 schrieb Rob Herring : > > On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller > wrote: >> Since our proposed API was not acceptable and the new serdev API has arrived >> in 4.11 kernels, >> we finally took the challenge to update the w2sg and w2cbw drivers

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-22 Thread Rob Herring
On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller wrote: > Since our proposed API was not acceptable and the new serdev API has arrived > in 4.11 kernels, > we finally took the challenge to update the w2sg and w2cbw drivers to use the > serdev API. > > The approach is

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-22 Thread Rob Herring
On Sun, May 21, 2017 at 5:44 AM, H. Nikolaus Schaller wrote: > Since our proposed API was not acceptable and the new serdev API has arrived > in 4.11 kernels, > we finally took the challenge to update the w2sg and w2cbw drivers to use the > serdev API. > > The approach is to write a "man in

[RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-21 Thread H. Nikolaus Schaller
Since our proposed API was not acceptable and the new serdev API has arrived in 4.11 kernels, we finally took the challenge to update the w2sg and w2cbw drivers to use the serdev API. The approach is to write a "man in the middle" driver which is on one side a serdev client which directly

[RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

2017-05-21 Thread H. Nikolaus Schaller
Since our proposed API was not acceptable and the new serdev API has arrived in 4.11 kernels, we finally took the challenge to update the w2sg and w2cbw drivers to use the serdev API. The approach is to write a "man in the middle" driver which is on one side a serdev client which directly