Necromancing this thread...
Sage has a patch to *optionally* use a serial console log in
board_status.sh: http://review.coreboot.org/#/c/6094/
Earlier objections to such an approach seemed to stem from either:
- Desire to use cbmem console instead. A fine idea, but on some platforms
(especially
On Thu, Jul 3, 2014 at 4:18 PM, David Hendricks dhend...@google.com wrote:
Necromancing this thread...
Sage has a patch to *optionally* use a serial console log in
board_status.sh: http://review.coreboot.org/#/c/6094/
Earlier objections to such an approach seemed to stem from either:
-
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
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
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
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
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
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
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.
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
Am Dienstag, den 11.02.2014, 00:04 +0100 schrieb Vladimir 'φ-coder/phcoder'
Serbinenko:
On 10.02.2014 23:47, David Hendricks wrote:
On Sun, Feb 9, 2014 at 4:50 AM, Paul Menzel wrote:
currently no coreboot messages are stored for boards not supporting
CBMEM console (or where this
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
I 'm with Vladimir on this one.
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
On Sun, Feb 9, 2014 at 4:50 AM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
Dear coreboot folks,
currently no coreboot messages are stored for boards not supporting
CBMEM console (or where this option is disabled (currently by default))
or no coreboot *romstage* messages are
On 10.02.2014 23:47, David Hendricks wrote:
On Sun, Feb 9, 2014 at 4:50 AM, Paul Menzel
paulepan...@users.sourceforge.net
mailto:paulepan...@users.sourceforge.net wrote:
Dear coreboot folks,
currently no coreboot messages are stored for boards not supporting
CBMEM console
On Tuesday, February 11, 2014 12:04:33 AM Vladimir 'φ-coder/phcoder'
Serbinenko wrote:
If we let user supply
files at all, it should be added to report, not replace files, and it
should have some prefix to clearly indicate that user was involved in
creating them. E.g. user_serial_log.txt
On 11.02.2014 01:56, mrnuke wrote:
On Tuesday, February 11, 2014 12:04:33 AM Vladimir 'φ-coder/phcoder'
Serbinenko wrote:
If we let user supply
files at all, it should be added to report, not replace files, and it
should have some prefix to clearly indicate that user was involved in
Dear coreboot folks,
currently no coreboot messages are stored for boards not supporting
CBMEM console (or where this option is disabled (currently by default))
or no coreboot *romstage* messages are stored for boards, where the data
cannot be preserved (passed to ramstage).
Using the serial
On 09.02.2014 13:50, Paul Menzel wrote:
Dear coreboot folks,
currently no coreboot messages are stored for boards not supporting
CBMEM console
Is there any remaining? If so it's an issue to be fixed
(or where this option is disabled (currently by default))
Change the defaults.
or no
Am Sonntag, den 09.02.2014, 14:18 +0100 schrieb Vladimir 'φ-coder/phcoder'
Serbinenko:
On 09.02.2014 13:50, Paul Menzel wrote:
currently no coreboot messages are stored for boards not supporting
CBMEM console
Is there any remaining? If so it's an issue to be fixed
Sorry, no idea. I
On 09.02.2014 14:34, Paul Menzel wrote:
Am Sonntag, den 09.02.2014, 14:18 +0100 schrieb Vladimir 'φ-coder/phcoder'
Serbinenko:
On 09.02.2014 13:50, Paul Menzel wrote:
currently no coreboot messages are stored for boards not supporting
CBMEM console
Is there any remaining? If so it's an
On 02/09/2014 07:34 AM, Paul Menzel wrote:
Sorry, no idea. I thought there were some. At least not all boards
have been tested to my knowledge.
Please stop just throwing half-thoght proposals out there when you
have no idea (your words, not mine).
Alex
--
coreboot mailing list:
22 matches
Mail list logo
