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. 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. On November 10, 2015 6:20:59 AM CST, Jim Perrin <jperrin at centos.org> wrote: >So, I'll blame it (publicly at least) on not having coffee yet this >morning. Where did you turn up this bit of code, and what does this get >added to? > >On 11/10/2015 05:46 AM, cc35359 at gmail.com wrote: >> 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. >> >> >> #include <fcntl.h> >> >> #include <linux/fb.h> >> >> #include <sys/ioctl.h> >> >> #include <sys/mman.h> >> >> #include <unistd.h> >> >> #include <assert.h> >> >> int main(int argc, char **argv) { >> >> struct fb_fix_screeninfo fixed; >> >> struct fb_var_screeninfo variable; >> >> char *fb; >> >> int line_size, size, buffer_size, i; >> >> int fd = open("/dev/fb0", O_RDWR); >> >> ioctl(fd, FBIOGET_VSCREENINFO, &variable); >> >> variable.xres = 1280; >> >> variable.yres = 720; >> >> variable.xres_virtual = 1280; >> >> variable.yres_virtual = 1440; >> >> variable.bits_per_pixel = 24; >> >> ioctl(fd, FBIOPUT_VSCREENINFO, &variable); >> >> ioctl(fd, FBIOGET_FSCREENINFO, &fixed); >> >> variable.xoffset = 0; >> >> variable.yoffset = 720; >> >> ioctl(fd, FBIOPAN_DISPLAY, &variable); >> >> variable.xoffset = 0; >> >> variable.yoffset = 0; >> >> ioctl(fd, FBIOPAN_DISPLAY, &variable); >> >> close(fd); >> >> return 0; >> >> } >> >> On November 9, 2015 4:22:42 PM CST, Jim Perrin <jperrin at centos.org> >wrote: >>> I've posted a first build of CentOS for the Hikey from 96boards, and >a >>> ReadMe with the steps required to get the board going. >>> >>> http://people.centos.org/jperrin/hikey/ >>> >>> The ReadMe assumes that you've at least skimmed the 'Getting >Started' >>> section of the Hikey documentation, but walks through the fastboot >>> commands to load the image. >>> >>> What I consider the 'blocker' to releasing this image presently is >the >>> lack of console output on HDMI. If someone's able to make that go, I >>> will happily mail them some CentOS swag and put their name in the >>> release notes for the image. >>> >>> >>> >>> >>> -- >>> Jim Perrin >>> The CentOS Project | http://www.centos.org >>> twitter: @BitIntegrity | GPG Key: FA09AD77 >>> _______________________________________________ >>> Arm-dev mailing list >>> Arm-dev at centos.org >>> https://lists.centos.org/mailman/listinfo/arm-dev >> >> >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev at centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev >> > >-- >Jim Perrin >The CentOS Project | http://www.centos.org >twitter: @BitIntegrity | GPG Key: FA09AD77 >_______________________________________________ >Arm-dev mailing list >Arm-dev at centos.org >https://lists.centos.org/mailman/listinfo/arm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20151110/ff428ab4/attachment-0006.html>