Hey All,
Ever since I switched over to the new input layer I've had a really
annoying problem with my keyboard modifier keys. If I hold a modifier
key down for more than 5 secs without hitting another key, I get a
spurious key-up event, so that even though I'm still holding the key
down
At 8:37 PM -0500 3/27/01, Adam C Powell IV wrote:
Right. The "Linux" mapping is different from the ADB mapping. See
/usr/include/linux/input.h for keycodes to use there.
For all the gory details:
http://homepages.munich.netsurf.de/Franz.Sirl/inputppc.html
I know, very confusing, lots of br
On Wed, Mar 28, 2001 at 01:04:26PM -0500, Patrice LaFlamme wrote:
>
> I do see the new input layer. It does't compile, no matter how many times
> I rerun menuconfig. But maybe I'm doing something wrong, don't know what.
it took me a couple times to get it right.
On Wed, Mar 28, 2001 at 05:24:37AM -0900 or thereabouts, Ethan Benson wrote:
> it can be done, with 2.2.18 and 2.2.19. its just the kernel
> configuration system is buggy so you have to do two runthroughs to get
> the old adb drivers turned off, which allows the new input layer
> dri
any
> > documentation for the whole stuff also distributed with the kernel
> > itself?
> > Patrice: It does work on the 3400 (gpm, X).
>
> Hm, I guess I'll have to re-read this thread ;)
> But, my main problem is that I can't even get a kernel compiled with th
On Wed, Mar 28, 2001 at 09:06:00AM -0500, Patrice LaFlamme wrote:
>
> But, my main problem is that I can't even get a kernel compiled with the
> new input layer, so there's no chance of getting it to work (that's with
> 2.2.18).
it can be done, with 2.2.18 and 2
> itself?
> Patrice: It does work on the 3400 (gpm, X).
Hm, I guess I'll have to re-read this thread ;)
But, my main problem is that I can't even get a kernel compiled with the
new input layer, so there's no chance of getting it to work (that's with
2.2.18).
As for 2.4.
* Adam C Powell IV <[EMAIL PROTECTED]>, 20010328 12:02 +0200:
> Andre Berger wrote:
>
> > #/etc/sysctl.conf
> > dev.mac_hid.mouse_button2_keycode = 76
> > dev.mac_hid.mouse_button3_keycode = 127
> > dev.mac_hid.mouse_button_emulation = 1
> >
> > (and rebooted; /proc/sys/dev/mac_hid/mouse* are set
On Wed, Mar 28, 2001 at 12:11:36AM +0200 or thereabouts, Andre Berger wrote:
> Those keycodes are mapped to my keypad-enter (btn2) and the power button
I never managed to use that keypad-enter for mouse-button emulation,
and I don't think I tried with the power button. This left me with very
littl
Andre Berger wrote:
> #/etc/sysctl.conf
> dev.mac_hid.mouse_button2_keycode = 76
> dev.mac_hid.mouse_button3_keycode = 127
> dev.mac_hid.mouse_button_emulation = 1
>
> (and rebooted; /proc/sys/dev/mac_hid/mouse* are set to these values)
>
> Those keycodes are mapped to my keypad-enter (btn2) and t
* Patrice LaFlamme <[EMAIL PROTECTED]>, 20010327 22:36 +0100:
> On Mon, Feb 12, 2001 at 02:57:00AM +0100 or thereabouts, Andre Berger wrote:
> > I've updated my potato system (PB3400) to kernel 2.2.19pre17-pmac from
> > proposed updates, which uses the new input layer mod
On Mon, Feb 12, 2001 at 02:57:00AM +0100 or thereabouts, Andre Berger wrote:
> I've updated my potato system (PB3400) to kernel 2.2.19pre17-pmac from
> proposed updates, which uses the new input layer model. I've changed
> mouse type and device successfully, the mouse works in X
I've updated my potato system (PB3400) to kernel 2.2.19pre17-pmac from
proposed updates, which uses the new input layer model. I've changed
mouse type and device successfully, the mouse works in X and the
consoles, with gpm. The only thing not solved: Mouse button emulation. I
used to
Quoting Sergio Brandano <[EMAIL PROTECTED]>:
>
> ...
>
> I checked Documentation/usb/input.txt before writing my message;
> there is no info on adbmouse and adbkeyboard. Also, the www page
ADB kbd works the same as USB kbd with the new input layer, so do ADB mice
(
Hi Adam,
I agree with you that the docs are not up to date; for example, the
kernel docs
on the mouse layer for Mac are completely missing. I appreciated the URL
mentioned by Bastien?, although certain infos should be in the kernel
Docs.
I also agree with you that there is a confusing situation
On Mon, Dec 18, 2000 at 05:46:18PM +0100, Michael Schmitz wrote:
> I agree that breaking this in stable wasn't a good idea. Others gave
> priority to phasing out the old mouse driver sooner rather than later
> (which is a Good Thing, all things considered).
> The documentation might have gotten out
> > Has any of you read this page about the PPC Input layer ?!
> > http://home.munich.netsurf.de/Franz.Sirl/inputppc.html
>
> Yes, went through the whole thing and still didn't understand this. For
> example,
> it says, "For backwards compatibility, the deprecated adb_buttons= kernel
> argument
On Mon, Dec 18, 2000 at 10:20:31AM -0500, Adam C Powell IV wrote:
> Yes, went through the whole thing and still didn't understand this. For
> example,
> it says, "For backwards compatibility, the deprecated adb_buttons= kernel
> argument
> still uses ADB keycodes" but this is clearly failing for
Quoting Adam C Powell IV <[EMAIL PROTECTED]>:
> Bastien Nocera wrote:
>
> > Sergio Brandano wrote:
> > >
> > > Ah. That explains why the uparrow disappears every time I enable
> > > mouse_button_emulation. By playing with it, I discovered that 103 is
> actually
> > > the uparrow, which is also t
Bastien Nocera wrote:
> Sergio Brandano wrote:
> >
> > Ah. That explains why the uparrow disappears every time I enable
> > mouse_button_emulation. By playing with it, I discovered that 103 is
> > actually
> > the uparrow, which is also the mouse button 2. The funny thing is that,
> > at the sam
Sergio Brandano wrote:
>
> Hi Adam,
>
> Adam C Powell IV wrote:
>
> > > Yes, echoing on /proc is what I did too. The values are 103 and 111
> > > but I still report the problem.
> >
> > And you echoed to the mouse_button_emulation too? And when you read it, it
> > gives 1? That's very strang
Hi Adam,
Adam C Powell IV wrote:
> > Yes, echoing on /proc is what I did too. The values are 103 and 111
> > but I still report the problem.
>
> And you echoed to the mouse_button_emulation too? And when you read it, it
> gives 1? That's very strange. The Debian kernel is working fine for m
Sergio Brandano wrote:
> Hi Adam,
>
> >Sergio Brandano wrote:
> >
> >> Thank you Ethan. Now I have kernel 2.2.18pre21 up and running, which
> >> is the latest stable from samba. In order to have X11 (old) running,
> >> I had to modify the pointer section from
> >>
> >> BusMouse on /dev/adbmou
> As for Bastien's point, "RTFM", I think that is appropriate for a point
> upgrade,
> e.g. slink to potato, but a minor upgrade to 2.2r2 should really not require
> paging
> through oodles of kernel docs in the console (because X won't start without
> the
> pointer). Maybe we need some kind of
Sergio Brandano wrote:
> Thank you Ethan. Now I have kernel 2.2.18pre21 up and running, which
> is the latest stable from samba. In order to have X11 (old) running,
> I had to modify the pointer section from
>
> BusMouse on /dev/adbmouse to ImPS/2 on /dev/input/mice.
>
> X11 is up and running
Ethan Benson wrote:
> On Mon, Dec 11, 2000 at 03:42:03PM +0100, Bastien Nocera wrote:
> >
> > I'm not in front of my Debian box. What is used to generate the /dev nodes
> > ? A
> > postinstall script ? of which package ? Is it in the base.tgz ?
>
> the nodes in /dev are in base2_2.tgz, but they a
Hi again,
showkey maps F11 to 103 and F12 to 111.
bootx maps mouse_button2 to 103 and mouse_button3 to 111
/proc/sys/dev/mac_hid/mouse_button2 points at 97 and
.../mouse_button3 points at 100.
I tried modifying bootx parameters to 97 and 100, but it
did not work. I also
Thank you Ethan. Now I have kernel 2.2.18pre21 up and running, which
is the latest stable from samba. In order to have X11 (old) running,
I had to modify the pointer section from
BusMouse on /dev/adbmouse to ImPS/2 on /dev/input/mice.
X11 is up and running again. So far so good. What is no
On Mon, Dec 11, 2000 at 03:42:03PM +0100, Bastien Nocera wrote:
>
> I'm not in front of my Debian box. What is used to generate the /dev nodes ?
> A
> postinstall script ? of which package ? Is it in the base.tgz ?
the nodes in /dev are in base2_2.tgz, but they are also
generated/maintained by
On Mon, Dec 11, 2000 at 01:11:58PM +, Sergio Brandano wrote:
>
> ...
>
> I checked Documentation/usb/input.txt before writing my message;
> there is no info on adbmouse and adbkeyboard. Also, the www page
> http://home.munich.netsurf.de/Franz.Sirl/inputppc.html is not up
> to date. Thank
> > Have these keys been hardcoded?
>
> BenH explained this before, I think he said it was a hardware problem (the
> Caps-Lock key not sending a keycode when it goes back up, or something like
> that), that would also explain why you can't switch these 2 keys. Is there a
> fix
> for that ?
Th
ut not quite
> doing caps lock right- I don't quite remember, but it was pretty odd.
> Heard somewhere that it was an issue in the adb keyboard driver in the
> kernel...)
>
> Now with the new input layer, I thought "Great, I can finally switch
> them." But no,
> I checked Documentation/usb/input.txt before writing my message;
> there is no info on adbmouse and adbkeyboard. Also, the www page
> http://home.munich.netsurf.de/Franz.Sirl/inputppc.html is not up
> to date. Thank you for help anyway.
What do you mean, not up to date? Did you update the de
as pretty odd.
Heard somewhere that it was an issue in the adb keyboard driver in the
kernel...)
Now with the new input layer, I thought "Great, I can finally switch
them." But no, trying to do so has no effect now, not even the wierd
behavior from before.
Have these keys been hardcoded?
Ano
...
I checked Documentation/usb/input.txt before writing my message;
there is no info on adbmouse and adbkeyboard. Also, the www page
http://home.munich.netsurf.de/Franz.Sirl/inputppc.html is not up
to date. Thank you for help anyway.
Could anyone running the new kernel and the new X11 on
Quoting Sergio Brandano <[EMAIL PROTECTED]>:
>
> Hi,
>
> I am finding it difficult to create the new /dev/input for my
> PowerBook Lombard. I am compiling the latest pmac-stable tree
> from ppc.samba.org::linux-pmac-stable. The Mac-device-drivers
> section mentions "Use input layer for ADB
Hi,
I am finding it difficult to create the new /dev/input for my
PowerBook Lombard. I am compiling the latest pmac-stable tree
from ppc.samba.org::linux-pmac-stable. The Mac-device-drivers
section mentions "Use input layer for ADB keyboard and mouse"
but it does not say how to create them.
On Tue, Dec 05, 2000 at 09:53:18AM -0600, Phil Fraering wrote:
>
> Well, after reading replies from various people, I decided to try
> to get the new input layer working.
>
> There was an rpm on the site in Germany (linked to from Benh's page)
> that looked as if it wo
On Tue, Dec 05, Phil Fraering wrote:
> When I try to reboot, I eventually get the following messages:
There is proably something like with CMD646.
> And that's when it freezes.
>
> BTW, the buffer history (shift-pageup) still works.
pipe this through babelfish
(for short: you need a kernel tha
Well, after reading replies from various people, I decided to try
to get the new input layer working.
There was an rpm on the site in Germany (linked to from Benh's page)
that looked as if it would repopulate the /dev file system if I
installed it. I looked at it with alien first, to make
Bryan Stillwell <[EMAIL PROTECTED]> writes:
> Am I to understand that you have a ieee1394 hard drive working under ppc
> linux? This weekend I was able to get all the ieee1394 stuff working
> with 2.2.18pre21 from Paulus's tree, but I didn't have anything to test
> with besides gscanbus which see
Bryan Stillwell <[EMAIL PROTECTED]> writes:
> >So I grabbed 2.4.0-test11 off rsynch from linuxcare. It built the
> >ieee1394 with no trouble, but when I rebooted, I didn't have a
> >keyboard or a mouse -- no new input layer support, and all my input
> >device fi
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> >So I grabbed 2.4.0-test11 off rsynch from linuxcare. It built the
> >ieee1394 with no trouble, but when I rebooted, I didn't have a
> >keyboard or a mouse -- no new input layer support, and all my input
>
>So I grabbed 2.4.0-test11 off rsynch from linuxcare. It built the
>ieee1394 with no trouble, but when I rebooted, I didn't have a
>keyboard or a mouse -- no new input layer support, and all my input
>device files in /dev have been switched over.
Am I to understand that you hav
>Hey,
>
>So I've been happily running 2.2.x for quite some time. I shifted over
>to using my USB devices under the new input layer and have been
>extremely pleased.
>
>Just recently, I swamped my internal hardrive on my G3 pismo while
>building a debug version of Op
Hey,
So I've been happily running 2.2.x for quite some time. I shifted over
to using my USB devices under the new input layer and have been
extremely pleased.
Just recently, I swamped my internal hardrive on my G3 pismo while
building a debug version of OpenOffice, and bought a Maxtor ext
Well, after reading some about the new input layer (thanks for all help
and directions about this in the thread about Pismo touchpad btw) I now
use the se-latin1.kmap in i386/qwerty. It works great with in X and
console but, I miss my pipe '|' and the at-sign '@'. I've tr
47 matches
Mail list logo
