linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: howarth@bromo.med.uc.edu (Jack Howarth)
Cc: Kostas Gewrgiou <gewrgiou@imbc.gr>, linuxppc-dev@lists.linuxppc.org
Subject: Re: patch to get latest XFree 4.0 snapshot (xf3918) to work on ppc with r128
Date: Fri, 3 Mar 2000 17:14:23 -0500	[thread overview]
Message-ID: <00030317250700.01446@localhost.localdomain> (raw)
In-Reply-To: <200003031924.LAA72531@bromo.med.uc.edu>


Hi Jack,

>     I am not sure if this may become a problem but be aware that the
> usb code from linux-pmac-devel is broken on the Sawtooth G4's and the
> newer portables. So you may want to be careful when you backport any
> of that into the linux-pmac-stable tree.

Actually, I won't actually backport anything from 2.3.X.  The problem is that
the XFree 4.0 Xservers expect bit 3 to always be set in the first character
read from the input buffer of the mouse doing IMPS/2 otherwise it assumes
something got out of sync and throws that character out.

So to make XF 4.0 work with linuxpmac 2.2.X kernels all we have to do in "or" in
0x8 (to set bit 3) on the first character so that it correctly does IMPS/2
(2.3.X already has this fix in place).

--- drivers/usb/mouse.c.prev    Fri Mar  3 17:18:37 2000
+++ drivers/usb/mouse.c Fri Mar  3 17:19:56 2000
@@ -183,6 +183,7 @@
                switch (state) {
                case 0: { /* buttons and sign */
                        int buttons = mouse->buttons;
+                        buttons = buttons | 0x08; // set bit 3 to fit imps/2
                        mouse->buttons = 0;
                        if (mouse->dx < 0)
                                buttons |= 0x10;


I still need to recompile and check this with an unpatched XFree 4.0 Xserver
but this should do the trick.

Thanks,

Kevin

 --
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario  N6A-3K7  CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2000-03-03 22:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003031924.LAA72531@bromo.med.uc.edu>
2000-03-03 22:14 ` Kevin Hendricks [this message]
     [not found] <v03110700b4dd777b032a@[209.183.136.166]>
2000-02-28  0:29 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on ppc with r128 Kostas Gewrgiou
2000-03-03 20:51   ` Kevin Hendricks
2000-02-25 14:36 Kevin_Hendricks
  -- strict thread matches above, loose matches on Subject: below --
2000-02-25  0:07 Dan Bethe
2000-02-25  8:04 ` Geert Uytterhoeven
2000-02-24 15:06 Kevin Hendricks
2000-02-24 17:48 ` Kostas Gewrgiou
2000-02-24 18:53   ` Kevin Hendricks
2000-02-24 22:25   ` Kevin Hendricks
2000-02-25  3:19     ` Kevin Hendricks
2000-02-25 12:28     ` Kostas Gewrgiou

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=00030317250700.01446@localhost.localdomain \
    --to=khendricks@ivey.uwo.ca \
    --cc=gewrgiou@imbc.gr \
    --cc=howarth@bromo.med.uc.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).