From: Julian Margetson <runaway@candw.ms>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Ian Munsie <imunsie@au1.ibm.com>
Subject: Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board
Date: Mon, 23 Feb 2015 22:22:32 -0400 (AST) [thread overview]
Message-ID: <45df690866b.32811198@smtp.gmail.com> (raw)
In-Reply-To: <1424737962.2318.2.camel@ellerman.id.au>
I had a hanging Uboot problem with a Sam440ep board.Never figured the problem out but
It workedd for another two years after the problems began. Died for good last September with the hanging becoming a daily issue.
Dont think that it was overheating. I thought that it could have been a problem with the on board ethernet.
anyway I am still not giving up hopes of DRI and future kernals working, only into my second year of trying so too soon to give up .
Doing a git bisect on the 4.00-rc1 now.
On 02/24/2015, you wrote:
> On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:
>> On 2/18/2015 11:25 PM, Julian Margetson wrote:
>
>> re PPC4XX PCI(E) MSI support.
>> https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html
>
> Hmm, I think all those comments were addressed before it was merged.
>
> I tried to get a 4xx board going here last week, but it doesn't seem happy. I
> can get a bit of uboot but then it hangs, might be overheating.
>
> cheers
>
>
next prev parent reply other threads:[~2015-02-24 10:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 12:16 Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-16 0:18 ` Michael Ellerman
2015-02-18 19:45 ` Julian Margetson
2015-02-19 0:13 ` Michael Ellerman
2015-02-19 1:36 ` Julian Margetson
2015-02-19 2:56 ` Michael Ellerman
2015-02-19 3:25 ` Julian Margetson
2015-02-20 19:25 ` Julian Margetson
2015-02-24 0:32 ` Michael Ellerman
2015-02-24 2:22 ` Julian Margetson [this message]
2015-02-24 11:08 ` Julian Margetson
2015-02-24 19:14 ` Gerhard Pircher
2015-02-24 20:26 ` Julian Margetson
2015-02-25 13:26 ` Julian Margetson
2015-02-25 13:32 ` Julian Margetson
2015-03-04 11:46 ` Julian Margetson
2015-03-04 23:52 ` Michael Ellerman
2015-03-05 11:15 ` Julian Margetson
2015-03-07 16:10 ` Julian Margetson
2015-03-10 0:30 ` Michael Ellerman
2015-03-10 0:53 ` Julian Margetson
[not found] ` <45dfe4c8990.73f22654@smtp.gmail.com>
2015-02-24 19:05 ` Julian Margetson
2015-02-19 15:57 ` Julian Margetson
[not found] ` <54EB253F.9020704@candw.ms>
2015-02-23 15:07 ` Problems with DRI " Julian Margetson
2015-02-23 17:43 ` Julian Margetson
2015-02-24 11:12 ` Julian Margetson
2015-02-24 18:57 ` Julian Margetson
2015-02-24 20:28 ` Julian Margetson
2015-02-25 13:25 ` Julian Margetson
2015-02-25 13:31 ` Julian Margetson
2015-03-07 16:05 ` Julian Margetson
2016-02-02 13:54 ` commit 9178ba294b6839eeff1a91bed95515d783f3ee6c Julian Margetson
2016-08-05 11:26 ` Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-19 2:20 ` Julian Margetson
2015-02-18 20:13 ` Julian Margetson
2015-04-27 10:59 ` Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands Julian Margetson
2015-04-28 1:12 ` Michael Ellerman
2015-04-28 3:49 ` Tejun Heo
2015-05-04 17:18 ` Andy Shevchenko
2015-05-04 18:13 ` Tejun Heo
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=45df690866b.32811198@smtp.gmail.com \
--to=runaway@candw.ms \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.