From: Wilmer van der Gaast <lintux@lintux.cx>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Oops in current linux-2.5-benh
Date: Fri, 14 Nov 2003 12:17:35 +0100 [thread overview]
Message-ID: <20031114111735.GA13590@gaast.net> (raw)
In-Reply-To: <1068793571.9828.40.camel@gaston>
Benjamin Herrenschmidt (benh@kernel.crashing.org) wrote:
> Does it happen if you built i2c in the kernel instead of as a module ?
It already was in the kernel (except for keywest), but somehow it
managed to load the i2c-core module anyway.
This was possible because linux-2.6.0-test9 (also on my machine) had its
modules in /lib/modules/2.6.0-test9 as well. I added -benh to the
EXTRAVERSION in linuxppc and recompiled/-installed the whole
kernel+modules. Isn't it better to keep that in EXTRAVERSION on the
bk/rsync source as well?
Anyway, it certainly looks a lot better now!!! aumix works (didn't work
in -test9), and even sleeping works! (I'd never seen that working in
Linux before)
This is fantastic. Okay, thanks. Keep up the good work, 2.6-benh works
better for me than 2.4-benh already.
By the way, not really on-topic, but I'm probably not the first to see
this problem: The UTF8 stuff in 2.6 breaks linedrawing chars and makes
almost every curses application ugly and unusable. What to do about
that?
Wilmer van der Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| lintux : :' : lintux.cx | | OSS Programmer www.bitlbee.org |
| at `. `~' debian.org | | www.algoritme.nl www.lintux.cx |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-14 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 1:10 Oops in current linux-2.5-benh Wilmer van der Gaast
2003-11-14 7:06 ` Benjamin Herrenschmidt
2003-11-14 10:35 ` Wilmer van der Gaast
2003-11-14 11:17 ` Wilmer van der Gaast [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=20031114111735.GA13590@gaast.net \
--to=lintux@lintux.cx \
--cc=benh@kernel.crashing.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).