The attached patch gets coreboot going on the ASRock E350M1 board.
This is an AMD family 14h Fusion board I bought for US $120, including
processor. The video option rom is from the supplied UEFI BIOS.
The patch modifies the persimmon project and is for development use,
not for commit. With this p
Scott Duplichan wrote:
> The attached patch gets coreboot going on the ASRock E350M1 board.
> This is an AMD family 14h Fusion board I bought for US $120, including
> processor. The video option rom is from the supplied UEFI BIOS.
>
> The patch modifies the persimmon project and is for development
-Original Message-
From: coreboot-boun...@coreboot.org [mailto:coreboot-boun...@coreboot.org] On
Behalf Of Peter Stuge
Sent: Wednesday, February 23, 2011 10:15 PM
To: coreboot@coreboot.org
Subject: Re: [coreboot] Coreboot for AMD Fusion family 14h: ASRock E350M1
Scott Duplichan wrote
Scott Duplichan wrote:
> > The patch modifies the persimmon project and is for development
> > use, not for commit.
>
> ]What would you like to add functionally before commiting?
>
> I guess the main thing to do before a commit is to branch persimmon
> and make an asrock e350m1 project. I suspect
Peter wrote:
]Great! Use svn cp to create the directory, then put your changes in
]there, and then svn diff should create the corresponding small patch
]that you sent already. I'm happy to ack. This looks like a nice board
]for a media center system.
]
]//Peter
Thanks Peter. I accidentally did th
Scott Duplichan wrote:
> I accidentally did the 'svn cp' step interactively instead of by
> patch. The attached patch completes the work of converting AMD
> Persimmon into ASRock E350M1.
Good stuff. Some simple comments, then I'll ack.
> A video option rom needs to be added to support the built-
Am Donnerstag, den 24.02.2011, 05:34 +0100 schrieb Peter Stuge:
> Scott Duplichan wrote:
These are really great news.
[…]
> This looks like a nice board for a media center system.
Indeed. There are some reviews available of this board [1][2].
Unfortunately in Germany all the online shops seem
Peter wrote:
]Scott Duplichan wrote:
]> I accidentally did the 'svn cp' step interactively instead of by
]> patch. The attached patch completes the work of converting AMD
]> Persimmon into ASRock E350M1.
]
]Good stuff. Some simple comments, then I'll ack.
]
]> A video option rom needs to be added
Scott Duplichan wrote:
> ]> A video option rom needs to be added to support the built-in uma
> ]> graphics.
> ]
> ]Does the default filename match what was extracted from factory EFI?
>
> I do not know of a way to recover the original filename of the
> extracted video BIOS. After booting the facto
Peter wrote:
]Scott Duplichan wrote:
]> ]> A video option rom needs to be added to support the built-in uma
]> ]> graphics.
]> ]
]> ]Does the default filename match what was extracted from factory EFI?
]>
]> I do not know of a way to recover the original filename of the
]> extracted video BIOS. A
* Scott Duplichan [110224 05:03]:
> The attached patch gets coreboot going on the ASRock E350M1 board.
> This is an AMD family 14h Fusion board I bought for US $120, including
> processor. The video option rom is from the supplied UEFI BIOS.
>
> The patch modifies the persimmon project and is for
Any chance to move the SSDTs to the northbridge/southbridge/cpu
directory instead of having them live under mainboard?
* Scott Duplichan [110224 07:05]:
> Index: src/mainboard/asrock/e350m1/acpi/ssdt2.asl
> ===
> --- src/mainboard/as
Stefan Reinauer wrote:
]> +#define SERIAL_DEV PNP_DEV(0x2e, W83627HF_SP1)
]if CONFIG_SIO_PORT is defined in Kconfig (why?) we could as well use it
]in romstage.c. Is there a chance to remove it from Kconfig instead?
Certainly the two occurrences of 2e is not ideal. This change works:
-#define
Stefan Reinauer wrote:
]Any chance to move the SSDTs to the northbridge/southbridge/cpu
]directory instead of having them live under mainboard?
It looks like SSDT2,3,4,5 are never used and can be removed from
this project.
Thanks,
Scott {
--
coreboot mailing list: coreboot@coreboot.org
htt
* Scott Duplichan [110225 02:02]:
> Stefan Reinauer wrote:
>
> ]> +#define SERIAL_DEV PNP_DEV(0x2e, W83627HF_SP1)
>
> ]if CONFIG_SIO_PORT is defined in Kconfig (why?) we could as well use it
> ]in romstage.c. Is there a chance to remove it from Kconfig instead?
>
> Certainly the two occurrence
On 02/24/11 13:48, Scott Duplichan wrote:
Peter wrote:
]Scott Duplichan wrote:
]> ]> A video option rom needs to be added to support the built-in uma
]> ]> graphics.
]> ]
]> ]Does the default filename match what was extracted from factory EFI?
]>
]> I do not know of a way to recover the o
Anish Patel wrote:
]this EFI bios is using the CSM module so it can use the traditional vBIOS.
]are there any plans to support this new GOP model they (the EFI guys)
]are trying to push?
I like the idea of replacing a 16-bit binary module with 32-bit
source code. But I think the use of EFI GOP i
On 03/10/11 13:36, Scott Duplichan wrote:
Anish Patel wrote:
]this EFI bios is using the CSM module so it can use the traditional vBIOS.
]are there any plans to support this new GOP model they (the EFI guys)
]are trying to push?
I like the idea of replacing a 16-bit binary module with 32-bit
so
Anish Patel wrote:
>> ]are there any plans to support this new GOP model they (the EFI
>> ]guys) are trying to push?
>>
>> I like the idea of replacing a 16-bit binary module with 32-bit
>> source code.
..
> Well Intel lets you get to their GOP module with IMGD/EMGD for
> certain products. They al
19 matches
Mail list logo
