From: Tomasz Sterna <tomek@xiaoka.com>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance.
Date: Fri, 01 Oct 2010 22:07:02 +0200 [thread overview]
Message-ID: <1285963622.25392.5.camel@wing> (raw)
In-Reply-To: <1285948046.22265.12.camel@m0nster>
Dnia 2010-10-01, pią o godzinie 08:47 -0700, Daniel Walker pisze:
> I don't have access to Streak hardware, and I've not talked to anyone
> that does. But if you give us the OOPS message we can try to figure
> out what's going on..
Do you say, that on other Snapdragon hardware msm-2.6.35 tree with
console=tty works fine and there is no error?
> BTW did Dell release a kernel for Streak? They might already have a
> workaround in their kernel.
Yes they did: http://opensource.dell.com/releases/streak/
(This is where I ported the changes and drivers from)
But this kernels have exactly the same problem.
framebuffer driver works fine accessed from userspace, but breaks on
displaying kernel boot messages. Right after the message:
Console: switching to colour frame buffer device 60x50
I will try to retype the OOPS message, but it's hard - it scrolls out of
the screen ;-)
next prev parent reply other threads:[~2010-10-01 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:42 [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance Tomasz Sterna
2010-09-30 23:04 ` Daniel Walker
2010-10-01 8:52 ` Tomasz Sterna
2010-10-01 15:47 ` Daniel Walker
2010-10-01 20:07 ` Tomasz Sterna [this message]
2010-10-02 0:26 ` Daniel Walker
2010-10-01 21:11 ` Tomasz Sterna
[not found] ` <AANLkTimVpsmWLpXwuLyFgC3sOSMVCbF38DNRL13_5bgk@mail.gmail.com>
2010-10-02 10:14 ` Bradley Smith
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=1285963622.25392.5.camel@wing \
--to=tomek@xiaoka.com \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-msm@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 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.