From: Paul Mackerras <paulus@cs.anu.edu.au>
To: bh40@calva.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Xpmac compatibility
Date: Wed, 10 Feb 1999 14:53:05 +1100 [thread overview]
Message-ID: <199902100353.OAA05305@tango.anu.edu.au> (raw)
In-Reply-To: <19990209204546.006029@mail.mipsys.com> (message from BenH on Tue, 9 Feb 1999 20:45:46 +0100)
BenH <bh40@calva.net> wrote:
> Is the code that sends mouse buttons & movements as keycodes needed only
> for Xpmac compatibility ? Or is it something standard ? I was thinking
Only for Xpmac compatibility AFAIR.
> about conditionally defining it, probably using the CONFIG_FB_COMPAT_XPMAC.
Sounds reasonable.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-02-10 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 19:45 Xpmac compatibility BenH
1999-02-10 3:53 ` Paul Mackerras [this message]
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=199902100353.OAA05305@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=bh40@calva.net \
--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).