From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] p1022ds: add video support
Date: Tue, 21 Sep 2010 18:01:19 -0500 [thread overview]
Message-ID: <4C99393F.8010301@freescale.com> (raw)
In-Reply-To: <20100922005700.499ce44d@wker>
Anatolij Gustschin wrote:
>> Also, I thought it would be better to provide some sort of completeness for the
>> > bits I am using.
> We do not add unused code.
Well, I don't see how macros are "unused code", but I'll delete those lines.
>>> > > CONFIG_VIDEO definition should depend on CONFIG_FSL_DIU_FB,
>>> > > I think. Otherwise the building won't succeed if CONFIG_FSL_DIU_FB
>>> > > is not defined (due to absence of video_hw_init()).
>> >
>> > We need the DIU initialized, even if U-Boot doesn't use it. This is what
>> > CONFIG_FSL_DIU_FB does. CONFIG_VIDEO then tells U-Boot to actually use the DIU.
> I understand it. I didn't say you should make CONFIG_FSL_DIU_FB
> dependent on CONFIG_VIDEO, but the opposite.
Ok.
> On the other site, one of the design principles states:
>
> initialize devices only when they are needed within U-Boot.
Well, I'll try to work toward that, but I'm pretty sure there are plenty of
devices that are initialized but not used in U-Boot already.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-09-21 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 20:35 [U-Boot] [PATCH] p1022ds: add video support Timur Tabi
2010-09-21 21:56 ` Anatolij Gustschin
2010-09-21 22:00 ` Timur Tabi
2010-09-21 22:57 ` Anatolij Gustschin
2010-09-21 23:01 ` Timur Tabi [this message]
2010-09-22 15:07 ` Detlev Zundel
2010-09-22 15:10 ` Timur Tabi
2010-09-22 15:16 ` York Sun
2010-09-22 15:33 ` Detlev Zundel
2010-09-22 15:35 ` Timur Tabi
2010-09-22 15:45 ` Detlev Zundel
2010-09-22 15:30 ` Detlev Zundel
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=4C99393F.8010301@freescale.com \
--to=timur@freescale.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