From: Andreas Schwab <schwab@suse.de>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Tue, 05 Apr 2005 14:39:36 +0200 [thread overview]
Message-ID: <je1x9pv1mf.fsf@sykes.suse.de> (raw)
In-Reply-To: <4240b91605040504525fd877e5@mail.gmail.com> (Jerome Glisse's message of "Tue, 5 Apr 2005 13:52:33 +0200")
Jerome Glisse <j.glisse@gmail.com> writes:
> I will try t look at radeon framebuffer see if i can find anythings.
> Any idea of which change on that code may be the origin of this ?
I'd suggest looking at the changes between rc1 and rc2 first. On my iBook
G3 with Radeon M6 I'm also having problems with rc2, whereas rc1 is
working fine. I haven't found the time to look closer yet.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-04-05 12:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:32 linux 2.6.12-rc1-bk5 compilation error Jerome Glisse
2005-04-04 10:51 ` Jerome Glisse
2005-04-04 11:52 ` Jerome Glisse
2005-04-04 12:41 ` Benjamin Herrenschmidt
2005-04-04 19:11 ` Jerome Glisse
2005-04-04 23:12 ` Benjamin Herrenschmidt
2005-04-05 11:52 ` Jerome Glisse
2005-04-05 12:39 ` Andreas Schwab [this message]
2005-04-05 15:17 ` Jerome Glisse
2005-04-05 23:12 ` Benjamin Herrenschmidt
2005-04-05 23:25 ` Andreas Schwab
2005-04-05 23:11 ` Benjamin Herrenschmidt
2005-04-07 17:10 ` Tom Rini
2005-04-08 10:13 ` Jerome Glisse
2005-04-08 15:34 ` [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error) Tom Rini
2005-04-08 22:27 ` Jerome Glisse
2005-04-08 23:47 ` 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=je1x9pv1mf.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=j.glisse@gmail.com \
--cc=linuxppc-dev@ozlabs.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).