All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Stephen Yee <stonepine@126.com>
Cc: sm5xx-devel@lists.berlios.de, Stephen Yee <shyi@bmrtech.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: FYI:  SM5xx toolchain project berliOS registration
Date: Tue, 21 Nov 2006 15:08:11 +0300	[thread overview]
Message-ID: <4562EC2B.9090508@varma-el.com> (raw)
In-Reply-To: <4561F9F2.8020706@126.com>

Hi Stephen,

Stephen Yee wrote:
> Hi All,
>  I want to make Voyager GX PCI Demo Board Ver.A(a PCI cards with
> SiliconMotion SM501 chip) work on PPC 405ep board to support CRT
> monitor, I have ported Andrey Volkov's SiliconMotion SM501 drivers to
> 2.6.17,  and I have modified the module parameter 'active_plane' to CRT,
> but, I can't get anything from the CRT monitor, and the relative console
> messages as following:
It is not sufficient, I'm sorry, but driver is not in production stage.

sm5xx_fb_default_var, module_param(active_plane, int, ....) (at the
bottom of sm5xx_fb.c) must be correct too.

Default/active plane(s) must be, certainly, selected by driver
parameter, but...

> 
> ....
> registered sm5xx-fb device
> sm5xx_fb_enable_controller: Enabling CRT controller
> Console: switching to colour frame buffer device 128x48
> fb0: SM5xx CRT frame buffer device
> .....
> 
> is Here a  successful  story  about using SM501 on PPC platform with
> this driver?  and would you please give me some advices to drive this
> devices?
Properly speaking, we are use SM5xx on our MPC5200 based board.
So this driver, by definition, working on PPC ;).
AFAIK, only one problem exist in kernel FB: it is 16bpp (AKA RGB565).
(in DirectFB and in X such problem worked around)

P.S. Stephen, as I pointed in my mail, which you are quote,
sm5xx-devel@lists.berlios.de is working, so, please, CC such mails
in this list too.

--
Andrey Volkov


> Thanks in Advance.
> Stephen.
> 
> Andrey Volkov wrote:
> 
>> Hi all,
>>
>> Yesterday I issued new SiliconMotion SM501 drivers
>> project request to berlios, and receive
>> approvement couple hours ago.
>>
>> So project home page is:
>>
>> http://developer.berlios.de/projects/sm5xx/
>>
>> Anyone who wants admin/write-access, please register with
>> berlios and tell me your account.
>>
>> SVN will be activated in nearest hours.
>> Berlios has direct shell access to your repos.
>> So if there are any svn/CVS-dumps to import or any
>> scripts to set up...
>>
>> The central mailing list
>>
>>     sm5xx-devel@lists.berlios.de
>>
>> will be active soon too.
>>
>> -- 
>> Happy hacking ;),
>>
>> Andrey Volkov
>> Varma Electronics Oy
>>
>> -------- Original Message --------
>> Subject: BerliOS Developer Project Approved
>> Date: Wed, 11 Oct 2006 12:49:58 +0200 (CEST)
>> From: admin@berlios.de
>> To: avolkov@varma-el.com
>>
>> Your project registration for BerliOS Developer has been approved.
>>
>> Project Full Name:  SM5xx Toolchain
>> Project Unix Name:  sm5xx
>> CVS Server:         cvs.berlios.de
>> SVN Server:         svn.berlios.de
>> Shell Server:       shell.berlios.de
>> Web Server:         sm5xx.berlios.de
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>>  
>>
> 
> 
> 
> 

      parent reply	other threads:[~2006-11-21 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 14:36 FYI: SM5xx toolchain project berliOS registration Andrey Volkov
2006-10-11 14:36 ` Andrey Volkov
2006-11-20 18:54 ` Stephen Yee
2006-11-20 21:41   ` Wolfgang Denk
2006-11-22 19:03     ` Stephen Yee
2006-11-21 12:08   ` Andrey Volkov [this message]

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=4562EC2B.9090508@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=shyi@bmrtech.com \
    --cc=sm5xx-devel@lists.berlios.de \
    --cc=stonepine@126.com \
    /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.