From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] p1022ds: add video support
Date: Wed, 22 Sep 2010 17:33:35 +0200 [thread overview]
Message-ID: <m2fwx1u71s.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1285168585.4843.16.camel@oslab-l1> (York Sun's message of "Wed, 22 Sep 2010 08:16:25 -0700")
Hi,
> On Wed, 2010-09-22 at 10:10 -0500, Timur Tabi wrote:
>> > Is there a technical reason why the initialization has to be in U-Boot?
>>
>> I'll have to re-examine the code. There may be a way to eliminate any such
>> initialization.
>>
> There is a technical reason. The DIU driver needs initialize DVI encoder
> which is on I2C bus. Linux kernel starts to use console device long
> before I2C is available. So it has to be done in U-boot.
Ok, then why not always define CONFIG_VIDEO for this configuration and
let U-Boot initialize _and_ use it? Actually I fail to see why U-Boot
shouldn't use it if the support is there or what am I missing?
Best wishes
Detlev
--
"Our enemies are innovative and resourceful, and so are we. They
never stop thinking about new ways to harm our country and our people,
and neither do we."
-- George W. Bush during a defense bill ceremony on 5. Aug 2004
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-09-22 15:33 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
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 [this message]
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=m2fwx1u71s.fsf@ohwell.denx.de \
--to=dzu@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