Which is where the "porting" would come in handy. . . . On Sat, Dec 20, 2014 at 7:21 AM, Newton <thom0...@gmail.com> wrote:
> > > Le samedi 20 décembre 2014 01:38:56 UTC+1, RobertCNelson a écrit : >> >> On Fri, Dec 19, 2014 at 6:28 PM, Newton <thom...@gmail.com> wrote: >> > >> > >> > Le vendredi 19 décembre 2014 05:45:40 UTC+1, William Hermans a écrit : >> >> >> >> Well considering the rPI is armv5 versus armv7 on the beaglebone black >> . . >> >> . You probably have some "porting" to do. >> >> >> >> On Thu, Dec 18, 2014 at 6:34 PM, Newton <thom...@gmail.com> wrote: >> >>> >> >>> Any News ? >> >>> I tried to compile the kernel(3.8) by myself with fbtft without any >> >>> success :/ >> >>> >> >>> Le lundi 15 décembre 2014 02:32:40 UTC+1, Newton a écrit : >> >>>> >> >>>> I have not tested it yet (I'll probably do it soon, but must I learn >> >>>> about kernel compilation etc), so I can not real advise you. >> >>>> Anyway thank you for responding so quickly and sorry for syntax >> errors >> >>>> in my first post I did not read me: p >> >>>> >> >>>> >> >>>> Le lundi 15 décembre 2014 01:20:39 UTC+1, RobertCNelson a écrit : >> >>>>> >> >>>>> On Sun, Dec 14, 2014 at 6:15 PM, Newton <thom...@gmail.com> wrote: >> >>>>> > Hello, >> >>>>> > >> >>>>> > I think it's a good idea to include fbTFT drivers into the >> mainline >> >>>>> > Linux >> >>>>> > kernel(the Beaglebone fork of course). This will permit the use >> of >> >>>>> > low-cost >> >>>>> > screens more easily. Because Actually except for "official" capes >> it >> >>>>> > is >> >>>>> > really hard to develop with screens, and generally with objects >> "non >> >>>>> > officiales" >> >>>>> > >> >>>>> > https://github.com/notro/fbtft >> >>>>> >> >>>>> Very cool, do you have reference tft device i should pick up for >> >>>>> testing, before i merge these into our "3.8" and "3.14" bb.org >> >>>>> branches? >> >>>>> >> >>>>> Regards, >> >>>>> >> >>>>> -- >> >>>>> Robert Nelson >> >>>>> http://www.rcn-ee.com/ >> >>> >> >>> -- >> >>> For more options, visit http://beagleboard.org/discuss >> >>> --- >> >>> You received this message because you are subscribed to the Google >> Groups >> >>> "BeagleBoard" group. >> >>> To unsubscribe from this group and stop receiving emails from it, >> send an >> >>> email to beagleboard...@googlegroups.com. >> >>> For more options, visit https://groups.google.com/d/optout. >> > >> > >> > >> > Apparently, there are no problems with that, but they used features >> that >> > are'nt available in 3.8. And they added the device tree support after >> this >> > patch. So it will be difficult to make it work on 3.8. >> >> Have you looked at our "Frankenstein" 3.8, there's a lot of things in >> there that aren't available in kernel.org's 3.8.13. ;) >> >> Regards, >> >> -- >> Robert Nelson >> http://www.rcn-ee.com/ >> > > > Yes, but probably it is me who is bad in compilation :p > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
