I tried everything in my knowledge and googling through, to move back to tag 4.1.13-ti-r33 but I get errors. So is there no way to move back to a tag... even when I clone a new repo ?? Pls help. Your last instructions were not clear to me, so want to move back to working version i.e4.1.13-ti-r33 . 1. Tried to create a new repo git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git cd ti-linux-kernel-dev/ git checkout tags/4.1.13-ti-r33 ./build_kernel.sh
2.tried to switch to a new tag on exisiting repo git reset --hard 4.1.13-ti-r33 ./build_kernel.sh Error: Applying: Fix remoteproc to work with the PRU GNU Binutils port error: drivers/remoteproc/pruss_remoteproc.c: does not exist in index Patch failed at 0001 Fix remoteproc to work with the PRU GNU Binutils port When you have resolved this problem run "git am --resolved". If you would prefer to skip this patch, instead run "git am --skip". To restore the original branch and stop patching run "git am --abort". Regards Nagla On Saturday, March 5, 2016 at 1:06:30 AM UTC+5:30, William Hermans wrote: > > *One other thing which I am unable to get is that since with the with new >> build I stop uboot into loading and running the linux kernel(basically i am >> at uboot command prompt), so why do I see this issue while in earlier >> version its not present? Pinmux settings will come into picture only when >> debugging Linux kernel if I am right.Why should it affect Uboot debug, >> where uboot repo and build does not change at all?* >> > > THis is not necessarily true. uboot at minimum can do *some* pinmux > control. As it has the to use I2C, which in the case of the beagebone > boards is sometimes used to determine which board file to load. Through > reading the onboard eeprom, which sits on an I2C bus . . . At least that's > my understanding. > > On Fri, Mar 4, 2016 at 7:45 AM, Robert Nelson <[email protected] > <javascript:>> wrote: > >> On Fri, Mar 4, 2016 at 8:10 AM, gnu gnu <[email protected] <javascript:>> >> wrote: >> > Thanks Robert... But as I mentioned earlier I am not at all good at >> git, so >> > could you please let me know what commands I need to run ? Right now my >> > kernel makefile points to 4.1.18 >> >> So delete the repo and re-clone, then follow the guide posted in the >> previous message.. >> >> > >> > One other thing which I am unable to get is that since with the with new >> > build I stop uboot into loading and running the linux kernel(basically >> i am >> > at uboot command prompt), so why do I see this issue while in earlier >> > version its not present? Pinmux settings will come into picture only >> when >> > debugging Linux kernel if I am right.Why should it affect Uboot debug, >> where >> > uboot repo and build does not change at all? >> >> Sorry, i never bother with jtag debugging. I just gave you an easy way >> to revert the functionality i had changed by default.. >> >> 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] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
