All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add suport for the graphic	controller included in	the JADE SOC
Date: Thu, 02 Jul 2009 11:27:15 +0200	[thread overview]
Message-ID: <4A4C7D73.1080502@denx.de> (raw)
In-Reply-To: <4A4C6999.2E8A.0063.0@graf-syteco.de>

Matthias Weisser wrote:
>>>> Anatolij Gustschin <agust@denx.de> schrieb am 01.07.2009 um 15:40:
>> Dear Matthias,
>>
>> Thanks for this patch! Please see some comments/issues below which
> we
>> should resolve before committing the driver.
> 
> First of all thanks for your detailed comments. I fix them all before 
> resending the patch. Please see some additional comments at some
> points.
> 
>>> +		if(0 == bpp){
>> if (bpp == 0) {
> 
> The spaces are OK but why turn around the comparison? I always use 
> this style to prevent from unwanted assignments. Well, GCC warns 
> about assignments in ifs and as u-boot is GCC only I can do that.

it is a matter of personal preference. "if (0 == bpp) {" is OK for
me, too.

>> We also should use macros for register offsets, I think. Can we
>> coordinate efforts for fixing this in mb862xx driver also?
> 
> As the graphic controller in the jade soc is only a slight evolution
> of
> the coral graphic chip (additional display output/video input) I think
> 
> we may even merge the two drivers into one with some #ifdefs to deal
> with the differences.
> 
> When I started to implement the driver I decided against that idea
> because I don't have any hardware here to test the "non-jade" case.

if you want to use the existing driver, it shouldn't be too complicated.
To use the mb862xx driver you can implement "board_video_init()" in your
board code in which you initialize both display controllers, set
"GraphicDevice mb862xx" structure fields winSizeX, etc. and return
the video RAM base. Then additionally implement "board_get_regs()" in
your board code, e.g.

#include <mb862xx.h>

static const gdc_regs init_regs [] =
{
	{0, 0}
}

const gdc_regs *board_get_regs (void)
{
        return init_regs;
}

and define CONFIG_VIDEO_MB862xx in the board config file.

see e.g. the appropriate code in "board/lwmon5/lwmon5.c".
It does the display controller initialization differently and
therefore my suggestion to do the display controller init in
custom "board_video_init()".

We have to fix some register access macros in the mb862xx driver
for JADE and it should work. I can try to provide a patch for
this fix in mb862xx.c.

> But a common include file with the register offsets seems to be a
> good idea to me.

I'will prepare a list of register offset defines for "include/mb862xx.h"
and send a patch so that you can use them in your code.

Thanks,
Anatolij

  reply	other threads:[~2009-07-02  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 13:21 [U-Boot] [PATCH] This patch adds support for Fujitsu MB86R01 'JADE' SOC Matthias Weisser
2009-06-30 13:21 ` [U-Boot] [PATCH] Add suport for the graphic controller included in the JADE SOC Matthias Weisser
2009-06-30 13:21   ` [U-Boot] [PATCH] Added support for splash screen positioning adding by adding Matthias Weisser
2009-06-30 13:21     ` [U-Boot] [PATCH] Added support for jadecpu board using the MB86R01 'Jade' SOC from Fujitsu Matthias Weisser
2009-07-01  9:18     ` [U-Boot] [PATCH] Added support for splash screen positioning adding by adding Anatolij Gustschin
2009-07-01 13:40   ` [U-Boot] [PATCH] Add suport for the graphic controller included in the JADE SOC Anatolij Gustschin
2009-07-02  6:02     ` [U-Boot] Antw: " Matthias Weisser
2009-07-02  9:27       ` Anatolij Gustschin [this message]
2009-07-04 23:30         ` [U-Boot] " Wolfgang Denk
2009-07-07 12:29         ` Anatolij Gustschin
2009-07-19 20:12 ` [U-Boot] [PATCH] This patch adds support for Fujitsu MB86R01 'JADE' SOC 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=4A4C7D73.1080502@denx.de \
    --to=agust@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.