linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rolf Offermanns <roffermanns@sysgo.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: TQM5200 + SM501 FB
Date: Fri, 04 Dec 2009 15:23:16 +0100	[thread overview]
Message-ID: <4B191B54.6030804@sysgo.com> (raw)

Hi All,

does anyone has a working SM501 framebuffer on the STK5200 board? The 
board itself works fine on the 2.6.32 kernel.

I got a patch from TQ which used to work around 2.6.24 but it seems with 
the unification of the "simple mpc5200" boards the sm501 support got lost.

I toyed around with the patch a bit and I got the driver to probe and 
initialize the chip, but I don't get an output on the crt port and an 
open() on /dev/fb0 or /dev/fb1 fails with "no device".

Any hints are welcome.

Thanks,
Rolf.

             reply	other threads:[~2009-12-04 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 14:23 Rolf Offermanns [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-04 22:04 TQM5200 + SM501 FB Wolfgang Denk
2009-12-06  8:30 ` Rolf Offermanns
2009-12-06  9:17   ` Wolfgang Denk

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=4B191B54.6030804@sysgo.com \
    --to=roffermanns@sysgo.com \
    --cc=linuxppc-dev@lists.ozlabs.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).