I have access to an E350M1. I will test these patches tonight and report back with results.
Thank you! -Marshall Buschman
On 09/07/2011 02:53 AM, She, Kerry wrote:
-----Original Message----- From: email@example.com [mailto:coreboot- firstname.lastname@example.org] On Behalf Of email@example.com Sent: Friday, August 19, 2011 12:37 AM To: coreboot Subject: [coreboot] E350M1 does not POST
Upon booting, I get this:
you could try commit 0df0e14fb, that may or may not work, the
that broke fusion boards completely, apparently.
Thank you! I can confirm that 0df0e14fb works properly. -Marshall
It looks like we have a regression. Is there some dependency on the other patches that have not yet been committed?
Unfortunately git bisect is no help here because the commit which
the regression was a huge one.
It's important that large patches are broken down into a set of small comprehensible patches, each with an explanatory commit message.
<<quote from git-bisect-lk2009.html documentation>> ... sometimes "interesting" changes of behavior in the software are introduced in some commits.
In fact people are specially interested in commits that introduce a "bad" behavior, called a bug or a regression. They are interested in these commits because a commit (hopefully) contains a very small set of source code changes. And it's much easier to understand and properly fix a problem when you only need to check a very small set of changes, than when you don't know where look in the first place.
So to help people find commits that introduce a "bad" behavior, the "git bisect" set of commands was invented.
Since commit 84cbce2 cause E350M1 not POST, Following patches should resolve this regression problem, please see the attachment in detail. I have test it on a Persimmon mainboard, anybody can have a test on E350M1? Thanks -- Kerry sheh