linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kate Alhola <kate@iti.fi>
To: Wolfgang Denk <wd@denx.de>
Cc: Stefan Nickl <Stefan.Nickl@kontron.com>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Lite5200 CoralP issues
Date: Fri, 02 Jul 2004 14:35:05 +0300	[thread overview]
Message-ID: <40E54869.4070908@iti.fi> (raw)
In-Reply-To: <20040702085145.0A0C9C109F@atlas.denx.de>


Wolfgang Denk wrote:

>In message <40E514DE.6020300@iti.fi> you wrote:
>
>
>>>This is why we implemented an accelerated X11 driver for the Coral-P.
>>>
>>>
>>>
>>I should try this new one. With the older one i have some problems with get all required
>>virtual console etc drivers to compiled to kernel to make Xfree 4.4 happy. Ok, now
>>there looks a like to be icecube_5200_CoralP_defconfig
>>
>>
>Yes, this is what we use for testing. It requires  a  USB  mouse  and
>keyboard to make the X11 server happy.
>
>
>
I took as test the yours uImage-LITE5200 kernel etc. It booted up
nicelly with newest
CVS snapshot with console text to CoralP display.

But still starting X it says "can not open free VT". As i earlier wrote
on list, there is even hard coded
in Xfree sources that it tries open /dev/tty0 with following strace results

open("/dev/tty0", O_WRONLY)             = 4
ioctl(4, 0x5600, 0x101b6eb0)            = -1 ENOTTY (Inappropriate ioctl
for device)

The problem is that /dev/tty0 looks a like to be hardcoded to
"xf86OpenConsole(void)" in xfree86 lnx_init.c and
it is called unconditionally from xf86Init.c . I have not found any
switch to switch console off from xfree86
config files. Also linkig /dev/tty to /dev/null or /dev/vcs0 etc does
not help, it just replaces
"can not open" error with "Cannot find a free VT".

How you get avoid this one ?

>>May be it is worth to try use QT with X11 server instead using embedded qt direct to
>>fb device. In older driver it was anyhow much better to use embedded qt direrctly.
>>
>>
>
>We have standard versions of Debian  and  YellowDog  running  on  the
>LITE5200, so Qt embedded should be pretty straightforward, too.
>
>
The largest problem is to make minimun set that fits in a Flash memory
with enough functions.
I think that i am still missing something important why i can't get X
running with CoralP drivers.
It needs something and i should find out what is needed. If there is
full yellowdog, then
you have 99.9% extra for most embedded systems.

OK, there is two ways, take YDL and start strip it down untiull it stops
working
or then find out every dependensy that is needed to get minimun system
running.
I think that is better to find out and understand these dependensies.

The Embedded QT runs easier because there is less dependensies to some
strange things
but now with accellerated coralP driver there is reason use X server.

Finally anyhow in embedded systems there should be GUI that works
without any dependensies
to mouse/keyboard

Kate

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-02 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01  9:18 Lite5200 PCI not working Wolfgang Denk
2004-07-01 11:36 ` Kate Alhola
2004-07-01 12:38   ` Stefan Nickl
2004-07-01 22:20     ` Kate Alhola
2004-07-01 22:29       ` Wolfgang Denk
2004-07-02  4:43         ` Kate Alhola
2004-07-02  7:22           ` Wolfgang Denk
2004-07-02  7:55             ` Kate Alhola
2004-07-02  8:51               ` Wolfgang Denk
2004-07-02 11:35                 ` Kate Alhola [this message]
2004-07-02 13:46                   ` Lite5200 CoralP issues Mark Chambers
2004-07-02 14:51                     ` Wolfgang Denk
2004-07-08 11:57             ` Lite5200 PCI not working Stefan Nickl
2004-07-08 12:12               ` Wolfgang Denk

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=40E54869.4070908@iti.fi \
    --to=kate@iti.fi \
    --cc=Stefan.Nickl@kontron.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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).