From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] corenet: Disable video on P2020DS
Date: Fri, 25 Jan 2013 15:48:50 -0500 [thread overview]
Message-ID: <5102EFB2.6000305@ti.com> (raw)
In-Reply-To: <CC6546B78A5F204290BB35835D3E8581314A72@039-SN2MPN1-011.039d.mgd.msft.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/25/2013 03:43 PM, Fleming Andy-AFLEMING wrote:
>
> On Jan 25, 2013, at 12:50 PM, Tom Rini wrote:
>
>> On Fri, Jan 25, 2013 at 10:38:01AM -0600, Andy Fleming wrote:
>>
>>> The P2020DS build had grown too large, and video support isn't
>>> enabled in almost any other Freescale board. Disabling it
>>> allows us to keep building, and provides options for reenabling
>>> it later.
>>>
>>> Signed-off-by: Andy Fleming <afleming@freescale.com>
>>
>> Now we may start having dead code around, yes? Can you perhaps
>> get away with making this be disable video or something else and
>> add a P2020DS_video boards.cfg entry or similar? Thanks!
>
> There doesn't appear to be any 2020-specific code in
> drivers/video/. The truth is, I doubt the code gets more than
> compile-tested by the setting being there. Also, as noted, P1022
> defines it, in addition to MPC8536, MPC8544, MPC8572, MPC8610, and
> MPC8641. I'd rather not hack up a "video" config just for P2020,
> if possible.
That's all I was looking for, that yes, we don't now have very dead
code there. Thanks! (and I kicked off my loop of testing on the PR
that includes this change a while ago, still spinning over everything).
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRAu+yAAoJENk4IS6UOR1WxmMP/3n2qAoSndB5DpCjiaMj0zTz
33ShG55Zv14aU40WCD1I4yMkY/hi/mEr3sOIo/D7pZ+FzciYhliBNPejCUuTfmtD
T4YkE1rvtmF+TMKxLdqeUXiQPJyI81tzwGfA2y+NZXnpTMEqpo+ke6DM2xXHxjHP
Vxjp+IGBT0gKG/gjp6c/WdR1kdbqGQRQBnM3l9Ifdt64c7GksMCEg2MyVIBkPQpY
K/WvB03wQz/CohAPy/ySIrzdxKoXjrurUBNZOiKQ4rwBs7O7i6xhr02ZE8Mjco2n
13SY+jRYSlH24F5BbKS2TKtD5b3DGXa9SLihg+nl6gdzyZ/kZJo2zdGm5K+scFS5
1jLWUOOI06xxLUoGCmaCPzOvbxMTSQKSHpLhFSR/EryOq2NlY4D+wHtAPQmbI8GU
eP5lnV/a44kCG5CMgoBKOy8vRxIRjUZaTDFix5fC+rxbgZUTh1MGO4Mp4ieuxHz5
B/48CbN1Ka9fpMQOlo1u01ZbCAya5aUeL6TduvGr4SXaw878hS8S9+89nRMoSma1
Rc9tH2B5F4LKsky8C4lcGsE2YsPd7z2kkRApyMzoKd+O2ZCcDXdnZ9RQO3+is0y7
pWqzfWZhfg4UDWn8jD3Sv3uLxwM890FsmhiAoDhTjdhB4K7sL5AU8dcD2u6G35cg
uq6A/XJ6nVxAW+a4p1Uv
=C7Yu
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-01-25 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 16:38 [U-Boot] [PATCH] corenet: Disable video on P2020DS Andy Fleming
2013-01-25 18:50 ` Tom Rini
2013-01-25 19:25 ` Scott Wood
2013-01-25 19:35 ` Scott Wood
2013-01-25 19:35 ` Tom Rini
2013-01-25 20:43 ` Fleming Andy-AFLEMING
2013-01-25 20:48 ` Tom Rini [this message]
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=5102EFB2.6000305@ti.com \
--to=trini@ti.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