Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Helge Deller <deller@gmx.de>, Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Update palo documentation
Date: Sun, 07 Jul 2019 13:58:12 -0700	[thread overview]
Message-ID: <1562533092.3216.20.camel@HansenPartnership.com> (raw)
In-Reply-To: <70b4c08b-de2e-91f7-890d-767cad3dfad1@gmx.de>

On Sun, 2019-07-07 at 22:01 +0200, Helge Deller wrote:
> 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/co
> mmit/?id=bcf3f1752a622f1372d3252d0fea8855d89812e7

It's a 3.16 based rescue kernel and ramdisk I built long ago and keep
around just in case.

James


      reply	other threads:[~2019-07-07 20:58 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
2019-07-07 20:58       ` James Bottomley [this message]

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=1562533092.3216.20.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --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