dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48304] text in fbterm is garbled
Date: Thu, 05 Apr 2012 06:35:53 +0000	[thread overview]
Message-ID: <bug-48304-502-e6n3P6zWJ2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48304-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=48304

Michel Dänzer <michel@daenzer.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|r600g: text in fbterm is    |text in fbterm is garbled
                   |garbled                     |
            Version|XOrg CVS                    |unspecified

--- Comment #4 from Michel Dänzer <michel@daenzer.net> 2012-04-04 23:35:53 PDT ---
This has nothing to do with r600g.

fbterm works fine here; please also attach the output of fbset -i.

As fbterm does all rendering in software, this could be an fbterm or maybe
freetype issue.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-04-05  6:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 10:13 [Bug 48304] New: r600g: text in fbterm is garbled bugzilla-daemon
2012-04-04 18:04 ` [Bug 48304] " bugzilla-daemon
2012-04-04 19:55 ` bugzilla-daemon
2012-04-04 20:45 ` bugzilla-daemon
2012-04-05  6:35 ` bugzilla-daemon [this message]
2012-04-05 12:56 ` [Bug 48304] " bugzilla-daemon
2012-04-05 13:41 ` bugzilla-daemon
2012-04-05 19:32 ` bugzilla-daemon
2012-04-06 10:58 ` bugzilla-daemon

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=bug-48304-502-e6n3P6zWJ2@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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).