Regarding the mouse, I've found this: http://maemo.org/pipermail/maemo-developers/2006-October/005941.html Francesc. A Dimarts 06 Mar? 2007, Larry Battraw va escriure: > On 3/5/07, Francesc Roig-i-Feliu <francesc.roig at impress.biz> wrote: > > Hi > > > > Anybody knows if is possible that mameo recognizes a BT mouse? > > Anybody has tryed it? > > No and yes :-) The X-server Maemo uses is not capable of using a > mouse because 1) There is no existing option (as OS2007 is shipped) > to tell it to look for one and 2) Even when you point it to a mouse > it still does not work. Tried it this weekend and although pairing > worked fine the X server refused to respond to the mouse, using the > -mouse <device_path> option. > > Daniel, I note that you're the build-master and author of a lot of the > changes for the X/kdrive server (I built it over the weekend and dug > around in the code). I'm still unclear on what is causing the mouse > to not work, and how you would tell it what type of mouse is > connected. In hw/kdrive/linux/mouse.c I can see the code for handling > different types of mice and it appears to be compiled into linux.a for > linking against, since you need it for tslib. It's unclear how much > of linux.a is used for kdrive beyond tslib.c. Can you give me a > couple hints for starting work on getting a mouse functional? > > Thanks- > Larry > > Larry -------------------------------------------------------- This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
