From: Martin Costabel <costabel@wanadoo.fr>
To: "Joshua M. Thompson" <funaho@jurai.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.18 and CONFIG_ADB_MOUSE
Date: Sat, 11 Sep 1999 10:04:04 +0200 [thread overview]
Message-ID: <37DA0CF4.74840414@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.9909101954130.10100-100000@ifurita.jurai.org
Sorry for this, I was too tired when I wrote it. Sometimes the day job
can get in the way of successful Linux hacking :-)
I had seen the typo in drivers/char/Config.in, but forgot to correct it.
And then it seemed more logical to have the selection of ADB_MOUSE next
to ADB_KEYBOARD, but maybe it isn't.
Anyway, in 'make menuconfig' the mouse selection is buried rather deep
down, on the 'Character devices' page after things like 'Non-standard
serial port support' and 'Unix98 PTY support'. Let's see... OK, this
seems to be a bug in drivers/char/Config.in. There is an 'endmenu'
missing just before
mainmenu_option next_comment
comment 'Mice'
But, if I put an 'endmenu' there, then 'make xconfig' breaks. And 'make
xconfig' got it right before! (Right = Put 'Mice' and 'Video for Linux'
and so on into the main menu and not in the 'Character devices' menu).
Solution (but this is black magic, I don't understand it and better give
up on this):
Put a line with '#endmenu' instead of 'endmenu' there. Now both 'make
menuconfig' and 'make xconfig' are happy and behave in the same way
(well, almost, in 'make xconfig', the 'watchdog timer' selection is
still on the 'Character devices' page, but the 'watchdog card' selection
is in the main menu). Weird stuff.
Here is the patch:
cvs diff -u drivers/char/Config.in
Index: drivers/char/Config.in
===================================================================
RCS file: /cvs/linux/linux/drivers/char/Config.in,v
retrieving revision 1.80
diff -u -r1.80 Config.in
--- drivers/char/Config.in 1999/09/11 03:39:16 1.80
+++ drivers/char/Config.in 1999/09/11 07:02:10
@@ -61,6 +61,7 @@
fi
dep_tristate 'Support for user-space parallel port device drivers'
CONFIG_PPDEV $CONFIG_PARPORT
fi
+#endmenu
mainmenu_option next_comment
comment 'Mice'
--
Martin
(Not drunk, it's 10am, but feeling slightly seasick after one hour with
the config.in files)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-11 8:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-09 5:18 Paul's devel branch on Lombard? Hugh Caley
1999-09-09 14:25 ` Shaw Terwilliger
1999-09-09 14:51 ` Hugh Caley
1999-09-09 21:03 ` Martin Costabel
1999-09-09 21:30 ` Shaw Terwilliger
1999-09-09 22:45 ` Martin Costabel
1999-09-10 0:07 ` David D. Kilzer
1999-09-10 0:29 ` Paul Mackerras
1999-09-10 9:42 ` Geert Uytterhoeven
1999-09-10 9:46 ` Geert Uytterhoeven
1999-09-10 17:49 ` Martin Costabel
1999-09-10 22:08 ` 2.3.18 and CONFIG_ADB_MOUSE Martin Costabel
1999-09-10 23:55 ` Joshua M. Thompson
1999-09-11 8:04 ` Martin Costabel [this message]
1999-09-13 5:43 ` Joshua M. Thompson
1999-09-13 6:55 ` Martin Costabel
1999-09-13 7:29 ` Geert Uytterhoeven
1999-09-13 8:32 ` Martin Costabel
1999-09-13 8:54 ` Geert Uytterhoeven
1999-09-11 3:37 ` Paul Mackerras
1999-09-11 3:47 ` David D. Kilzer
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=37DA0CF4.74840414@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=funaho@jurai.org \
--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).