public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] video: ct6900: Add an option to skip video initialization
Date: Thu, 14 May 2009 15:53:20 +0200	[thread overview]
Message-ID: <200905141553.20682.sr@denx.de> (raw)
In-Reply-To: <20090514133715.0DDEB832E416@gemini.denx.de>

Hi Wolfgang,

On Thursday 14 May 2009 15:37:15 Wolfgang Denk wrote:
> > This patch adds an option to skip the video initialization on the
> > ct6900. This is needed for the CPCI750 which can be built as CPCI
> > host and adapter/target board. And the adapter board can't access the
> > video cards.
>
> Hm... why do you change the code of the viseo driver then? This change
> should be local to the CPCI750 board only.

I would love to do it this way. It's not possible though. At least I don't see 
such a solution.

> > +/*
> > + * Implement a weak default function for boards that optionally
> > + * need to skip the video initialization.
> > + */
> > +int __board_video_skip(void)
> > +{
> > +	return 0;
> > +}
> > +int board_video_skip(void) __attribute__((weak,
> > alias("__board_video_skip"))); +
> > 
> > /************************************************************************
> >******* *
> >  * Init video chip
> > @@ -982,8 +992,12 @@ video_hw_init (void)
> >  	struct ctfb_res_modes *res_mode;
> >  	struct ctfb_res_modes var_mode;
> >  	struct ctfb_chips_properties *chips_param;
> > -	/* Search for video chip */
> >
> > +	/* Check if video initialization should be skipped */
> > +	if (board_video_skip())
> > +		return NULL;
>
> This makes no sense  to  me.  Instead  of  adding  a  (basicly  board
> specific,  even if you hide it with the weak implementation) shortcut
> to video_hw_init() you should not initialize the video driver on this
> board at all, leaving the video driver code unchanged.

Then please let me know how this can be accomplished. The CPCI750 uses the 
same U-Boot image both for the video-enabled CPCI-host version and for the 
video-disabled CPCI-adapter version. The video driver is not called from 
within the CPCI750 board files. It's called from drivers/video/cfb_console.c. 

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2009-05-14 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14  5:25 [U-Boot] [PATCH] video: ct6900: Add an option to skip video initialization Stefan Roese
2009-05-14 13:37 ` Wolfgang Denk
2009-05-14 13:53   ` Stefan Roese [this message]
2009-05-14 14:02     ` Wolfgang Denk
2009-05-14 14:13       ` Stefan Roese
2009-05-14 15:01         ` Wolfgang Denk
2009-05-14 15:17           ` Stefan Roese
2009-05-15  0:44             ` Anatolij Gustschin
2009-05-15  5:36               ` Wolfgang Denk
2009-05-15  6:24                 ` Stefan Roese
2009-05-15  0:36           ` Anatolij Gustschin

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=200905141553.20682.sr@denx.de \
    --to=sr@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