From: Martin Costabel <costabel@wanadoo.fr>
To: Chris Gehlker <canyonrat@mac.com>
Cc: Dev List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Problems with building Paul's Stable Release
Date: Fri, 21 Apr 2000 08:24:22 +0200 [thread overview]
Message-ID: <38FFF416.6DBB01A7@wanadoo.fr> (raw)
In-Reply-To: 38FF8897.D80916CC@mac.com
Chris Gehlker wrote:
>
> This is a tiny bug report and a plea for help. I grabbed the latest
> stable release, 2.2.15pre19, from Paul's tree to build for a Sawtooth.
> Reading the archives of this list I see I'm supposed to disable PowerMac
> Keyboard and I'm enabling usb hubs, keyboards and mice but no joy. My
> usb devices are DOA.
Where did you read that you have to disable PowerMac Keyboard? This
doesn't seem right to me. Or do you have a PC keyboard?
> The tiny bug is that the little pearl file mkmap in /drivers/usb has the
> wrong permissions. Please excuse me if I'm violating etiquette by
> reporting such a nit.
This is a longstanding bug in a particular version of the usb drivers.
Both scripts mkmap and mkmap.adb should be executable, but aren't. In
Paul's tree it is half fixed, i.e. mkmap.adb is executable, but mkmap
isn't.
Now for the Macs this should be sufficient, because they need the keymap
made by mkmap.adb (even if you don't have an ADB keyboard!). But for
this you have to have CONFIG_MAC_KEYBOARD=y. If you do this, then mkmap
should never be used.
If you really have to chmod mkmap, then you also need to rm keymap.c
(same goes for mkmap.adb and keymap-mac.c), because in the first
attempt, it probably got created with length zero, and afterwards make
thinks it doesn't have to redo it.
All these are very ugly hacks, and they have rightly disappeared from
more recent usb drivers.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-04-21 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-20 22:45 Problems with building Paul's Stable Release Chris Gehlker
2000-04-21 6:24 ` Martin Costabel [this message]
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=38FFF416.6DBB01A7@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=canyonrat@mac.com \
--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).