All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@frus.com>
To: Helge Deller <deller@gmx.de>
Cc: Michael Cree <mcree@orcon.net.nz>,
	debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Subject: Re: 5.17.0 boot issue on Miata
Date: Wed, 6 Apr 2022 17:44:01 -0500	[thread overview]
Message-ID: <Yk4XsdHvjrLqN1LR@gherkin.frus.com> (raw)
In-Reply-To: <10d61d8f-edfc-fc39-0936-233692464dbd@gmx.de>

On Tue, Apr 05, 2022 at 08:22:48PM +0200, Helge Deller wrote:
> You don't need to enable it, but for alpha it's probably beneficial to enable it.
> When enabled, you will see a big speed improvement when logging in to a graphics text
> console and printing info.  E.g. try "time dmesg" with and without that option...
> The "dmesg" will scroll the screen, and that's what it accelerates (only if the driver
> has such hardware bitblt-support).

v5.17-rc2 ok.  v5.17-rc3 I get the disk sector errors and hang that I
reported in the first message in this thread.

(Unrelated, I *did* enable the framebuffer option, and that part of the
boot worked just fine.)

I'm going to try a native build of '-rc3' just to rule out any
cross-compiler strangeness.  Should have something to report in another
34 hours or so :-(.

--Bob

  reply	other threads:[~2022-04-06 22:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  2:54 5.17.0 boot issue on Miata Bob Tracy
2022-03-26 22:21 ` Michael Cree
2022-04-05  1:42   ` Bob Tracy
2022-04-05  5:01     ` Michael Cree
2022-04-05 13:55       ` Bob Tracy
2022-04-05 18:22         ` Helge Deller
2022-04-06 22:44           ` Bob Tracy [this message]
2022-04-08 13:02             ` Bob Tracy
2022-04-19  4:53               ` Bob Tracy
2022-04-25  9:26                 ` John Garry
2022-04-25  9:26                   ` John Garry
2022-05-03 15:50                   ` Bob Tracy

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=Yk4XsdHvjrLqN1LR@gherkin.frus.com \
    --to=rct@frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=deller@gmx.de \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    /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.