Hello again, I sent my message below at the end of December, but never heard anything back. I realize that the end of December was bad timing; many people were likely to be away for year-end holidays. Thus, I am following up.
The boards I have, in rough order of ascending age, are: * MSI MS-7548 v1 (Compaq Aspen GL8E) * MSI MS-7310 v1 / K9N4 Ultra-F * Asus M2N-SLI Deluxe * Supermicro PDSME+ v1.1 * Jetway VM2DMP v2 * MSI MS-6119 v1.1 BX2 (There's a couple others in storage I can dig out if there's interest, an Asus A8N or A8V, and something more recent, IIRC) I realize that some of these are rather old, but there are similarly old motherboards listed in the supported motherboards list on the wiki[1], so I hope I'm not offering obsolete junk that Coreboot has no interest in, or has decided not to support any more. 1. https://www.coreboot.org/Supported_Motherboards On Wed, Dec 27, 2017 at 5:54 PM, Jeremy Banks <[email protected]> wrote: > Hello, > > I have some older motherboards I'd like to offer as QA targets for > autotest as described in the Testing section of Development Guidelines on > the wiki.[1] They are older boards, ranging from Slot 1 to Socket AM3. > Would the coreboot team have any interest in these, or are they too > obsolete to serve as QA targets? > > Assuming there is interest, what is required for an autotest setup? The > wiki says "a permanent connection to the net, a host system and some > special circuitry," are required. How permanent of a connection is > required? Is something like a cable or DSL line in the US sufficient, or is > something closer to leased space at a datacenter facility needed? > > Are there any particular requirements of a host system that necessitate a > particularly powerful system, or would a small single-board system like a > Raspberry Pi suffice? > > Regarding the special circuitry: I assume this includes equipment for > flashing the ROM chip on the motherboard under test, a means of controlling > at least the motherboard's power switch and reset line, and something to > monitor output from the board so to verify it did boot successfully (serial > port?). Is this roughly accurate? Are there other bits of the special > circuitry that I am missing, or specific brands/models of tools required to > implement the special circuitry? > > Regards, > > Jeremy Banks > > > 1. https://www.coreboot.org/Development_Guidelines#Testing > >
-- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
