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
>>
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
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
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
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,
>>>
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 :
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,
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
+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
+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,
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.
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
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
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,
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
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
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
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
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
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
20 matches
Mail list logo