From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Enric Balletbo Serra <eballetbo@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: omap DSS fails with tft410 driver panel?
Date: Thu, 29 Nov 2012 16:31:47 +0200 [thread overview]
Message-ID: <50B771D3.8050907@ti.com> (raw)
In-Reply-To: <CAGDS+n=oQYr+24mX6bdgtW=fzvfvfX5rAvNXXpxM4YKPxHDodQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On 2012-11-29 16:18, Steve Sakoman wrote:
> On Thu, Nov 29, 2012 at 3:22 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> On 2012-11-27 21:15, Steve Sakoman wrote:
>>> It seems that dss_mgr_check_timings is being called with a null dssdev->manager.
>>>
>>> Other than the fact that there should be a null pointer check in the
>>> code, it seems that this is a regression since it used to be possible
>>> to switch the default display in this fashion. Is this no longer
>>> allowed?
>>
>> It is allowed. Which kernel is that? I tried v3.7-rc4 and the current
>> omapdss master, both work for me with overo + lcd43 add on.
>
> It is stock Linux 3.6 (i.e. commit a0d271cbfed1dd50278c6b06bead3d00ba0a88f9)
Still can't reproduce. So does the null pointer deref happen at boot
time? What display related kernel boot options do you have? This looks
funny, considering lcd43 is a bit smaller lcd:
[ 3.483062] fbcvt: 1024x768@60: CVT Name - .786M3-R
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2012-11-29 14:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:58 omap DSS fails with tft410 driver panel? Enric Balletbo Serra
2012-10-12 10:56 ` Tomi Valkeinen
2012-10-15 16:08 ` Enric Balletbo Serra
2012-10-16 7:30 ` Tomi Valkeinen
2012-11-22 0:08 ` Steve Sakoman
2012-11-22 8:47 ` Tomi Valkeinen
2012-11-23 6:14 ` Steve Sakoman
2012-11-23 8:46 ` Tomi Valkeinen
2012-11-23 15:20 ` Steve Sakoman
2012-11-27 11:32 ` Tomi Valkeinen
2012-11-27 19:15 ` Steve Sakoman
2012-11-29 11:22 ` Tomi Valkeinen
2012-11-29 11:33 ` Enric Balletbo Serra
2012-11-29 14:24 ` Steve Sakoman
2012-11-29 14:30 ` Enric Balletbo Serra
2012-11-29 14:18 ` Steve Sakoman
2012-11-29 14:31 ` Tomi Valkeinen [this message]
2012-11-29 14:53 ` Steve Sakoman
2012-11-29 14:56 ` Tomi Valkeinen
2012-12-18 8:31 ` Javier Martinez Canillas
2012-12-18 11:23 ` Javier Martinez Canillas
2012-12-18 13:45 ` Javier Martinez Canillas
2012-12-19 8:33 ` Tomi Valkeinen
2012-12-19 11:27 ` Javier Martinez Canillas
2012-12-19 8:24 ` Tomi Valkeinen
2012-12-21 8:30 ` Laurent Pinchart
2012-12-21 10:19 ` Javier Martinez Canillas
2013-09-12 11:12 ` pawel cern
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=50B771D3.8050907@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=eballetbo@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
--cc=tony@atomide.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).