[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Usbb2k-api-dev] Kernel Panic On Device Disconnect
From: |
yealink |
Subject: |
Re: [Usbb2k-api-dev] Kernel Panic On Device Disconnect |
Date: |
Sun, 3 Sep 2006 02:02:59 +0200 |
User-agent: |
Mutt/1.5.6i |
On Thu, Aug 31, 2006 at 01:42:04PM +0100, Dan Conlon wrote:
> I am using the 20060503 module with a P4K on Ubuntu Linux.
>
> I can confirm that all functions work through the /sys/ interface, with
> the exception of RINGTONE which when activated via show_icon does not
> result in any ring tone being emitted. I am not sure whether I have
> misunderstood the use of this and I should be playing a ringtone PCM
> through the sound device to achieve ring functionality?
Yes, RINGTONE is a P1K feature, for the P4K you should activate SPEAKER and
send PCM data via the audio channel.
>
> I am now in the process of writing a wrapper for linphonec to allow the
> P4K to control it. I am opening the /dev/input/eventX device, issuing
> the EVIOCGRAB ioctl and my thread is then in a blocking read() to wait
> for key input. However the effect of this is that when the device is
> disconnected, a kernel panic occurs, presumably because the eventX
> device cannot be removed or is removed whilst a process has it open.
>
> How should I deal with this or is my approach of using the eventX devide
> incorrect in general?
There's an updated version available on:
http://cvs.savannah.nongnu.org/viewcvs/yealink-module/?root=usbb2k-api
Hopefully this fixes the problem, if not, can you please include a trace?
-Henk
- Re: [Usbb2k-api-dev] Kernel Panic On Device Disconnect,
yealink <=