On 03/18/2015 02:49 AM, Carl-Daniel Hailfinger wrote:
[off-list]
Hi Timothy,
On 16.03.2015 18:15, Timothy Pearson wrote:
On 03/16/2015 08:17 AM, Alexander Couzens wrote:
On Mon, 16 Mar 2015 01:20:17 -0500
Timothy Pearson wrote:
Just wanted to mention that Raptor Engineering now has an aut
On 03/16/2015 08:17 AM, Alexander Couzens wrote:
On Mon, 16 Mar 2015 01:20:17 -0500
Timothy Pearson wrote:
Just wanted to mention that Raptor Engineering now has an automated test
stand for the ASUS KFSN4-DRE board, run nightly with automatic bricking
recovery. It has two Opteron 2431 (AMD Fa
On Mon, 16 Mar 2015 01:20:17 -0500
Timothy Pearson wrote:
> Just wanted to mention that Raptor Engineering now has an automated test
> stand for the ASUS KFSN4-DRE board, run nightly with automatic bricking
> recovery. It has two Opteron 2431 (AMD Family 10h, 6 core @ 2.4GHz)CPUs
> and 6GB of
On 02/18/2015 05:14 PM, Carl-Daniel Hailfinger wrote:
Hi,
I am currently planning to set up a test system with 5 (later up to 10)
machines boot testing each new coreboot commit. This test system will be
serviced (i.e. recovery from bricking) Mo-Fr during CET/CEST office hours.
Just wanted to m
Am Freitag, den 27.02.2015, 12:20 +0100 schrieb Carl-Daniel Hailfinger:
> On 19.02.2015 00:14, Carl-Daniel Hailfinger wrote:
> > The selection of target systems should include:
> > 1. at least one x86 laptop without an active ME (present but inactive
> > would be OK)
> > 2. at least one x86 laptop
This is a friendly reminder. 2 days left for nominations of systems.
On 19.02.2015 00:14, Carl-Daniel Hailfinger wrote:
> The selection of target systems should include:
> 1. at least one x86 laptop without an active ME (present but inactive
> would be OK)
> 2. at least one x86 laptop which can bo
On Wed, Feb 18, 2015 at 3:14 PM, Carl-Daniel Hailfinger <
c-d.hailfinger.devel.2...@gmx.net> wrote:
> Hi,
>
> I am currently planning to set up a test system with 5 (later up to 10)
> machines boot testing each new coreboot commit. This test system will be
> serviced (i.e. recovery from bricking)
2015-02-19 17:22 GMT+01:00 Kevin O'Connor :
> It would be a bit of work to get the software working and packaged
> nicely - but if it was, I think it could enable many more users to
> participate in automated tests and remote development.
That already was the hope of many coreboot related automated
On Thu, Feb 19, 2015 at 12:35:11PM +0100, Patrick Georgi via coreboot wrote:
> 2015-02-19 0:14 GMT+01:00 Carl-Daniel Hailfinger
> :
> > I am currently planning to set up a test system with 5 (later up to 10)
> > machines boot testing each new coreboot commit. This test system will be
> > serviced (
2015-02-19 0:14 GMT+01:00 Carl-Daniel Hailfinger
:
> I am currently planning to set up a test system with 5 (later up to 10)
> machines boot testing each new coreboot commit. This test system will be
> serviced (i.e. recovery from bricking) Mo-Fr during CET/CEST office hours.
>
> Current goals for
2015-02-19 0:14 GMT+01:00 Carl-Daniel Hailfinger
:
> Hi,
>
> I am currently planning to set up a test system with 5 (later up to 10)
> machines boot testing each new coreboot commit. This test system will be
> serviced (i.e. recovery from bricking) Mo-Fr during CET/CEST office hours.
(..)
> Pleas
Hi,
I am currently planning to set up a test system with 5 (later up to 10)
machines boot testing each new coreboot commit. This test system will be
serviced (i.e. recovery from bricking) Mo-Fr during CET/CEST office hours.
Current goals for every commit:
- Check if coreboot + SeaBIOS are able to
12 matches
Mail list logo
