From: Dave Young <dyoung@redhat.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: matt.fleming@intel.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi earlyprintk fix
Date: Thu, 7 Nov 2013 20:00:12 +0800 [thread overview]
Message-ID: <20131107120012.GA4116@dhcp-16-126.nay.redhat.com> (raw)
In-Reply-To: <20131106084921.GA22856@console-pimps.org>
On 11/06/13 at 08:49am, Matt Fleming wrote:
> On Mon, 04 Nov, at 08:58:53PM, Dave Young wrote:
> > On 11/04/13 at 10:37am, Matt Fleming wrote:
> > > On Sun, 03 Nov, at 08:16:47PM, Dave Young wrote:
> > > >
> > > > there's below one line shift problem:
> > > >
> > > > ACPI=0xdabfe000 ACPI 2.0=0xdabfe014 SMBIOS=0xdaa9e000
> > > > [ 0.000000] efi:
> > > >
> > > > In fact check efi_y and the lfb_height should be compared at the begin of the
> > > > loop of early_efi_write
> > >
> > > Hmm... this is interesting. I can't produce this on any of my machines.
> > > Where did you see this? What hardware?
> >
> > It's my laptop Thinkpad T420, the screen scolls very fast, I use boot_delay=500
> > to verify it with my patch for moving boot_delay param an early param.
>
> Dave, how are you booting your laptop? Are you using grub? Does the
> earlyprintk output start at the bottom of the screen? Do you set any
> parameters for efifb?
I tried both grub and efi stub. The messages seems come from the n-1 line
of the screen. I did not set any parameters by myself.
next prev parent reply other threads:[~2013-11-07 12:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 12:16 Dave Young
2013-11-04 10:37 ` Matt Fleming
2013-11-04 12:58 ` Dave Young
2013-11-06 8:49 ` Matt Fleming
2013-11-07 12:00 ` Dave Young [this message]
2013-11-06 9:23 ` Dave Young
2013-11-06 9:38 ` Matt Fleming
2013-11-07 12:09 ` Dave Young
2013-11-08 10:36 ` Matt Fleming
2013-11-09 3:44 ` Dave Young
2013-11-11 16:13 ` Matt Fleming
2013-11-12 2:22 ` Dave Young
2013-12-18 9:52 ` Dave Young
2013-12-18 10:31 ` Matt Fleming
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=20131107120012.GA4116@dhcp-16-126.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®