From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Baytrail/T (ASUS T100 etc) regression from 3.13 onwards
Date: Tue, 11 Feb 2014 11:45:24 -0800 [thread overview]
Message-ID: <20140211114524.42ceefa5@jbarnes-desktop> (raw)
In-Reply-To: <20140211182812.7cc8854a@alan.etchedpixels.co.uk>
On Tue, 11 Feb 2014 18:28:12 +0000
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> wrote:
> O> > According to the reg dumps, this is actually a MIPI panel we're failing
> > > to bring up properly. We're working on that issue, but in the
> > > meantime, maybe something like the below would work for you?
> >
> > A module paramater to fix a bug? Ugh, that's almost worse than just
> > reverting the original patch, right?
> >
> > Please don't do this, the distros will hate you even more than they
> > currently do :)
>
> Can we just turn hot plug detection off if a panel is present for now ?
Looks like another option would be to add an 'e' to your forced boot
line. That should prevent the detection stuff from running. E.g. in
your case:
video=VGA-1:1366x768e
There's some info on this in Documentation/fb/modedb.txt
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-02-11 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 13:33 Linux 3.13-rc8 Linus Torvalds
2014-01-14 12:01 ` One Thousand Gnomes
2014-02-11 14:22 ` Baytrail/T (ASUS T100 etc) regression from 3.13 onwards One Thousand Gnomes
2014-02-11 16:35 ` Greg KH
2014-02-11 18:11 ` Jesse Barnes
2014-02-11 18:18 ` Greg KH
2014-02-11 18:28 ` Jesse Barnes
2014-02-11 18:28 ` One Thousand Gnomes
2014-02-11 19:45 ` Jesse Barnes [this message]
2014-02-11 20:58 ` One Thousand Gnomes
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=20140211114524.42ceefa5@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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