grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: GRUB as coreboot payload with *working* AHCI mode support
Date: Sun, 28 Apr 2013 13:25:23 +0200	[thread overview]
Message-ID: <517D0723.6040805@gmail.com> (raw)
In-Reply-To: <1367139772.4598.14.camel@mattotaupa>

[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]

On 28.04.2013 11:02, Paul Menzel wrote:

> Dear GRUB folks,
> 
> 
> just for your information, I successfully tested revision 4911
> containing the AHCI support, Vladimir committed yesterday. Big thanks to
> Vladimir! Here is the serial log from running coreboot with the GRUB
> payload on the ASRock E350M1.
> 

Nice to hear. Thanks for testing.


>         02.316: <1b>[H<1b>[J<1b>[1;1Hdisk/ahci.c:211: dev: 0:11.0
> 
> Here the debug messages start as there is `set debug="ahci"` in
> `grub.cfg` in the memdisk. (Not sure where the strange characters in the
> beginning come from though.)

It's an escape sequence ehich causes screen clear when running vt100
compatible terminal.

>         02.317: disk/ahci.c:267: AHCI is in compat mode. Switching
> 
> I have to read about that and figure out, if and where I can configure
> that mode in coreboot. Vladimir, could you please add to the error
> message, to what mode the mode is switched to?

It's not an error, it's perfectly specified part of AHCI startup. It's
GHC.AE

>         10.269: 
>         10.269: <1b>[m<1b>[4;2H+----------------------------------------------------------------------------+<1b>[5;2H|<1b>[5;79H|<1b>[6;2H|<1b>[6;79H|<1b>[7;2H|<1b>[7;79H|<1b>[8;2H|<1b>[8;79H|<1b>[9;2H|<1b>[9;79H|<1b>[10;2H|<1b>[10;79H|<1b>[11;2H|<1b>[11;79H|<1b>[12;2H|<1b>[12;79H|<1b>[13;2H|<1b>[13;79H|<1b>[14;2H|<1b>[14;79H|<1b>[15;2H|<1b>[15;79H|<1b>[16;2H|<1b>[16;79H|<1b>[17;2H+----------------------------------------------------------------------------+<1b>[m<1b>[18;2H<1b>[m
>         10.269:       Use the ^ and v keys to select which entry is highlighted.
>         10.269:       Press enter to boot the selected OS, `e' to edit the commands
>         10.269:       before booting or `c' for a command-line.
>         […]
> 
> So my Western Digital WD20EARS seems to take about ten seconds to start
> up. (Under SeaBIOS it has the same behavior.)

Hm, it's somewhat slow to spinup but sounds credible that some drives
would need so much time.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2013-04-28 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28  9:02 GRUB as coreboot payload with *working* AHCI mode support Paul Menzel
2013-04-28 11:25 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-04-28 12:04   ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=517D0723.6040805@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).