From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wolfgang Denk <wd@denx.de>
Date: Thu, 18 Mar 2010 00:00:03 +0100
Subject: [U-Boot] [PATCH] add new board pm9g45
In-Reply-To: <4BA1363B.7010002@ronetix.at>
References: <1268744233-2497-1-git-send-email-dimov@ronetix.at>
	<20100316190012.84CA75086C@gemini.denx.de>
	<4BA1363B.7010002@ronetix.at>
Message-ID: <20100317230003.487FD5086C@gemini.denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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