From: BenH <bh40@calva.net>
To: Shaw Terwilliger <sterwill@io.nu>, paulus@linuxcare.com
Cc: linuxppc-dev@lists.linuxppc.org, dan@netx4.com
Subject: Re: 2.3.30-pre3
Date: Mon, 29 Nov 1999 00:06:45 +0100 [thread overview]
Message-ID: <19991129000645.003441@smtp.calvacom.fr> (raw)
In-Reply-To: <19991128154913.A15762@io.nu>
On Sun, Nov 28, 1999, Shaw Terwilliger <sterwill@io.nu> wrote:
>I can make diffs if anyone wants them; I'm sure some other people would
>rather like to build from Paul's unstable tree. :) I'd been using
>his stable tree, but for the last 3 months, I can't boot one of his
>stable kernels without getting a machine check somewhere in init.
>The unstable ones have no problems with it, although my USB mouse seems
>to have stopped working... (so now I'm trying to make Xpmac use some
>keys to emulate mouse buttons, but they seem hard-coded, so it'll be
>a little harder than I thought).
Yes, please, send me your patches. Paul will be away for a few weeks and
I want to move all my patches (there are more coming ;) to 2.3.x asap.
BTW, dmasound is broken in Paul's current stable 2.2.14pre. I don't know
yet what's going on but it looks like the driver had major changes
(backported sound in from 2.3.x ?). I can't get any sound output on my
wallstreet anymore. I'll try to look into this next week.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-28 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-28 21:35 2.3.30-pre3 Geert Uytterhoeven
1999-11-28 21:49 ` 2.3.30-pre3 Shaw Terwilliger
1999-11-28 21:54 ` 2.3.30-pre3 Eric Benard
1999-11-28 23:06 ` BenH [this message]
1999-11-29 4:17 ` 2.3.30-pre3 Shaw Terwilliger
1999-11-29 8:19 ` 2.3.30-pre3 Martin Costabel
1999-11-30 20:07 ` 2.3.30-pre3 Paul Mackerras
1999-11-30 20:39 ` 2.3.30-pre3 Shaw Terwilliger
1999-11-30 20:44 ` 2.3.30-pre3 Ani Joshi
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=19991129000645.003441@smtp.calvacom.fr \
--to=bh40@calva.net \
--cc=dan@netx4.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
--cc=sterwill@io.nu \
/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).