From: Pavel Machek <pavel@ucw.cz>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, will.deacon@arm.com,
catalin.marinas@arm.com
Subject: Re: 3.12-rc1: no longer compiles for Nokia n900 (omap based), display no longer works
Date: Thu, 26 Sep 2013 02:23:49 +0200 [thread overview]
Message-ID: <20130926002349.GA26599@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130919184703.GE30568@blackmetal.musicnaut.iki.fi>
Hi!
> On Thu, Sep 19, 2013 at 11:44:02AM +0200, Pavel Machek wrote:
> > something in 3.12-rc1 broke display :-(. (dmesg diff attached at the
> > end, maybe someone knows...)
>
> 3.12-rc1 for N900 compiles and works (also display) here with binutils
> 2.23.2.
I updated to eldk-5.4, and now it compiles, but still no display on
> > + omapfb omapfb: no displays
>
> [...]
>
> > - acx565akm spi1.2: omapfb: acx565akm rev 12 LCD detected
>
> I think this is because the panel driver has changed, and the old one
> was deleted. You need to change your kernel configuration with something
> like below:
>
> -CONFIG_PANEL_ACX565AKM=y
> +CONFIG_DISPLAY_PANEL_SONY_ACX565AKM=y
Thanks for the hint.. but apparently it was not enough. Still no
display on qemu :-(.
Anyway, "make oldconfig" is expected to produce working kernel, which
is clearly not case here. Perhaps this should be added to fix that?
[Who can take the patch?]
Pavel
PS: whoever named directory in kernel sources "displays-new" should...
think again.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
index 6c90885..d3eabd2 100644
--- a/drivers/video/omap2/displays-new/Kconfig
+++ b/drivers/video/omap2/displays-new/Kconfig
@@ -40,6 +40,7 @@ config DISPLAY_PANEL_DSI_CM
config DISPLAY_PANEL_SONY_ACX565AKM
tristate "ACX565AKM Panel"
+ default PANEL_ACX565AKM
depends on SPI && BACKLIGHT_CLASS_DEVICE
help
This is the LCD panel used on Nokia N900
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2013-09-26 0:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 9:30 3.12-rc1: no longer compiles for Nokia n900 (omap based) Pavel Machek
2013-09-19 9:36 ` Will Deacon
2013-09-19 9:57 ` Pavel Machek
2013-09-23 23:59 ` new binutils needed for arm in 3.12-rc1 Pavel Machek
2013-09-24 2:13 ` Rob Landley
2013-09-24 12:11 ` Måns Rullgård
2013-09-24 21:23 ` Rob Landley
2013-09-24 21:48 ` Russell King - ARM Linux
2013-09-25 1:13 ` Rob Landley
2013-09-25 2:07 ` Nicolas Pitre
2013-09-25 15:23 ` Rob Landley
2013-09-25 15:52 ` Måns Rullgård
2013-09-26 0:10 ` Rob Landley
2013-09-26 22:24 ` Måns Rullgård
2013-09-25 16:13 ` Nicolas Pitre
2013-09-26 22:48 ` Rob Landley
2013-09-27 19:41 ` Pavel Machek
2013-09-28 8:43 ` Pavel Machek
2013-09-25 20:44 ` Russell King - ARM Linux
2013-09-25 20:49 ` Måns Rullgård
2013-09-26 22:50 ` Rob Landley
2013-09-26 7:18 ` Geert Uytterhoeven
2013-09-28 9:03 ` richard -rw- weinberger
2013-09-24 2:20 ` Rob Landley
2013-09-19 9:44 ` 3.12-rc1: no longer compiles for Nokia n900 (omap based), display no longer works Pavel Machek
2013-09-19 18:47 ` Aaro Koskinen
2013-09-26 0:23 ` Pavel Machek [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=20130926002349.GA26599@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=will.deacon@arm.com \
/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).