On Wed, Mar 30, 2016 at 6:01 AM, Edward Wingate <[email protected]> wrote: > Thank you, I added this to my configuration: > KBRANCH_pn-linux-xlnx-dev = "master" > > and it appears to be working (still building, but continues further now). > > I don't know about removing branch specifier completely.
For reference, the linux-xlnx.inc will auto select (was added in the jethro release, so this wont work with fido) whether to checkout as nobranch or with branch. See: http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/tree/recipes-kernel/linux/linux-xlnx.inc?h=jethro#n8 . If you are after a specific commit (or tag), set SRCREV = "<id>", and set KBRANCH/SRCBRANCH = "". This will ensure that it checks out the commit regardless of whether the branch/ref has that commit or not. Regards, Nathan > > I've been on fido branch for a year now. Tried jethro recently with > my custom layer and got a bunch of errors, so went back to fido for > now. But I suppose that's the usual drill with an upgrade? Just have > to bite the bullet and fix the errors one by one until it works again? > > > On Tue, Mar 29, 2016 at 11:17 AM, Sören Brinkmann wrote: >> On Tue, 2016-03-29 at 11:06:24 -0700, Edward Wingate wrote: >>> I've been using linux-xlnx-dev.bb recipe to compile a kernel with the >>> following: >>> PREFERRED_PROVIDER_virtual/kernel = "linux-xlnx-dev" >>> SRCREV_pn-linux-xlnx-dev = "3be00480727bf360d912223026b789011b1e5251" >>> >>> This was pointing to a 4.0 kernel. Now, on a fresh build, I get >>> "unable to find revision" errors: >>> >>> WARNING: Failed to fetch URL >>> git://github.com/Xilinx/linux-xlnx.git;protocol=https;branch=master-next, >>> attempting MIRRORS if available >>> ERROR: Fetcher failure: Unable to find revision >>> 3be00480727bf360d912223026b789011b1e5251 in branch master-next even >>> from upstream >>> ERROR: Function failed: Fetcher failure for URL: >>> 'git://github.com/Xilinx/linux-xlnx.git;protocol=https;branch=master-next'. >>> Unable to fetch URL from any source. >>> >>> Can I still get to this kernel revision somehow? Or was this revision >>> struck from the source tree? >> >> The commit does exist: >> https://github.com/Xilinx/linux-xlnx/commit/3be00480727bf360d912223026b789011b1e5251 >> >> I suspect the problem is the 'branch' specifier. The master-next branch >> has been deprecated for quite a while, as it was a mere copy of 'master' >> anyways. Earlier this year, IIRC, the branch has been removed. I'd >> suspect changing the branch to 'master' would fix it. Or even better, if >> OE allows that, remove the branch specifier completely, as the commit >> hash is fully identifying a commit independent of any branches. >> >> Sören > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
