From: john@jjdev.com (John de la Garza)
To: kernelnewbies@lists.kernelnewbies.org
Subject: booting arm board
Date: Sun, 11 Jan 2015 22:38:08 -0500 [thread overview]
Message-ID: <20150112033805.GA12195@vega.jjdev.com> (raw)
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?
next reply other threads:[~2015-01-12 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 3:38 John de la Garza [this message]
2015-01-12 3:44 ` booting arm board nick
2015-01-12 6:05 ` sanjeev sharma
2015-01-12 12:32 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150112033805.GA12195@vega.jjdev.com \
--to=john@jjdev.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).