Re: [coreboot] Coding for free
Nitin Issac Joy wrote: I am Nitin Issac Joy, 2nd Year Computer Science Engineering Student from India, wanting to contribute to coreboot. I want more hand-on experience with ASM and interfacing which is the reason why I am doing this. I know more than basic ASM, well versed in C. That's a good starting point, but you'll quickly have to learn many x86 details. Can anyone of you guide me? I think you'll find that everyone in the coreboot community is quite busy, and that you will have to learn most things on your own. Start out with building coreboot and running it in QEMU. That doesn't require buying any hardware and can already let you work on many different aspects of booting. If you want to continue with the project you will eventually need to work with hardware, which requires a suitable development environment with some tools and a target system which is not your primary machine. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Ram Init: Intel i945: Timing parameters
Mohit Gupta wrote: Don't understand why Intel has made DRAM controller setup/Ram-init documentation NDA, Many people wonder about the same thing. It's not clear. and have made chipset documentation public The chipset docs aren't really published. Only some parts of them. ** Important Note This email (including any attachments) contains information which is confidential Why are you sending confidential information in plain text to a public mailing list which is archived all on the web? That seems silly. Please make sure not to include any such nonsense disclaimers in your emails at the very least when you participate in open source projects. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
Am Mittwoch, den 19.02.2014, 00:47 +0100 schrieb Vladimir 'φ-coder/phcoder' Serbinenko: On 19.02.2014 00:18, Paul Menzel wrote: But in general I think I agree with Vladimir. CBMEM console should be supported and if not then that should be fixed. I also agree, but it’ll take more time and the above is a good work-around for the mean time. Strongly disagree workarounds are like glue: they stick around. This one is one that will stick around once implemented. It's better to avoid workarounds if sane solution is within reach. In this case you still haven't even named a single board where CBMEMC doesn't work. CBMEM console does not work for romstage on all AMD based boards. Ask Rudolf and Kyösti for more details, but as far as I understood them, the solution is *not* easy and not within reach at all. Thanks, Paul signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] `DEBUG_INTEL_ME` (incorrectly) only selected for Intel BD82x6x
Dear coreboot folks, looking through `src/console/Kconfig` I noticed if SOUTHBRIDGE_INTEL_BD82X6X DEFAULT_CONSOLE_LOGLEVEL_8 # Only visible with the right southbridge and loglevel. config DEBUG_INTEL_ME bool Verbose logging for Intel Management Engine default n help Enable verbose logging for Intel Management Engine driver that is present on Intel 6-series chipsets. endif which seems odd as currently other chipsets needing the Intel Management Engine were submitted. $ git grep DEBUG_INTEL_ME src/Kconfig:config DEBUG_INTEL_ME src/southbridge/intel/bd82x6x/me.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/bd82x6x/me_8.x.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/fsp_bd82x6x/me.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/fsp_bd82x6x/me_8.x.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/ibexpeak/me.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/lynxpoint/me_9.x.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/lynxpoint/me_9.x.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/lynxpoint/me_9.x.c:#if CONFIG_DEBUG_INTEL_ME src/southbridge/intel/lynxpoint/me_9.x.c:#if CONFIG_DEBUG_INTEL_ME I am unable to test this, so it would be great if somebody else could fix this. Thanks, Paul signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
On 19.02.2014 23:03, Paul Menzel wrote: Am Mittwoch, den 19.02.2014, 00:47 +0100 schrieb Vladimir 'φ-coder/phcoder' Serbinenko: On 19.02.2014 00:18, Paul Menzel wrote: But in general I think I agree with Vladimir. CBMEM console should be supported and if not then that should be fixed. I also agree, but it’ll take more time and the above is a good work-around for the mean time. Strongly disagree workarounds are like glue: they stick around. This one is one that will stick around once implemented. It's better to avoid workarounds if sane solution is within reach. In this case you still haven't even named a single board where CBMEMC doesn't work. CBMEM console does not work for romstage on all AMD based boards. Ask Rudolf and Kyösti for more details, but as far as I understood them, the solution is *not* easy and not within reach at all. As I already told the info from romstage is likely of minor importance if the board boots. And if it doesn't, well no board status. If any of the info from romstage is relevant it can be printed in ramstage as well Thanks, Paul signature.asc Description: OpenPGP digital signature -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
Paul, your idea is a non-starter, so let's wind this conversation up, ok? ron -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
On 02/20/2014 12:28 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 19.02.2014 23:03, Paul Menzel wrote: Am Mittwoch, den 19.02.2014, 00:47 +0100 schrieb Vladimir 'φ-coder/phcoder' Serbinenko: On 19.02.2014 00:18, Paul Menzel wrote: But in general I think I agree with Vladimir. CBMEM console should be supported and if not then that should be fixed. I also agree, but it’ll take more time and the above is a good work-around for the mean time. Strongly disagree workarounds are like glue: they stick around. This one is one that will stick around once implemented. It's better to avoid workarounds if sane solution is within reach. In this case you still haven't even named a single board where CBMEMC doesn't work. CBMEM console does not work for romstage on all AMD based boards. Ask Rudolf and Kyösti for more details, but as far as I understood them, the solution is *not* easy and not within reach at all. As I already told the info from romstage is likely of minor importance if the board boots. And if it doesn't, well no board status. If any of the info from romstage is relevant it can be printed in ramstage as well You do not get raminit debug output printed in ramstage. Unfortunately, the case of incompatible DIMMs seems to be common one with recent AGESA ports so information from romstage what DIMMs have worked is actually relevant. Kyösti -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
You do not get raminit debug output printed in ramstage. Unfortunately, the case of incompatible DIMMs seems to be common one with recent AGESA ports so information from romstage what DIMMs have worked is actually relevant. Just read this data from registers and print it. Kyösti signature.asc Description: OpenPGP digital signature -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
Am Mittwoch, den 19.02.2014, 23:56 +0100 schrieb Vladimir 'φ-coder/phcoder' Serbinenko: You do not get raminit debug output printed in ramstage. Unfortunately, the case of incompatible DIMMs seems to be common one with recent AGESA ports so information from romstage what DIMMs have worked is actually relevant. Just read this data from registers and print it. Until this is done, such data is lost and it is not nice to ask users to rerun stuff again with such a patch. So please, could we just decide on a name for the serial/USB debug log file and be done with this? Not a lot of people are going to do this anyway. Thanks, Paul signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
On 02/20/2014 12:56 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote: You do not get raminit debug output printed in ramstage. Unfortunately, the case of incompatible DIMMs seems to be common one with recent AGESA ports so information from romstage what DIMMs have worked is actually relevant. Just read this data from registers and print it. Neither of us has probably looked closely what details we are missing from AGESA romstages. I very much doubt it would be just static register configuration on memory controllers that could be dumped afterwards. AMD has an amount of SMP init going on in romstage along with possibly multiple logical CPUs using CAR etc. Kyösti -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] SeaVGABIOS with native vga init (Need testers)
On Sun, 16 Feb 2014 14:51:47 -0500 Kevin O'Connor ke...@koconnor.net wrote: There's also no cursor, which can probably be enhanced as well. Yes, I tested more, with seabios directly as a payload, for giving my old Lenovo x60 to someone and spending less time right now to explain him how to configure well grub to be used as a payload. And I saw the cursor issue, that's the most annoying issue because the grub( ran in BIOS platform mode ) that is loaded from disk doesn't show a cursor when editing the menu contents with 'e' I'm surprised you need ps2-keyboard-spinup if you chain load seabios. I'll retest soon. --- a/vgasrc/cbvga.c +++ b/vgasrc/cbvga.c @@ -162,8 +162,8 @@ cbvga_setup(void) SET_VGA(CBmode.height, ylines); SET_VGA(CBmode.depth, bpp); -// Setup BDA -vga_set_mode(CBMODENUM, MF_NOCLEARMEM); +// Setup BDA and clear screen. +vga_set_mode(CBMODENUM, 0); return 0; } Thanks a lot, I'll try that as soon as possible, but it's like 23:30 now here, so it'll be for another day. Denis. signature.asc Description: PGP signature -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [RFC] board_status: Add serial log to `serial_console.txt`
On Thursday, February 20, 2014 12:11:58 AM Paul Menzel wrote: Until this is done, such data is lost and it is not nice to ask users to rerun stuff again with such a patch. So please, could we just decide on a name for the serial/USB debug log file and be done with this? Not a lot of people are going to do this anyway. Paul! It's been decided! It's dead! Drop it! Alex -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
