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?
--
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.
On Mar 6, 2016 1:23 AM, "gnu gnu" <nagla...@gmail.com> wrote:
>
> 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
You can't, one of the git reps we pull is constantly changing with no tags..
Just do what I said, as I pushed a special patch for you to enable.
Regards,