From: Benjamin Herrenschmidt <bh40@calva.net>
To: Martin Costabel <costabel@wanadoo.fr>
Cc: <linuxppc-dev@lists.linuxppc.org>, <paulus@linuxcare.com.au>
Subject: Re: Patches for 2.4.0-test7
Date: Sun, 27 Aug 2000 00:36:03 +0200 [thread overview]
Message-ID: <20000826223603.5117@192.168.1.10> (raw)
In-Reply-To: <39A8379C.E4EBB33A@wanadoo.fr>
>
>I wouldn't mind changing the keymaps, but I really would like to use the
>same keymaps for 2.2.x kernels, for 2.4.0-test kernels with
>CONFIG_ADB_KEYBOARD and with CONFIG_INPUT_ADBHID.
Well, my kernel for now are the only 2.2 to contain the new stuff and
support for linux keycodes. It's currently a different implementation
than the one in 2.4. I beleive that at a given point in the future, we'll
inherit from the 2.4 version in our 2.2 kernels via the USB backport.
>Yes, it is still there, I just verified. There must be some difference
>between Paul's kernel and the bitkeeper tree that causes this. Here is
>another strange observation:
>
>I type "printenv", and LD_LIBARY_PATH is listed with the other env
>variables (with "env", it does not get listed). Now I use the newly
>recovered strace (see below) to try to understand what printenv does
>differently from env. Well, "strace printenv" does not show
>LD_LIBARY_PATH any more!
Ok, I'll look if I see something, but we are in parts of the kernel here
that I don't know very well. Paul, any idea ?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-26 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-26 13:12 Patches for 2.4.0-test7 Martin Costabel
2000-08-26 16:41 ` Benjamin Herrenschmidt
2000-08-26 21:33 ` Martin Costabel
2000-08-26 22:36 ` Benjamin Herrenschmidt [this message]
2000-08-27 16:28 ` Michael Schmitz
2000-08-27 22:54 ` Paul Mackerras
2000-08-28 7:38 ` Martin Costabel
2000-08-28 9:34 ` Benjamin Herrenschmidt
2000-08-28 10:43 ` Michael Schmitz
[not found] ` <Pine.LNX.4.10.10008281239570.28749-100000@opal.biophys.uni -duesseldorf.de>
2000-08-28 11:51 ` Franz Sirl
2000-08-27 9:59 ` Paul Mackerras
2000-08-27 12:02 ` Benjamin Herrenschmidt
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=20000826223603.5117@192.168.1.10 \
--to=bh40@calva.net \
--cc=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 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).