linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Beck <nbeck@mpcdata.com>
To: Tomi Valkeinen <tomi.valkeinen@Nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP2 DSS Linux Driver
Date: Wed, 28 Jul 2010 11:57:54 +0100	[thread overview]
Message-ID: <4C500D32.8060408@mpcdata.com> (raw)
In-Reply-To: <1280313123.2427.109.camel@tubuntu.research.nokia.com>

On 28/07/10 11:32, Tomi Valkeinen wrote:
> On Wed, 2010-07-28 at 10:55 +0200, ext Nicholas Beck wrote:
>    
>> Hi Tomi,
>>
>> Firstly, I apologise if you would prefer this on a maillist rather than
>> a direct mail. Please let me know if you would prefer this on a maillist
>> I will post it there instead.
>>      
> cc'ing linux-omap mailing list is always good (cc'd). More people can
> answer, and more people will see the answer.
>    
Thanks and understood. I will make sure that future posts hit the mail list.
>    
>> I am working with the omap2 DSS driver implementation that you created.
>> The DSS linux docs say that MIPI DBI (RFBI) output is working and tested.
>>
>> Please could you let me know what platform you tried this on?
>>      
> That information is a bit outdated. RFBI was working and tested, and the
> platform was Nokia N800. However, the panel driver for N800 was just a
> quickly ported hack, and currently there are no public boards that use
> DSS2 and RFBI.
>
> There has been quite big changes in the DSS2 code, and RFBI is most
> likely broken. There has also been some discussions about RFBI in
> linux-omap mailinglist, but I haven't looked at the RFBI code myself as
> I don't have any board to test it on.
>
>    
>> I am working with some custom hardware, which is largely similar to the
>> OMAP3530EVM, but will use MIPI DBI (RFBI) through a custom FPGA instead
>> of MIPI DPI (RFBI bypass) as used by the EVM's LCD. We are trying to
>> reduce the integration risk by basing this work on a known working platform.
>>      
> Most likely the problems with RFBI are quite small, as the driver did
> work earlier. However, finding those small problems may be a big job =).
> I suggest you search l-o mailing list archives, and try to work with the
> guys there who are trying to use RFBI.
>
>    
Thanks for the info. I'll dig through the archive and see what the 
current state is.

Nick


      reply	other threads:[~2010-07-28 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C4FF08D.4040503@mpcdata.com>
2010-07-28 10:32 ` OMAP2 DSS Linux Driver Tomi Valkeinen
2010-07-28 10:57   ` Nicholas Beck [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=4C500D32.8060408@mpcdata.com \
    --to=nbeck@mpcdata.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@Nokia.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 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).