<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 How do I realize a Bootloader Logo</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-do-I-realize-a-Bootloader-Logo/m-p/604828#M91132</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a device (i.MX6DL based) that needs to present to the user a configurable (based on GPIO input) boot screen and I have chosen to do this through U-Boot due to the boot time of Linux and Application code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is that when Linux starts booting, the screen is blanked and it is some seconds before application code is drawing to the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done some research into the Device Tree Settings for IPU (BYPASS_RESET) and FB (LATE_INIT), but am finding no matter the setting, in the file (mxc_ipuv3_fb.c) if the FB Start &amp;amp; Len (smem_start &amp;amp; smem_len) are not defined, a routine (mxcfb_map_video_memory) is called where at the end, the screen is cleared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see in mxcfb_probe where the LATE_INIT device tree setting is read, but I also see following a platform_get_resource which looks to be trying to see if start &amp;amp; end are defined.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where I am stumped is how to define this Start &amp;amp; End:&amp;nbsp; Both in the FB section and in the Memory section.&amp;nbsp;&amp;nbsp; I believe these need to either be passed from U-Boot or predefined in U-Boot &amp;amp; Linux Device Tree.&amp;nbsp; I did not see in any of the device tree Documentation anything suggesting how this should be done...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any example or documentation of how this should be done??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for your advice....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mike Sims&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jan 2017 13:44:56 GMT</pubDate>
    <dc:creator>mike_sims</dc:creator>
    <dc:date>2017-01-10T13:44:56Z</dc:date>
    <item>
      <title>How do I realize a Bootloader Logo</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-do-I-realize-a-Bootloader-Logo/m-p/604828#M91132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a device (i.MX6DL based) that needs to present to the user a configurable (based on GPIO input) boot screen and I have chosen to do this through U-Boot due to the boot time of Linux and Application code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is that when Linux starts booting, the screen is blanked and it is some seconds before application code is drawing to the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done some research into the Device Tree Settings for IPU (BYPASS_RESET) and FB (LATE_INIT), but am finding no matter the setting, in the file (mxc_ipuv3_fb.c) if the FB Start &amp;amp; Len (smem_start &amp;amp; smem_len) are not defined, a routine (mxcfb_map_video_memory) is called where at the end, the screen is cleared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see in mxcfb_probe where the LATE_INIT device tree setting is read, but I also see following a platform_get_resource which looks to be trying to see if start &amp;amp; end are defined.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where I am stumped is how to define this Start &amp;amp; End:&amp;nbsp; Both in the FB section and in the Memory section.&amp;nbsp;&amp;nbsp; I believe these need to either be passed from U-Boot or predefined in U-Boot &amp;amp; Linux Device Tree.&amp;nbsp; I did not see in any of the device tree Documentation anything suggesting how this should be done...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any example or documentation of how this should be done??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for your advice....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mike Sims&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2017 13:44:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-do-I-realize-a-Bootloader-Logo/m-p/604828#M91132</guid>
      <dc:creator>mike_sims</dc:creator>
      <dc:date>2017-01-10T13:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: How do I realize a Bootloader Logo</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-do-I-realize-a-Bootloader-Logo/m-p/604829#M91133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;Please check document regarding bootloader logo:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-98109"&gt;https://community.nxp.com/docs/DOC-98109&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 17:10:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-do-I-realize-a-Bootloader-Logo/m-p/604829#M91133</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2017-01-11T17:10:04Z</dc:date>
    </item>
  </channel>
</rss>

