Linux bluetooth development
 help / color / mirror / Atom feed
From: Peter Klausler <peter@klausler.com>
To: Charles Bueche <charles@bueche.ch>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Mon, 1 Dec 2003 09:38:04 -0600	[thread overview]
Message-ID: <20031201093804.A1281@schnell.us.cray.com> (raw)
In-Reply-To: <1070218289.8534.30.camel@bluez.bueche.ch>; from charles@bueche.ch on Sun, Nov 30, 2003 at 12:51:29 -0600

On 2003.11.30 12:51 Charles Bueche wrote:
> Hi again,
> 
> responding to my own email after studying fake.c : I got it to compile
> on 2.6, but this code isn't able to run as module on 2.6 kernels,
> which
> changed the module format.
> 
> Peter : do you plan a 2.6 version anytime soon ?

For 2.6 the fake.o driver shouldn't be needed; I'm told that
there's a legitimate driver in 2.6 that can be used to
inject input events from user-land.  But I've been way
too busy porting 2.6 to a new architecture to spend much
time playing with it on i386, so I can't tell you how hard
it would be to adjust bthid to use the new driver.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-12-01 15:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38   ` Peter Klausler [this message]
2003-12-02 15:55     ` Edd Dumbill
2003-12-02 16:01       ` Edd Dumbill
2003-12-03 20:18         ` Charles Bueche
2003-12-03 20:35           ` Marcel Holtmann
2003-12-04  8:53             ` Olivier Bornet
2003-12-04 13:52               ` Marcel Holtmann
2003-12-04 13:57                 ` Olivier Bornet
2003-12-04 14:10                   ` Marcel Holtmann
2003-12-04 16:35                     ` Olivier Bornet
2003-12-04 17:03                       ` Marcel Holtmann
2003-12-09 20:31               ` Charles Bueche
2003-12-09 22:42                 ` Olivier Bornet
2003-12-10  8:12                   ` Charles Bueche
2003-12-10  8:30                     ` Olivier Bornet
2003-12-13 15:56                       ` Charles Bueche
2003-12-13 16:39                         ` Marcel Holtmann
2003-12-13 18:51                           ` Charles Bueche
2003-12-13 19:04                             ` Marcel Holtmann
2003-12-14 13:55                               ` Charles Bueche
2003-12-14 14:22                                 ` Marcel Holtmann
2003-12-14 20:01                                   ` Charles Bueche
2003-12-14 20:09                                     ` Marcel Holtmann
2003-12-10  1:41                 ` Marcel Holtmann
2003-12-02 17:39       ` Marcel Holtmann
2003-12-02 17:42         ` Peter Klausler
2003-12-02 17:56           ` Marcel Holtmann
2003-12-03 10:10         ` Stephen Crane
2003-12-03 13:06           ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031201093804.A1281@schnell.us.cray.com \
    --to=peter@klausler.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=charles@bueche.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox