From: Paul Mackerras <paulus@cs.anu.edu.au>
To: tmrini@ntplx.net
Cc: brad@turbolinux.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: rsync kernel compile fails
Date: Fri, 4 Jun 1999 12:02:10 +1000 [thread overview]
Message-ID: <199906040202.MAA04489@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.05.9906031521390.731-100000@pc.wackyland.com> (message from Tom Rini on Thu, 3 Jun 1999 15:23:46 -0400 (EDT))
Tom Rini <tmrini@ntplx.net> wrote:
> It's actually not too hard to do. (I did it to a vger tree for a while).
> Just gotta backport the keyboard changes from 2.2.8 (or was it 7 when usb
> went in?) and then fix a few problems that will no doubt show up w/ the
> multikeyboard patch. It'll work, and should be good enough until one of
> the OHCI drivers in the new USB stack works w/ ppc (tho I suspect it might
> be a bit of a pain, w/ the kernel_thread link problem, or whatever it
> was...)
Do you have a recent 2.2.x tree that all works?
The reason I was thinking of converting the USB keycodes to ADB
keycodes is that that is what will have to happen with the new USB
stack (either that or converting everything to PC keycodes, which will
break a lot of things).
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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-06-04 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-02 7:07 rsync kernel compile fails Brad Midgley
1999-06-02 12:53 ` Tom Rini
1999-06-03 5:58 ` Paul Mackerras
1999-06-03 19:23 ` Tom Rini
1999-06-04 2:02 ` Paul Mackerras [this message]
1999-06-04 2:17 ` Tom Rini
1999-06-04 2:37 ` Paul Mackerras
1999-06-04 2:57 ` Tom Rini
1999-06-04 4:01 ` Problem with linux/in.h Patrik Jonsson
1999-06-04 4:27 ` Matt McLean
1999-06-04 4:31 ` Paul Mackerras
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=199906040202.MAA04489@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=brad@turbolinux.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tmrini@ntplx.net \
/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).