atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Geert Uytterhoeven]

Hi Michael,

On Sat, Apr 30, 2011 at 01:35, Michael Schmitz
<schmitzmic@googlemail.com> wrote:
> Falcon CT60, 14MB/512MB no swap:
>
> Out of memory: Kill process 8644 (malloctest) score 967 or sacrifice child
> Killed process 8644 (malloctest) total-vm:512244kB, anon-rss:510088kB,
> file-rss:284kB

Ah, real hardware ;-)

Any chance you can try the mouse (e.g. with gpm), and check if
http://permalink.gmane.org/gmane.linux.ports.m68k/1867 is needed, so we know
if this is an ARAnyM issue or not?

Thx!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Michael Schmitz]

Hi Geert,

>> Falcon CT60, 14MB/512MB no swap:
>>
>> Out of memory: Kill process 8644 (malloctest) score 967 or sacrifice child
>> Killed process 8644 (malloctest) total-vm:512244kB, anon-rss:510088kB,
>> file-rss:284kB
>
> Ah, real hardware ;-)

Slow but still works :-)

> Any chance you can try the mouse (e.g. with gpm), and check if
> http://permalink.gmane.org/gmane.linux.ports.m68k/1867 is needed, so we know
> if this is an ARAnyM issue or not?

If I can find a version of gpm that works, sure! Due to my ongoing
battle with the SCSI driver the 2.6 test system is really minimal ...

Cheers,

  Michael

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Michael Schmitz]

Hi Geert,

>> Ah, real hardware ;-)
>
> Slow but still works :-)
>
>> Any chance you can try the mouse (e.g. with gpm), and check if
>> http://permalink.gmane.org/gmane.linux.ports.m68k/1867 is needed, so we know
>> if this is an ARAnyM issue or not?
>
> If I can find a version of gpm that works, sure! Due to my ongoing
> battle with the SCSI driver the 2.6 test system is really minimal ...

I've installed gpm but all I ever get when I move the mouse is
keyboard overruns. Does that ring a bell, anyone?

Cheers,

  Michael

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Michael Schmitz]

Hi again,

> I've installed gpm but all I ever get when I move the mouse is
> keyboard overruns. Does that ring a bell, anyone?

Looks like I need to move the mouse real slow - it appears the patch
is still needed. Moving the mouse down moves the cursor up. The
buttons are reversed as well.

I'll have to put the actual input interface call in a tasklet perhaps,
to shorten the time spent in the mouse interrupt handler.

Cheers,

  Michael

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Finn Thain]

On Fri, 6 May 2011, Michael Schmitz wrote:

> Hi again,
> 
> > I've installed gpm but all I ever get when I move the mouse is 
> > keyboard overruns. Does that ring a bell, anyone?
> 
> Looks like I need to move the mouse real slow - it appears the patch is 
> still needed. Moving the mouse down moves the cursor up. The buttons are 
> reversed as well.
> 
> I'll have to put the actual input interface call in a tasklet perhaps, 
> to shorten the time spent in the mouse interrupt handler.

The input interface overhead is cheap enough with ADB so I don't think 
that's the problem. The printk(KERN_DEBUG "Keyboard overrun\n") in the 
interrupt handler would be costly though. The comments in atakeyb.c could 
be taken to mean that overruns are expected from fast mouse movements...

Finn

> 
> Cheers,
> 
>   Michael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Michael Schmitz]

Hi Finn,

>> I'll have to put the actual input interface call in a tasklet perhaps,
>> to shorten the time spent in the mouse interrupt handler.
>
> The input interface overhead is cheap enough with ADB so I don't think
> that's the problem. The printk(KERN_DEBUG "Keyboard overrun\n") in the
> interrupt handler would be costly though. The comments in atakeyb.c could
> be taken to mean that overruns are expected from fast mouse movements...

That's always been the case but it's not been quite as bad in old kernels.

Moving input syncing  and even reporting of mouse movement into a
software interrupt does not appear to help much. Not generating the
keyboard overun message does help a bit but there's a lot of
'unhandled scancode 7d' messages still happening. These can be
suppressed in the atakbd.c driver.

I'll give the various options a bit more testing - not sure the added
complexity of using a work queue is worth the effort.

Cheers,

  Michael

Re: atarimouse (was: Re: [git pull] m68k SLUB fix for 2.6.39)

[Geert Uytterhoeven]

On Fri, May 6, 2011 at 10:42, Michael Schmitz <schmitzmic@googlemail.com> wrote:
>> I've installed gpm but all I ever get when I move the mouse is
>> keyboard overruns. Does that ring a bell, anyone?
>
> Looks like I need to move the mouse real slow - it appears the patch
> is still needed. Moving the mouse down moves the cursor up. The
> buttons are reversed as well.
>
> I'll have to put the actual input interface call in a tasklet perhaps,
> to shorten the time spent in the mouse interrupt handler.

Thanks, will apply and queue for 2.6.40.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds