[coreboot] E350M1 does not POST

[Marshall Buschman]

On 09/07/2011 11:38 AM, Marshall Buschman wrote:
> 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:coreboot-bounces at coreboot.org  [mailto:coreboot-
>>> bounces at coreboot.org] On Behalf Ofperh52 at runbox.com
>>> Sent: Friday, August 19, 2011 12:37 AM
>>> To: coreboot
>>> Subject: [coreboot] E350M1 does not POST
>>>
>>>>>> Hi,
>>>>>>
>>>>>>> Upon booting, I get this:
>>>>>> [...]
>>>>>>
>>>>>> you could try commit 0df0e14fb, that may or may not work, the
>> commit
>>> after
>>>>>> that broke fusion boards completely, apparently.
>>>>>>
>>>>>> Florian
>>>>>>
>>>>> Thank you! I can confirm that 0df0e14fb works properly.
>>>>> -Marshall
>>>> Frank,
>>>>
>>>> It looks like we have a regression. Is there some dependency on the
>>>> other patches that have not yet been committed?
>>>>
>>>> Marc
>>> Unfortunately git bisect is no help here because the commit which
>> caused
>>> 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.
>> Hello, All
>>
>> 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
>>
>>
>>
>
>
>
Hello Kerry:

I have tested your patch set, and it does make the E350M1 boot.
The bad news is there is now a delay of approximately 5 minutes and 20 
seconds before any serial output is displayed.

The coreboot log is available at 
http://www.lucidmachines.com/coreboot/kerrypatches20110907.txt

Please let me know if I can assist further.

Thank you!
-Marshall Buschman

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20110907/866f1917/attachment.html>