<html><head></head><body>I found it from one of their people on their forums. I tried to track it down in their github, but hadn't found it yet.<br>
Since it has a main function, I assume just compile that bit of code and run it as a executable. They may have written it into a kernel patch versus standalone (after demo) for their hosted image (Debian?), I'll see if I can find out.<br>
<br>
<br>
<br><br><div class="gmail_quote">On November 10, 2015 6:20:59 AM CST, Jim Perrin <jperrin@centos.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">So, I'll blame it (publicly at least) on not having coffee yet this<br />morning. Where did you turn up this bit of code, and what does this get<br />added to?<br /><br />On 11/10/2015 05:46 AM, cc35359@gmail.com wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I believe this will do it for you. Code provided for their demo units. Its due in the end, to the fact that the board outputs one strict resolution. I can't find any sort of licensing on this tiny bit of code though, but the source is made public, freely available with no warranty is the closest I can find to a license.<br /> <br /> <br /> #include <fcntl.h><br /> <br /> #include <linux/fb.h><br /> <br /> #include <sys/ioctl.h><br /> <br /> #include <sys/mman.h><br /> <br /> #include <unistd.h><br /> <br /> #include <assert.h><br /> <br /> int main(int argc, char **argv) {<br /> <br />
struct fb_fix_screeninfo fixed;<br /> <br /> struct fb_var_screeninfo variable;<br /> <br /> char *fb;<br /> <br /> int line_size, size, buffer_size, i;<br /> <br /> int fd = open("/dev/fb0", O_RDWR);<br /> <br /> ioctl(fd, FBIOGET_VSCREENINFO, &variable);<br /> <br /> variable.xres = 1280;<br /> <br /> variable.yres = 720;<br /> <br /> variable.xres_virtual = 1280;<br /> <br /> variable.yres_virtual = 1440;<br /> <br /> variable.bits_per_pixel = 24;<br /> <br /> ioctl(fd, FBIOPUT_VSCREENINFO, &variable);<br /> <br /> ioctl(fd, FBIOGET_FSCREENINFO, &fixed);<br /> <br /> variable.xoffset = 0;<br /> <br /> variable.yoffset = 720;<br /> <br /> ioctl(fd, FBIOPAN_DISPLAY, &variable);<br /> <br /> variable.xoffset = 0;<br /> <br /> variable.yoffset = 0;<br /> <br /> ioctl(fd, FBIOPAN_DISPLAY, &variable);<br /> <br />
close(fd);<br /> <br /> return 0;<br /> <br /> }<br /> <br /> On November 9, 2015 4:22:42 PM CST, Jim Perrin <jperrin@centos.org> wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> I've posted a first build of CentOS for the Hikey from 96boards, and a<br /> ReadMe with the steps required to get the board going.<br /><br /> <a href="http://people.centos.org/jperrin/hikey">http://people.centos.org/jperrin/hikey</a>/<br /><br /> The ReadMe assumes that you've at least skimmed the 'Getting Started'<br /> section of the Hikey documentation, but walks through the fastboot<br /> commands to load the image.<br /><br /> What I consider the 'blocker' to releasing this image presently is the<br /> lack of console output on HDMI. If someone's able to make that go, I<br /> will happily mail them some CentOS swag and put their name in the<br /> release notes for the image.<br /><br /><br /><br /><br />
-- <br /> Jim Perrin<br /> The CentOS Project | <a href="http://www.centos.org">http://www.centos.org</a><br /> twitter: @BitIntegrity | GPG Key: FA09AD77<br /><hr /><br /> Arm-dev mailing list<br /> Arm-dev@centos.org<br /> <a href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a><br /></blockquote> <br /> <br /> <br /><hr /><br /> Arm-dev mailing list<br /> Arm-dev@centos.org<br /> <a href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a><br /> <br /></blockquote></pre></blockquote></div></body></html>