From: Jerome Glisse <j.glisse@gmail•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Tue, 5 Apr 2005 13:52:33 +0200 [thread overview]
Message-ID: <4240b91605040504525fd877e5@mail.gmail.com> (raw)
In-Reply-To: <1112656372.26086.88.camel@gaston>
I almost successfully run the 2.6.12-rc2, there were some
bad old stuff lying around. But i needed the two workaround
to compile it. So maybe this two could be applied to the kernel ?
Now the only issue which remains is that the radeon framebuffer
no more set a proper mode for my screen. The screen complain
about a out of range mode. But as soon as X start i get a proper
mode set but can't switch to console.
The screen is a crt one on a radeon 9600 with dvi->vga adapter.
Which works well on 2.6.10
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 ?
Jerome Glisse
next prev parent reply other threads:[~2005-04-05 11:52 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 [this message]
2005-04-05 12:39 ` Andreas Schwab
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=4240b91605040504525fd877e5@mail.gmail.com \
--to=j.glisse@gmail$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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