* booting arm board
@ 2015-01-12 3:38 John de la Garza
2015-01-12 3:44 ` nick
2015-01-12 12:32 ` Greg KH
0 siblings, 2 replies; 4+ messages in thread
From: John de la Garza @ 2015-01-12 3:38 UTC (permalink / raw)
To: kernelnewbies
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* booting arm board
2015-01-12 3:38 booting arm board John de la Garza
@ 2015-01-12 3:44 ` nick
2015-01-12 6:05 ` sanjeev sharma
2015-01-12 12:32 ` Greg KH
1 sibling, 1 reply; 4+ messages in thread
From: nick @ 2015-01-12 3:44 UTC (permalink / raw)
To: kernelnewbies
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 at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* booting arm board
2015-01-12 3:44 ` nick
@ 2015-01-12 6:05 ` sanjeev sharma
0 siblings, 0 replies; 4+ messages in thread
From: sanjeev sharma @ 2015-01-12 6:05 UTC (permalink / raw)
To: kernelnewbies
Hello John & Nick,
IMO,you should take stable release version of kernel and then give a try
because stable kernel has very less chance.
Regards
Sanjev Sharma
On Mon, Jan 12, 2015 at 9:14 AM, nick <xerofoify@gmail.com> wrote:
> 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 at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150112/82e5b273/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* booting arm board
2015-01-12 3:38 booting arm board John de la Garza
2015-01-12 3:44 ` nick
@ 2015-01-12 12:32 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2015-01-12 12:32 UTC (permalink / raw)
To: kernelnewbies
On Sun, Jan 11, 2015 at 10:38:08PM -0500, 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
Why not ask the developers of that patch, and the linux-arm mailing list
about this? That would be the best way to work through the issues.
good luck,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-01-12 12:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-12 3:38 booting arm board John de la Garza
2015-01-12 3:44 ` nick
2015-01-12 6:05 ` sanjeev sharma
2015-01-12 12:32 ` Greg KH
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).