public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add new board pm9g45
Date: Thu, 18 Mar 2010 00:00:03 +0100	[thread overview]
Message-ID: <20100317230003.487FD5086C@gemini.denx.de> (raw)
In-Reply-To: <4BA1363B.7010002@ronetix.at>

Dear RONETIX - Asen Dimov,

In message <4BA1363B.7010002@ronetix.at> you wrote:
>
> > This information should not be board-specific. The panel information
> > is generic and should moved to a separate header file that is not part
> > of the board code.
> >
> >   
> In the boards (at91sam9263ek and at91sam9m10g45ek, and some more 
> at91sam9 based boards) I am looking at, the panel_info is in the board 
> specific code.

Indeed. Patches to clean this up are welcome.

> There are some lcd.c files with panel_info structures: 
> drivers/video/mx3fb.c, cpu/pxa/pxafb.c and  cpu/mpc8xx/lcd.c .
> 
> Where should be the proper place for panel_info which is somehow 
> architecture dependent?

I'm not an expert in this area. In Linux there has been discussion to
put this type of information into the device tree. Either in the form
of (new, to be defined) specific bindings, or as EDID data.

I wonder if we could / should do something similar here?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Man is the best computer we can put aboard a spacecraft ...  and  the
only one that can be mass produced with unskilled labor.
                                                 -- Wernher von Braun

  reply	other threads:[~2010-03-17 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 12:57 [U-Boot] [PATCH] add new board pm9g45 Asen Dimov
2010-03-16 19:00 ` Wolfgang Denk
2010-03-17 20:06   ` RONETIX - Asen Dimov
2010-03-17 23:00     ` Wolfgang Denk [this message]
2010-03-18  6:41 ` Maxim Podbereznyi
2010-03-21 18:57   ` Wolfgang Denk
2010-03-20 19:10 ` Tom
2010-03-21 19:56   ` Wolfgang Denk
2010-03-30 11:55   ` RONETIX - Asen Dimov
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 12:02 Asen Dimov

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=20100317230003.487FD5086C@gemini.denx.de \
    --to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox