From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] viafb: don't setup TMDS if it doesn't exist
Date: Sat, 25 Sep 2010 21:06:29 +0000 [thread overview]
Message-ID: <4C9E6455.5080607@gmx.de> (raw)
In-Reply-To: <20100925195242.871699D401B@zog.reactivated.net>
Daniel Drake schrieb:
> On 25 September 2010 21:20, Florian Tobias Schandinat
> <FlorianSchandinat@gmx.de> wrote:
>> I wonder about that. Current linux-next with an unpatched viafb seems to
>> work well on my XO 1.5. I guess I should notice a missing output?
>
> Strange. I was testing with linus master. Nothing comes up on the
> screen at all, and the display controller dies a scary death (screen
> fades in and out as if the world is ending). Do you know which version
> of the XO-1.5 you are working with?
It's probably just that you tested
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary
while I'm talking about
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
which is pretty much what linus tree will look like after the next merge window
and includes
http://github.com/schandinat/linux-2.6/tree/viafb-next
I think the most relevant patch in it concerning the issue you mentioned is
http://github.com/schandinat/linux-2.6/commit/e029ab0d02b94d633d8e82a46dfdb7fd94a62216
at least that was the point in time where I got rid of the old OLPC-specific
patch which disabled tmds and lvds identification.
(there still is a big diff between linus tree and the XO 1.5 tree I run but at
least viafb should work well after the next merge window)
Thanks,
Florian Tobias Schandinat
next prev parent reply other threads:[~2010-09-25 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 19:52 [PATCH] viafb: don't setup TMDS if it doesn't exist Daniel Drake
2010-09-25 20:20 ` Florian Tobias Schandinat
2010-09-25 20:23 ` Daniel Drake
2010-09-25 21:06 ` Florian Tobias Schandinat [this message]
2010-09-26 14:51 ` Daniel Drake
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=4C9E6455.5080607@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.