Re: [Usbb2k-api-help] Yealink USB Handset

[Thomas Reitmayr]

Sure, there are a few things that changed:

1. The packet structure changed. The length and offset fields are gone and
the data size of 6 bytes now. This prevents the current driver from
functioning in the first place. But it can be used to automagically
distinguish a P1KH from the rest of the models, no need to know the
assigned range of the model version number.

2. You are right, key presses are not polled anymore (what an
improvement!) so you just sit and wait for interrupts to get the keys.

3. The key codes have changed.

Unchanged are:

1. The command codes and most of the parameters (without length+offset).
2. The LCD layout and the associated bits in the data array.
3. I think also the ring tone data (not 100% sure).

Therefore only audio (record+playback) should work right now, afaik.
Regards,
-Thomas

--- address@hidden schrieb:

> On Sat, Aug 11, 2007 at 09:23:10PM +0200, Thomas Reitmayr wrote:
> > Hi Henk and Andrew,
> > just today I received the key codes for a P1KH from a guy as I myself
> do
> > not own this handset either. So I think that's almost all information
> > needed to add the P1KH to the yealink kernel module. One thing I still
> > have to figure out is how to update just a part of the display.
> > For the first steps I will use the USB logs I received and my personal
> > P1KH model which basically implements the device side ("hardcoded") of
> > USBIP. I will let you know how work progresses.
> > Regards,
> > -Thomas
> > 
> > PS: My current knowledge about the P1KH is packed into a test program
> > 'p1kh' at
> >
>
http://www.devbase.at/svn/view.cgi/yealink-tools/trunk/?root=experimental
> > and some USB log files at
> > http://www.devbase.at/svn/view.cgi/yealink-logs/?root=experimental
> > 
> Well I suspect it is not only the keycodes that have changed but also
> the
> way keys are sent via USB. P1K uses polling for keys. P1KH probably uses
> interrupt driven transfers. (I haven't looked at the snoopy logs in
> detail)
> > 
> 
> Andrew: can you please specify what works with the current in-kernel
> module(s) for P1KH?
> Do some keys work?
> 
> 
> Matrix of supported features:
> function        API     P1K     P4K     B2K   P1KH
> ------------------------------------------------------        
> audio playback  alsa    ok      ok      ok    ?
> audio record    alsa    ok      ok      ok    ?
> keyboard        input   ok      ok      WIP   ?
> LCD             sysfs   ok      ok            ?
> LED             sysfs   ok                    ?
> DIALTONE        sysfs   ok      ok      ok    ?
> RINGTONE        sysfs   ok              WIP   ?
> 
> 
> See also the README in:
> http://cvs.savannah.gnu.org/viewcvs/usbb2k-api/yealink-module/
> 
> - henk
> 



      Heute schon einen Blick in die Zukunft von E-Mails wagen? 
www.yahoo.de/mail