From: Martin Costabel <costabel@wanadoo.fr>
To: paulus@linuxcare.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.18pre17 again
Date: Fri, 27 Oct 2000 08:21:10 +0200 [thread overview]
Message-ID: <39F91ED6.CD2AEF23@wanadoo.fr> (raw)
In-Reply-To: 14839.53124.753011.489351@argo.linuxcare.com.au
Paul Mackerras wrote:
> If anyone gets compile errors with my 2.2.18pre17 tree, or the current
> bk tree, please send me your .config. I'm making a collection. :)
I am sorry, but it still doesn't compile with CONFIG_MAGIC_SYSRQ=y. You
would need to patch
--- mac_hid.c Mon Oct 23 13:13:08 2000
+++ drivers/macintosh/mac_hid.c Thu Oct 26 23:24:13 2000
@@ -295,11 +295,11 @@
#ifdef CONFIG_MAGIC_SYSRQ
- ppc_md.ppc_kbd_sysrq_xlate =
mac_hid_kbd_sysrq_xlate;
+ kbd_sysrq_xlate = mac_hid_kbd_sysrq_xlate;
SYSRQ_KEY = 0x69;
#endif
memcpy(pc_key_maps_save, key_maps,
sizeof(key_maps));
memcpy(key_maps, mac_key_maps_save,
sizeof(key_maps));
} else {
#ifdef CONFIG_MAGIC_SYSRQ
- ppc_md.ppc_kbd_sysrq_xlate =
pckbd_sysrq_xlate;
+ kbd_sysrq_xlate = pckbd_sysrq_xlate;
SYSRQ_KEY = 0x54;
#endif
BTW, why didn't you adopt the names from the bk-linuxppc_2_3 tree for
the kbd_sysrq_xlate stuff? IMHO the circular macro definitions
#define kbd_sysrq_xlate (ppc_md.kbd_sysrq_xlate)
#define SYSRQ_KEY (ppc_md.SYSRQ_KEY)
in include/asm-ppc/keyboard.h are asking for trouble. They give you an
error (" parse error before `(' ") if you want to say
ppc_md.kbd_sysrq_xlate = pckbd_sysrq_xlate;
for example. If one day you should decide to #include <asm/keyboard.h>
into arch/ppc/kernel/pmac_setup.c, it won't compile any more.
Another problem I am having must be due to some bug in the screen
blanking code: The X server (Franz's XF-4.0.1) kills itself (and
everything that is running in an X window) after 10 minutes of idling.
This does not happen with 2.4.0-test kernels. It bit me hard, because it
happened while netscape was updating itself inside MOL inside an X
window. Now the MacOS boot partition is severely damaged.
If only MOL would run on 2.4.0 kernels on 603 machines, I would never go
back to 2.2.x kernels.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-27 6:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 6:30 2.2.18pre17 again Paul Mackerras
2000-10-26 14:19 ` Gabriel Paubert
2000-10-27 1:51 ` Paul Mackerras
2000-10-27 6:21 ` Martin Costabel [this message]
2000-10-27 11:59 ` Lombard Sleep Crash (Was: 2.2.18pre17 again) Albrecht Dre_
2000-10-27 14:39 ` Olaf Hering
2000-11-02 12:34 ` Albrecht Dreß
2000-11-02 15:07 ` Claus
2000-11-02 15:28 ` Albrecht Dre_
2000-11-02 18:09 ` Benjamin Herrenschmidt
2000-11-03 10:13 ` Albrecht Dre_
2000-11-03 12:22 ` Michael Schmitz
2000-11-03 12:32 ` Albrecht Dre_
2000-11-03 12:52 ` Michael Schmitz
2000-11-03 14:11 ` Albrecht Dre_
2000-11-03 14:52 ` Michael Schmitz
2000-11-03 21:51 ` Michael Schmitz
2000-11-02 15:35 ` Benjamin Herrenschmidt
2000-11-02 15:43 ` Michael Schmitz
2000-11-02 16:11 ` Benjamin Herrenschmidt
2000-11-02 17:13 ` Michael Schmitz
2000-11-03 15:22 ` Claus
2000-11-03 15:55 ` Benjamin Herrenschmidt
2000-11-03 21:53 ` Michael Schmitz
2000-11-09 1:22 ` Claus
2000-11-09 8:26 ` Michael Schmitz
2000-11-02 17:23 ` Joseph P. Garcia
2000-11-02 18:06 ` Benjamin Herrenschmidt
2000-11-02 22:18 ` Michael Schmitz
2000-11-02 22:56 ` Olaf Hering
2000-11-08 20:35 ` Michael Schmitz
2000-11-08 20:54 ` Benjamin Herrenschmidt
2000-11-08 21:48 ` Michael Schmitz
2000-10-27 19:02 ` 2.2.18pre17 again Olaf Hering
2000-10-28 0:14 ` Olaf Hering
2000-10-31 6:49 ` Michel Lanners
2000-10-31 11:53 ` Benjamin Herrenschmidt
2000-10-31 14:03 ` Gabriel Paubert
2000-10-31 14:48 ` Benjamin Herrenschmidt
2000-10-31 17:20 ` Gabriel Paubert
2000-11-01 1:20 ` Dan Malek
2000-11-01 7:33 ` Michel Lanners
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=39F91ED6.CD2AEF23@wanadoo.fr \
--to=costabel@wanadoo.fr \
--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 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.