From: Pavel Machek <pavel@ucw.cz>
To: Bernie Thompson <bernie@plugable.com>
Cc: roberto@unbit.it, gregkh@suse.de, Cyril Hrubis <metan@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: staging: udlfb -- staging version does not work, external does
Date: Sun, 11 Apr 2010 17:07:18 +0200 [thread overview]
Message-ID: <20100411150718.GA1401@ucw.cz> (raw)
In-Reply-To: <n2g480988181004110742w2ce92bfdr4f0f01216f879fe8@mail.gmail.com>
Hi!
> Thanks for the bug report!
You are welcome :-).
> > I tried getting udlfb to work in 2.6.34-rc*, and could not.
>
> What CPU arch are you on, and is it 32 or 64?
32bit Intel Core Duo.
> > 1) it hates vga console. If text-mode vga console is used (not
> > vesafb), system dies immeditaly during insmod or during boot if
> > monolithic kernel is used.
>
> It is a kernel oops? Where does the crash happen? Can you email any
> udlfb-specific output in logs (especially /var/log/kern.log)?
It just locks :-(.
> > 2) it does not display anything. With vesafb, it will not lockup the
> > system, and /dev/fb1 is created... Unfortunately, all I get is green
> > screen.
>
> The green screen means udlfb has initialized device and started
> rendering. So what this likely means is everything is fine -- just
> fbcon has matched against fb0, which is why it's not using the fb1
> udlfb screen.
Yep, but I still should be able to produce output on it.
> > (I tried testing with cat /bin/bash > /dev/fb1 and cat /dev/fb0 >
> > /dev/fb1).
>
> I don't think redirects like that will work. The fbcon module loads
> against one fb, and can only be switch with utilities like "fbset"
IMO they should work. First one should fill the screen with ~random
noise, and second should copy graphical representation on fb0 to
fb1. If they have same resolution and color depth, I should be looking
at copy of my console...
(And it does work with this driver:
> > So I tried
> >
> > Roberto De Ioris roberto at unbit.it
> > Wed Jun 10 08:00:07 PDT 2009
).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next parent reply other threads:[~2010-04-11 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100411072625.GA9926@elf.ucw.cz>
[not found] ` <n2g480988181004110742w2ce92bfdr4f0f01216f879fe8@mail.gmail.com>
2010-04-11 15:07 ` Pavel Machek [this message]
2010-04-11 16:42 ` staging: udlfb -- staging version does not work, external does Pavel Machek
2010-04-11 17:01 ` Bernie Thompson
2010-04-11 17:05 ` Pavel Machek
[not found] ` <20100411170117.GA22007@elf.ucw.cz>
[not found] ` <p2s480988181004111005kdeb479ddzd3719799f140f4a9@mail.gmail.com>
2010-04-11 17:18 ` Pavel Machek
2010-04-13 0:44 ` Bernie Thompson
2010-04-11 17:36 ` Pavel Machek
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=20100411150718.GA1401@ucw.cz \
--to=pavel@ucw.cz \
--cc=bernie@plugable.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=roberto@unbit.it \
/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.