From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ken Offer <koffer@arlut.utexas.edu>
Cc: linuxppcdev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Need a Linux PPC kernel which supports the Radeon Mobility 9600
Date: Thu, 16 Oct 2003 17:24:56 +0200 [thread overview]
Message-ID: <1066317895.1407.154.camel@gaston> (raw)
In-Reply-To: <4F1C744C-FFE6-11D7-9F9F-000393467F1A@arlut.utexas.edu>
>
> I have not. I wasn't aware of "module-init-tools". It shouldn't be
> necessary to build and link the 2.6 kernel, should it?
It is necessary for the modules stage to work properly, at least
for the depmod to work
> By the way, I went ahead and installed the 2.6 kernel it built (I
> figured it would be missing some modules, but what the heck...) X11
> appeared to work with the radeonfb driver. KDE asked me for the time,
> date, etc. However, just after I attempted to log in KDE croaked and
> locked up the system while "initializing services". Since it was a
> hard-freeze and I didn't get a kernel opps, I have no feedback other
> than this. I'm hoping it has nothing to do with the radeonfb driver.
Probably not.
> Right now I'm attempting to back-port the 2.6 radeonfb driver to the
> 2.4 kernel myself. I don't know the driver as well as you Ben, but I
> need to make some sort of progress. I'm betting the 2.6 kernel is
> probably too bleeding-edge right now for a deliverable system. :)
>
I did make some backporting (not the complete set of changes, but
some more recent board support).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-16 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 22:10 Need a Linux PPC kernel which supports the Radeon Mobility 9600 Ken Offer
2003-10-15 8:19 ` Benjamin Herrenschmidt
2003-10-15 15:09 ` Ken Offer
2003-10-15 15:22 ` Benjamin Herrenschmidt
2003-10-16 14:37 ` Ken Offer
2003-10-16 15:24 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 21:56 Ken Offer
2003-10-10 22:07 ` Benjamin Herrenschmidt
2003-10-11 21:44 ` Jens Schmalzing
2003-10-12 10:07 ` Benjamin Herrenschmidt
2003-10-12 11:10 ` Sam Ravnborg
2003-10-12 12:18 ` Jens Schmalzing
2003-10-12 16:17 ` Dale Harris
2003-10-14 14:37 ` Ken Offer
2003-10-14 15:14 ` Jens Schmalzing
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=1066317895.1407.154.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=koffer@arlut.utexas.edu \
--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).