John, I would recommend building the latest kernel,if it doesn't boot please git bisect and send in a bug report with the commit to revert, if there is a obvious commit that causes issues. If you don't known the maintainer/lists to send the message to run ./scripts/get_maintainer -f on the file in question from the root directory of your cloned git tree and is should tell you who to mail the message to and cc the message to. Cheers, Nick On 2015-01-11 10:38 PM, John de la Garza wrote: > I am trying to boot a foxg20 board. It uses an at91sam9g20 chip an > used to work in linux 3.5. I am looking for some advice on how to get > mainline linux to boot on it. > > I first tried bisecting and found this commit: > 4cf3326ab5f34a333a46c59d0d3783db9cef13bf > > which is where it wouldn't boot > > I figured I should understand what broke, I ended up simply upping > MMC_CMD_RETRIES from 3 to 10. So I was able to boot the version that > caused it to not work. This change doesn't fix the lastest has unified > some of the driver code. > > My question is: > > What is a good way to boot the latest kernel? Should I see where it > breaks then keeping fixing that and moving forward or should I just > start with the latest and take it from there? > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
