From: David Kuehling <dvdkhlng@gmx.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [bug] Wrong machtype argument passed for fuloong-2f
Date: Sat, 29 Oct 2011 13:43:09 +0200 [thread overview]
Message-ID: <87pqhgf2gi.fsf@snail.Pool> (raw)
In-Reply-To: <20111029103758.GM4110@mails.so.argh.org> (Andreas Barth's message of "Sat, 29 Oct 2011 12:37:58 +0200")
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
>>>>> "Andreas" == Andreas Barth <aba@not.so.argh.org> writes:
> * 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?
No, don't think so. (Well, there are some issues with the fuloong box,
but they don't seem to be fixed after patching fuloong's boot argument)
> 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 ...).
I didn't find a method to make linux report the actual mach type that it
is running with, so I don't know what it fell back to, and I just went
the safe route of patching my version of grub.
cheers,
David
--
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-10-29 11:43 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
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 [this message]
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=87pqhgf2gi.fsf@snail.Pool \
--to=dvdkhlng@gmx.de \
--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.