It seems that this board is actually a 'Pro' version. At least it's addressed as 'Pro' in the list of boards, which requires board_enable.
Signed-off-by: Peter Lemenkov lemenkov@gmail.com --- board_enable.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/board_enable.c b/board_enable.c index 963bf58..f6462d9 100644 --- a/board_enable.c +++ b/board_enable.c @@ -1403,7 +1403,7 @@ struct board_pciid_enable board_pciid_enables[] = { {0x1106, 0x0691, 0, 0, 0x1106, 0x3057, 0, 0, NULL, "abit", "vt6x4", "Abit", "VT6X4", 0, OK, via_apollo_gpo4_lower}, {0x105a, 0x0d30, 0x105a, 0x4d33, 0x8086, 0x1130, 0x8086, 0, NULL, NULL, NULL, "Acorp", "6A815EPD", 0, OK, board_acorp_6a815epd}, {0x1022, 0x746B, 0, 0, 0, 0, 0, 0, NULL, "AGAMI", "ARUMA", "agami", "Aruma", 0, OK, w83627hf_gpio24_raise_2e}, - {0x1106, 0x3177, 0x17F2, 0x3177, 0x1106, 0x3148, 0x17F2, 0x3148, NULL, NULL, NULL, "Albatron", "PM266A", 0, OK, w836xx_memw_enable_2e}, + {0x1106, 0x3177, 0x17F2, 0x3177, 0x1106, 0x3148, 0x17F2, 0x3148, NULL, NULL, NULL, "Albatron", "PM266A Pro", 0, OK, w836xx_memw_enable_2e}, {0x1106, 0x3205, 0x1106, 0x3205, 0x10EC, 0x8139, 0xA0A0, 0x0477, NULL, NULL, NULL, "AOpen", "vKM400Am-S", 0, OK, it8705f_write_enable_2e}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, NULL, "artecgroup", "dbe61", "Artec Group", "DBE61", 0, OK, board_artecgroup_dbe6x}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, NULL, "artecgroup", "dbe62", "Artec Group", "DBE62", 0, OK, board_artecgroup_dbe6x},
On Wed, May 26, 2010 at 09:30:45PM +0400, Peter Lemenkov wrote:
It seems that this board is actually a 'Pro' version. At least it's addressed as 'Pro' in the list of boards, which requires board_enable.
Signed-off-by: Peter Lemenkov lemenkov@gmail.com
Yep, thanks, r1015.
See also: http://www.flashrom.org/pipermail/flashrom/2009-July/000003.html
The board-enable was originally for a PM266A Pro, but should also work for the plain PM266A. I think it makes sense to mention the Pro in the table, if anybody tests on PM266A at some point and reports a mismatch in the name of the detected board we can maybe request a dmidecode to differentiate between the two boards, if possible and needed.
Uwe.