From: Chris Leishman <chris@sharinga.com>
To: Paul Mackerras <paulus@linuxcare.com.au>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.18-pre17 candidate
Date: Tue, 31 Oct 2000 02:39:14 +1100 [thread overview]
Message-ID: <20001031023914.B364@nina.dev.fol> (raw)
In-Reply-To: <14837.11341.207379.903189@argo.linuxcare.com.au>; from paulus@linuxcare.com.au on Tue, Oct 24, 2000 at 05:29:33PM +1100
On Tue, Oct 24, 2000 at 05:29:33PM +1100, Paul Mackerras wrote:
<snip>
> I'll be interested to hear how people go with it. I'll check the
> changes into the bitkeeper linuxppc_2_2 tree within the next day or
> so. If it goes OK I'll send the patch to Alan for inclusion in
> 2.2.18.
>
> Paul.
If you compile the GMAC driver as a module it complains about an unresolvable
symbol "feature_set_gmac_phy_reset". This is a symbol in the matching kernel,
so I'm not sure whats going on...
Also, when I tried using the new input stuff my mapping of right/middle mouse
buttons to F9 and F10 (use append="adb_buttons=101,109" in yaboot) stopped
working.
Chris
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-30 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 6:29 2.2.18-pre17 candidate Paul Mackerras
2000-10-24 7:32 ` Andreas Tobler
2000-10-24 11:06 ` Paul Mackerras
2000-10-24 11:53 ` Andreas Tobler
2000-10-24 9:13 ` Martin Costabel
2000-10-24 11:11 ` Paul Mackerras
2000-10-24 23:21 ` Martin Costabel
2000-10-24 20:18 ` Olaf Hering
2000-10-24 16:15 ` Is the difference in IRQ maps between 2.4/2.2 intentional? Vitaly Luban
2000-10-24 20:38 ` Matt Porter
2000-10-25 5:01 ` 2.2.18-pre17 candidate Paul Mackerras
2000-10-25 13:38 ` linux-pmac-benh off (WAS: " Benjamin Herrenschmidt
2000-10-30 15:39 ` Chris Leishman [this message]
2000-10-30 18:13 ` Michael Schmitz
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=20001031023914.B364@nina.dev.fol \
--to=chris@sharinga.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
/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).