From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [bug] Wrong machtype argument passed for fuloong-2f
Date: Sat, 29 Oct 2011 12:41:45 +0200 [thread overview]
Message-ID: <4EABD869.5040801@gmail.com> (raw)
In-Reply-To: <20111029103758.GM4110@mails.so.argh.org>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On 29.10.2011 12:37, Andreas Barth wrote:
> * David Kuehling (dvdkhlng@gmx.de) [111029 11:37]:
>> according to my /proc/cmdline grub passes
>> machtype=lemote-fuloong-2f-unknown as first argument to the linux
>> kernel.
> Did you see any issues because of that in Linux? Fallback within linux
> is MACH_LEMOTE_FL2F which is the one used with the argument
> "lemote-fuloong-2f-box" (not saying this bug shouldn't be fixed, but
> ...). Also I think grub should just forward the parameters added by
> pmon, but not adding them itself (except for the parameters via the
> grub configuration, e.g. root=...).
GRUB isn't restricted ot pmon environments so this argument makes little
sense to me.
>
> Andi
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-10-29 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 9:36 [bug] Wrong machtype argument passed for fuloong-2f David Kuehling
2011-10-29 10:37 ` Andreas Barth
2011-10-29 10:41 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-10-29 10:45 ` Andreas Barth
2011-10-29 10:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-29 13:56 ` Andreas Barth
2011-10-29 11:43 ` David Kuehling
2011-10-29 11:48 ` Andreas Barth
2011-10-29 20:46 ` David Kuehling
2011-10-29 20:54 ` Andreas Barth
2011-10-30 3:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-30 13:06 ` David Kuehling
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=4EABD869.5040801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.