From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.0-test5 observations
Date: Sat, 29 Jul 2000 22:06:54 +0100 [thread overview]
Message-ID: <200007292107.WAA04363@hyperion.valhalla.net> (raw)
Hi,
1. My build problem was solved by:
--- bk-devel/drivers/input/adbhid.c Sat Jul 29 08:04:54 2000
+++ linux-2.4.0-t5-wrk/drivers/input/adbhid.c Sat Jul 29 17:28:42 2000
@@ -40,9 +40,9 @@
#include <linux/input.h>
#include <linux/kbd_ll.h>
-#include <asm/adb.h>
-#include <asm/cuda.h>
-#include <asm/pmu.h>
+#include <linux/adb.h>
+#include <linux/cuda.h>
+#include <linux/pmu.h>
#include <asm/backlight.h>
#define KEYB_KEYREG 0 /* register # for key up/down data */
======
This may be related to my so-called "broken" distro re. kernel builds - but
there it is...
========
2. The sound [AWACS rev 3] (at present) exhibits the following behaviour
(built as modules).
The first buffer plays and then.... silence...
I don't know if it's related, but the kernel log is filling up with:
Jul 29 22:50:41 athena VFS: Disk change detected on device ide1(22,0)
Jul 29 22:50:41 athena last message repeated 684 times
messages... IIRC this happened also on 2.4.0-test4
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-07-29 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200007292107.WAA04363@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--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).