All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: brad@turbolinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: rsync kernel compile fails
Date: Thu, 3 Jun 1999 15:58:31 +1000	[thread overview]
Message-ID: <199906030558.PAA00552@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.3.95.990602005536.28345A-100000@pacific.pht.com> (message from Brad Midgley on Wed, 2 Jun 1999 01:07:06 -0600 (MDT))


Brad Midgley <brad@turbolinux.com> wrote:

> is the rsync kernel supposed to be working? i haven't changed my config
> but it fails to compile:

Well, the first problem is that drivers/Makefile goes into the usb
subdirectory for CONFIG_USB rather than the uusbd subdirectory.  Also
that tree doesn't have the multi-keyboard patch (and it won't apply
easily).

I have a 2.3.4 kernel working but without USB.  I plan to work on
getting the new USB stuff working on the iMac soon.  But in the
meantime maybe I need to get a recent 2.2.x kernel working with the
old UUSBD stack.  What I might do actually is kludge the USB keyboard
driver to convert all the keycodes to ADB keycodes, instead of
continuing with the multi-keyboard patch.

I have updated the rsync repository so that the linux-pmac-stable
module has the 2.2.7 tree that used to be in the linux-pmac-devel
module, and the linux-pmac-devel module now has a 2.3.4 tree.

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.   ]]

  parent reply	other threads:[~1999-06-03  5:58 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 [this message]
1999-06-03 19:23   ` Tom Rini
1999-06-04  2:02     ` Paul Mackerras
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=199906030558.PAA00552@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.