On Fri, Aug 28, 2015 at 9:51 AM, TheCajun <[email protected]> wrote: > On 2015-08-26 12:10, Robert Nelson wrote: >>> >>> Thank you. >>> >>> I used this command to get the repository. >>> >>> git clone https://github.com/Angstrom-distribution/meta-ti.git >>> >>> I see >>> >>> meta-ti/tree/master/recipes-kernel/linux/linux-3.0 >>> meta-ti/tree/master/recipes-kernel/linux/linux-3.0.bb >>> >>> I do not see >>> >>> meta-ti/blob/master/recipes-kernel/linux/linux_3.0.bb >> >> >> Well, yeah "blob" is just part of the github "web" interface... >> >>> >>> 1) Is linux-3.0.bb a script used with 'patch'? >>> 2) Do I cd to top level of kernel tree and run patch with this script? >>> 3) How is this script executed? >> >> >> It's a *.bb script... so either use "bitbake", or write a script to >> manually "patch -p1 < <file>" in the order shown in the *.bb file. >> >> I'd personally write a script.. Using "bitbake" requires more other >> un-related work.. >> >> Regards, > > > Ok, patches went in successfully, and uImage was built successfully. > I am still stuck at booting the kernel. I need an idea to debug this. > Any ideas?
Well, assuming you followed the *.bb exactly for the patches and kernel defconfig... It's probably a gcc bug.. Make sure you use a version of gcc from that same era. As that "repo" worked in that era. Good Luck! Regards, -- Robert Nelson https://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 [email protected]. For more options, visit https://groups.google.com/d/optout.
