From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx53loco build fails with CONFIG_VIDEO disabled
Date: Wed, 13 Jun 2012 23:23:56 +0530 [thread overview]
Message-ID: <4FD8D3B4.70109@gmail.com> (raw)
In-Reply-To: <4FD8CBF1.8060706@denx.de>
On 6/13/2012 10:50 PM, Stefano Babic wrote:
> On 13/06/2012 19:00, Vikram Narayanan wrote:
>> Hello,
>>
>> mx53loco build fails when CONFIG_VIDEO and its friends disabled.
>> I can send a patch fixing this.
>>
>
> But CONFIG_VIDEO is *not* set in mx53loco.h mainline. Do you mean you
> are testing Fabio's patches ?
With this (fedab338f3459315cb69627fcf46032ec8df1753) it is already in
the master.
> Fabio, can you give me an overview about your IPU patches ? I have seen
> several patches during my vacation, but it is not clear to me the
> status. In patchwork, most of them (but not all) are assigned to
> Anatolji. Can you help me to sync myself with the current status ?
>
>> I _really_ don't like ifdef -ing a lot of stuff.
>
> Nobody likes it ;-)
>
>> Instead I'd feel to
>> have a separate file in the directory which does this LCD init and FB
>> init call, and let the makefile handle the conditional compilation.
>
> A way we use in the past to have different compilation of the same board
> with different features is to use a separate entry into boards.cfg, for
> example see imx31_phycore, or also magnesium and imx27lite, or...
>
> Anyway, when patches for IPU flow into mainline, is there a good reason
> to not enable CONFIG_VIDEO for mx53loco ?
Though this would be helpful for headless boards, I'm not the right guy.
Fabio can give a better picture here.
Regards,
Vikram
> Best regards,
> Stefano
>
next prev parent reply other threads:[~2012-06-13 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 17:00 [U-Boot] mx53loco build fails with CONFIG_VIDEO disabled Vikram Narayanan
2012-06-13 17:12 ` Fabio Estevam
2012-06-13 17:20 ` Stefano Babic
2012-06-13 17:53 ` Vikram Narayanan [this message]
2012-06-13 17:59 ` Fabio Estevam
2012-06-13 17:56 ` Fabio Estevam
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=4FD8D3B4.70109@gmail.com \
--to=vikram186@gmail.com \
--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