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 20:20:47 +0000 [thread overview]
Message-ID: <4C9E599F.3040208@gmx.de> (raw)
In-Reply-To: <20100925195242.871699D401B@zog.reactivated.net>
Hi,
Daniel Drake schrieb:
> The OLPC XO-1.5 does not have this particular output interface.
> However, init_tmds_chip_info() always assumes it to be present,
> ignoring failure codes from viafb_tmds_trasmitter_identify().
This is true. I noticed it too while working on the identify logic. I will carry
it on in my tree after I adjusted it (because I replaced the OK/FAIL madness by
bool, it will change to "if (!viafb_tmds_trasmitter_identify())")
> This fixes lack of output on the XO-1.5 laptop display.
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?
> Thanks to Jon Nettleton for helping identify the problematic code.
>
> Signed-off-by: Daniel Drake <dsd@laptop.org>
Thanks,
Florian Tobias Schandiant
> ---
> drivers/video/via/hw.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/via/hw.c b/drivers/video/via/hw.c
> index 7dcb4d5..a24d03f 100644
> --- a/drivers/video/via/hw.c
> +++ b/drivers/video/via/hw.c
> @@ -2125,7 +2125,8 @@ static void init_gfx_chip_info(int chip_type)
>
> static void init_tmds_chip_info(void)
> {
> - viafb_tmds_trasmitter_identify();
> + if (viafb_tmds_trasmitter_identify() != OK)
> + return;
>
> if (INTERFACE_NONE = viaparinfo->chip_info->tmds_chip_info.
> output_interface) {
next prev parent reply other threads:[~2010-09-25 20:20 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 [this message]
2010-09-25 20:23 ` Daniel Drake
2010-09-25 21:06 ` Florian Tobias Schandinat
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=4C9E599F.3040208@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.