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 meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
