From: Hans de Goede <hdegoede@redhat.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: possible fb bug in linux-next 20150202
Date: Mon, 02 Feb 2015 13:42:59 +0000 [thread overview]
Message-ID: <54CF7EE3.3020404@redhat.com> (raw)
Hi,
On 02-02-15 14:36, Rares Aioanei wrote:
> Hi,
>
> First, sorry for the unproperly-formatted mail but I'm at work and this is
> the only way. Second, I installed the latest linux-next on a Dell Latitude
> D520 at work and the kernel won't boot unless I add nofb at the command
> line. Is this a known issue or do you need me to send all the good stuff
> (dmesg, cpuinfo and so on)? If there's anything I can do to help, please
> let me know. I have some time to test.
Not sure why you are sending this to me ?
Are you using a kernel with simplefb support enabled on x86? I only maintain
the simplefb driver, and you're not supposed to use that on x86.
Eitherway please send a detailed bug report to:
"Linux Fbdev development list <linux-fbdev@vger.kernel.org>"
with me in the Cc.
Regards,
Hans
reply other threads:[~2015-02-02 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54CF7EE3.3020404@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-fbdev@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).