From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Update palo documentation
Date: Sun, 7 Jul 2019 22:01:45 +0200 [thread overview]
Message-ID: <70b4c08b-de2e-91f7-890d-767cad3dfad1@gmx.de> (raw)
In-Reply-To: <1562528703.3216.17.camel@HansenPartnership.com>
On 07.07.19 21:45, James Bottomley wrote:
> On Sun, 2019-07-07 at 20:44 +0200, Helge Deller wrote:
>> On 07.07.19 20:01, James Bottomley wrote:
> [...]
>>> +Palo allows you to specify a kernel command line, which is stored
>>> in
>>> +the firstboot partition. The format should be kernel first
>>> followed
>>> +by an optional initrd= and then the rest of the kernel parameters.
>>> +For parisc system, you should specify a boot console as console=
>>> on
>>> +the command line.
>>
>> No, that's not recommended.
>> palo will detect the currently used console and add it automatically,
>> so one should NOT specify a console parameter.
>
> Ah well, I've got an rp3430 so its console name changes depending on
> kernel, which is why I specify it, but I can remove that from "For
> parisc system, you should ..."
The rp34xx series should work fine as well.
Can you give details, because I pushed a patch into stable series
which should have fixed that:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bcf3f1752a622f1372d3252d0fea8855d89812e7
Helge
next prev parent reply other threads:[~2019-07-07 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 18:01 [PATCH] Update palo documentation James Bottomley
2019-07-07 18:44 ` Helge Deller
2019-07-07 19:45 ` James Bottomley
2019-07-07 20:01 ` Helge Deller [this message]
2019-07-07 20:58 ` James Bottomley
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=70b4c08b-de2e-91f7-890d-767cad3dfad1@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-parisc@vger.kernel.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).