From: Simon Vincent <simon.vincent@xsilon.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: distorted text
Date: Thu, 28 May 2015 07:06:24 +0000 [thread overview]
Message-ID: <5566BE70.5020906@xsilon.com> (raw)
In-Reply-To: <555C660B.2080808@xsilon.com>
Has anyone else seen this problem?
Regards
Simon
On 20/05/15 17:03, Simon Vincent wrote:
> Sorry slightly incorrect I upgraded to linux v4.1-rc4.
>
> I have done some testing and the display works correctly with clear
> text on Linux v4.0 but is distorted/corrupted on v4.1-rc1. (These are
> tagged releases from https://github.com/torvalds/linux).
>
> I have had a look at the changes but I can't find anything that might
> cause the problem although I don't know much about this part of Linux.
> Any ideas?
>
> Simon
>
> On 20/05/15 11:46, Simon Vincent wrote:
>> Hi,
>>
>> I have previously been using Linux 3.16 with a OLED 128x32 display
>> setup as a fbconsole. This was working well until I upgraded to linux
>> 4.0. Now the console text is displayed on the OLED but the text is no
>> longer clear, it looks distorted.
>> I have uploaded a photo of the problem here.
>> http://s3.postimg.org/66a7lrp2b/IMG_20150520_114135_2.jpg
>>
>> Is this a known bug?
>>
>> Simon
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-fbdev" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-28 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 10:46 distorted text Simon Vincent
2015-05-20 16:03 ` Simon Vincent
2015-05-28 7:06 ` Simon Vincent [this message]
2015-05-28 7:35 ` Geert Uytterhoeven
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=5566BE70.5020906@xsilon.com \
--to=simon.vincent@xsilon.com \
--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 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).