Note that other LX platform "owners" should update the buildrom platform linuxbios tags to pick up the PERR#/SERR# fix.
Marc
I'm assuming, since you're Marc, that you tested it :-)
Acked-by: Ronald G. Minnich rminnich@gmail.com
can you run flashrom and actually flush?
thanks
ron
Ron, I have tested it. :) I have not used flashrom since I use a rom emulator. I will look into it. Marc
ron minnich wrote:
I'm assuming, since you're Marc, that you tested it :-)
Acked-by: Ronald G. Minnich rminnich@gmail.com
can you run flashrom and actually flush?
thanks
ron
On 9/26/07, Marc Jones marc.jones@amd.com wrote:
Ron, I have tested it. :) I have not used flashrom since I use a rom emulator. I will look into it.
I fixed my msm800sev problem. The part is an FWH part. We have a problem in flashrom in that parts can be FWH or LPC and I don't know how to detect this in flashrom. These dual-mode parts kind of break the structure a bit.
oh well.
ron
ron minnich wrote:
On 9/26/07, Marc Jones marc.jones@amd.com wrote:
Ron, I have tested it. :) I have not used flashrom since I use a rom emulator. I will look into it.
I fixed my msm800sev problem. The part is an FWH part. We have a problem in flashrom in that parts can be FWH or LPC and I don't know how to detect this in flashrom. These dual-mode parts kind of break the structure a bit.
oh well.
ron
Glad you figured this out. I couldn't think of anything off the top of my head.
For Geode 5536 you can check which mode it is in. DIVIL_BALL_OPT - MSR 51400015h PRI_BOOT_LOC [3:2]
It would be nice to have msr support in flashrom so it could handle write protect and rom type checking.
Marc
On 26/09/07 14:45 -0600, Marc Jones wrote:
ron minnich wrote:
On 9/26/07, Marc Jones marc.jones@amd.com wrote:
Ron, I have tested it. :) I have not used flashrom since I use a rom emulator. I will look into it.
I fixed my msm800sev problem. The part is an FWH part. We have a problem in flashrom in that parts can be FWH or LPC and I don't know how to detect this in flashrom. These dual-mode parts kind of break the structure a bit.
oh well.
ron
Glad you figured this out. I couldn't think of anything off the top of my head.
For Geode 5536 you can check which mode it is in. DIVIL_BALL_OPT - MSR 51400015h PRI_BOOT_LOC [3:2]
It would be nice to have msr support in flashrom so it could handle write protect and rom type checking.
Yes - you should just merge the readmsr and writemsr code into flashrom directly - avoid the outside middleman.
Jordan
I'm confused. Why do you have to talk differently to a FWH or LPC device? If the 5536 booted from a device, it should continue talking to that device unless someone changed the BALL_OPTS our from under it (like Marc said)
On 9/26/07, ron minnich rminnich@gmail.com wrote:
On 9/26/07, Marc Jones marc.jones@amd.com wrote:
Ron, I have tested it. :) I have not used flashrom since I use a rom emulator. I will look into it.
I fixed my msm800sev problem. The part is an FWH part. We have a problem in flashrom in that parts can be FWH or LPC and I don't know how to detect this in flashrom. These dual-mode parts kind of break the structure a bit.
oh well.
ron
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
On 9/26/07, Tom Sylla tsylla@gmail.com wrote:
I'm confused. Why do you have to talk differently to a FWH or LPC device? If the 5536 booted from a device, it should continue talking to that device unless someone changed the BALL_OPTS our from under it
the issue is that flashrom was not designed to associate two access methods for a single part. FWH has a totally different block locking method, requiring a second mmap, etc. I have found that a jedec (LPC) sequence can in some cases ID a part that is a FWH-strapped part. Weird but true -- I just saw it again today.
it's all a headache.
ron
On 9/26/07, Tom Sylla tsylla@gmail.com wrote:
I'm confused. Why do you have to talk differently to a FWH or LPC device? If the 5536 booted from a device, it should continue talking to that device unless someone changed the BALL_OPTS our from under it
the issue is that flashrom was not designed to associate two access methods for a single part. FWH has a totally different block locking method, requiring a second mmap, etc. I have found that a jedec (LPC) sequence can in some cases ID a part that is a FWH-strapped part. Weird but true -- I just saw it again today.
it's all a headache.
ron
On 26/09/07 11:48 -0600, Marc Jones wrote:
Note that other LX platform "owners" should update the buildrom platform linuxbios tags to pick up the PERR#/SERR# fix.
r42. Thanks.
-
Jordan Crouse -
Marc Jones -
ron minnich -
Tom Sylla