Re: [BRLTTY] bc640: Some debug info

2008-02-07 Thread Mario Lang
Dave Mielke <[EMAIL PROTECTED]> writes: >>Yes, for now, thats all that is necessary. The Linux hiddev >>interface has a bunch of ioctls as well (all defined in linux/hiddev.h). >>They can be used to get "reports" and do other things, but >>reading incoming events is as simple as reading from the

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Dave Mielke
[quoted lines by Mario Lang on 2008/02/06 at 23:57 +0100] >Yes, for now, thats all that is necessary. The Linux hiddev >interface has a bunch of ioctls as well (all defined in linux/hiddev.h). >They can be used to get "reports" and do other things, but >reading incoming events is as simple as rea

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Samuel Thibault
Mario Lang, le Wed 06 Feb 2008 23:57:38 +0100, a écrit : > > What's in the event->hid field? > > -16711674. 0xff010006 probably looks better, whatever it means :) Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Mario Lang
Dave Mielke <[EMAIL PROTECTED]> writes: >>Below is a C file that dumps the keypresses to stdout. > > So all you do is open a hiddev and read from it? Yes, for now, thats all that is necessary. The Linux hiddev interface has a bunch of ioctls as well (all defined in linux/hiddev.h). They can be u

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Dave Mielke
[quoted lines by Mario Lang on 2008/02/06 at 19:14 +0100] >Below is a C file that dumps the keypresses to stdout. So all you do is open a hiddev and read from it? What's in the event->hid field? Do you get any special event(s) when the device is turned off? Is the device just USB, or does it h

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Andor Demarteau
On Wed, 6 Feb 2008, Mario Lang wrote: > Andor Demarteau <[EMAIL PROTECTED]> writes: > > > you will probably not get any specs, I've been bugging optelec here in .nl > > for them for some time. > > Well, Dave already has the specs, so thats not the problem... well well okay > -- > CYa,

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Peter op 't Hof
scussion between users and developers of BRLTTY." Sent: Wednesday, February 06, 2008 7:16 PM Subject: Re: [BRLTTY] bc640: Some debug info > you will probably not get any specs, I've been bugging optelec here in .nl > for them for some time. > They even try to sell me this display i

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Mario Lang
Andor Demarteau <[EMAIL PROTECTED]> writes: > you will probably not get any specs, I've been bugging optelec here in .nl > for them for some time. Well, Dave already has the specs, so thats not the problem... -- CYa, ⡍⠁⠗⠊⠕ | Debian Developer http://debian.org/> .''`. | Get my public key vi

Re: [BRLTTY] bc640: Some debug info

2008-02-06 Thread Andor Demarteau
you will probably not get any specs, I've been bugging optelec here in .nl for them for some time. They even try to sell me this display instead of me going to the baum varioconnect models. O blundly told them, if you don't support linux no deal. seams even that didn't help much. Lucky me they w

[BRLTTY] bc640: Some debug info

2008-02-06 Thread Mario Lang
Hi. This is as far as I could get without any specs. Below is a C file that dumps the keypresses to stdout. Keypresses are delivers pretty strangely, first the "keycode" arrives, and then the key type. A key type indicator has the left nibble set to 1110 or to indicate press and release, an