ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] How to start X.


From: Stuart Hughes
Subject: Re: [Ltib] How to start X.
Date: Fri, 13 Aug 2010 18:32:51 +0100
User-agent: Thunderbird 2.0.0.16 (X11/20080707)

Hi Kevin,

Which link is giving trouble?  I just tried dltest and it was okay:

$ ./ltib -p qtopia-4 --dltest
Testing network connectivity for gpp
OK GPP: is available
OK GPP: freescale-powerpc-linux-gnu-4.3-74.i686.rpm

Processing platform: Freescale MPC8349E-mITX board
====================================================
using config/platform/mpc8349itx/.config

Processing: qtopia-4
======================
OK GPP: qtopia-opensource-src-4.3.0.tar.gz
OK GPP: qtopia-opensource-4.3.0-qconfig-cursor-mouse-01.patch
OK GPP: qtopia-opensource-4.3.0-native-endian-audio-01.patch
OK GPP: qtopia-opensource-4.3.0-standard-touchscreen-01.patch
OK GPP: qtopia-opensource-4.3.0-imx21-touchscreen-01.patch
OK GPP: qtopia-opensource-4.3.0-mx21-buttons-01.patch
OK GPP: qtopia-opensource-4.3.0-screensaver-01.patch
OK GPP: qtopia-opensource-4.3.0-mxc-platform-01.patch
OK GPP: qtopia-opensource-4.3.0-imx21-platform-01.patch
OK GPP: qtopia-opensource-4.3.0-gstreamer-01.patch
OK GPP: qtopia-opensource-4.3.0-usbkeyboard.patch
OK GPP: qtopia-opensource-4.3.0-video-playback-01.patch
OK GPP: qtopia-opensource-4.3.0-open_with_O_CREAT_fix.patch

Started: Fri Aug 13 18:31:38 2010
Ended:   Fri Aug 13 18:31:44 2010
Elapsed: 6 seconds

Build Succeeded


BTW: I've never tried qtopia-4, it's huge.

Regards, Stuart

Kevin Wells wrote:
> Hi Stuart,
> 
> Thq Qtopia 4 link might be bad. I can't seem to pull that file for a
> check, but all the others are pulling fine.
> 
> Hi Mario,
> 
> Tiny-X and Qtopia 2 should build fine. I haven't tried Qtopia 4 yet.
> 
> Qtopia 2 will work with no changes to the kernel and only enabling
> Qtopia 2 (and mouse support) in the LTIB package menu. If you don't
> select automatic startup of Qtopia2, you can manually start it once
> the shell comes up with:
> nxp#sh /etc/rc.d/init.d/qtopia (tying from memory)
> 
> Tiny-X will compile, but you'll get screen errors when you run it.
> (A matching display config couldn't be found). You'll see errors
> Similar to:
> ******
> address@hidden /]# fbset
> 
> mode "240x320-58"
>         # D: 5.213 MHz, H: 18.752 kHz, V: 57.698 Hz
>         geometry 240 320 240 320 16
>         timings 191828 22 11 2 1 5 2
>         accel false
>         rgba 5/11,6/5,5/0,0/0
> endmode
> 
>  address@hidden /]# Xfbdev -screen 240x320x16x58 -mouse mouse -keybd keyboard
> FBIOPUT_VSCREENINFO: Invalid argument
> 
> Fatal server error:
> no screens found
> ******
> 
> The changes below will get X support working...the patches need to be
> applied to the source in the ./rpm/BUILD area. (Unpack source as
> necessary)
> 
> The first change to get X working is to add the display geometry info
> in the kmode.c file in the X source. This is located at:
> ./rpm/BUILD/xorg-server-1.4.2/hw/kdrive/src/kmode.c
> Use the following patch...
> ******
> diff -Naur xorg-server-1.4.2/hw/kdrive/src/kmode.c 
> xorg-server-1.4.2-new/hw/kdrive/src/kmode.c
> --- xorg-server-1.4.2/hw/kdrive/src/kmode.c   2010-08-12 16:37:58.251918856 
> -0700
> +++ xorg-server-1.4.2-new/hw/kdrive/src/kmode.c       2010-08-12 
> 15:31:28.205045092 -0700
> @@ -39,6 +39,12 @@
>                   1,      11,     14,     KdSyncNegative,
>      },
>      
> +    {   240, 320,    58,     191828,
> +                 22,     11,     32,     KdSyncNegative,
> +                 1,      5,      2,      KdSyncNegative,
> +    },
> +
> ******
> This only covers the Phytec 240x320 portrait display. Not the EA display..
> 
> And this tweak reduces the check limits in the AMBA clcd driver on the
> single failed check. The default checks don't quite match what the hardware
> can do.
> ******
> diff -Naur linux-2.6.34/include/linux/amba/clcd.h 
> linux-2.6.34-new/include/linux/amba/clcd.h
> --- linux-2.6.34/include/linux/amba/clcd.h    2010-08-12 16:42:47.816919172 
> -0700
> +++ linux-2.6.34-new/include/linux/amba/clcd.h        2010-08-12 
> 16:35:36.857731747 -0700
> @@ -238,7 +238,7 @@
>  #define CHECK(e,l,h) (var->e < l || var->e > h)
>       if (CHECK(right_margin, (5+1), 256) ||  /* back porch */
>           CHECK(left_margin, (5+1), 256) ||   /* front porch */
> -         CHECK(hsync_len, (5+1), 256) ||
> +         CHECK(hsync_len, (5+0), 256) ||
>           var->xres > 4096 ||
>           var->lower_margin > 255 ||          /* back porch */
>           var->upper_margin > 255 ||          /* front porch */
> ******
> 
> Rebuild everything and run the following command the start X:
>       Xfbdev -screen 240x320x16x58 -mouse mouse -keybd keyboard
>       export DISPLAY=localhost:0.0
> 
> Good luck,
> Kevin
> 
>> Subject: Re: [Ltib] How to start X.
>>
>> Hi Mario,
>>
>> You can ignore the inet6 errors, it means your kernel does not have ipv6
>> support (I think).
>>
>> I don't know what the other error is.  Can someone else with that type
>> of board (PHYTEC LPC3250) reply if they have any ideas.
>>
>> Regards, Stuart
>>
>> Mário Henrique de Oliveira Carneiro wrote:
>>> Hello Stuart,
>>> thanks for responding.
>>> Once I can compile the X11, can not start X.
>>> I'm giving up.
>>> Would you have any ideas? See what happens:
>>>
>>> address@hidden /]# startx
>>> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
>>> _XSERVTransOpen: transport open failed for inet6/nxp:0
>>> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
>>> Warning: mode not found, using default
>>> error: Invalid argument
>>>
>>> Fatal server error:
>>> no screens found
>>> twm:  unable to open display ":0"
>>> killall: Xfbdev: no process killed
>>>
>>> Regards, Mário
>>>
>>> Em 11 de agosto de 2010 15:19, Stuart Hughes <address@hidden
>>> <mailto:address@hidden>> escreveu:
>>>
>>>     Hi Mario,
>>>
>>>     Yes X has been built/run on LTIB.  I've not tried on that particular
>>>     platform, but it should be okay.
>>>
>>>     I would expect the defaults for that platform to work?
>>>
>>>     Anyhow, make sure your kernel has frame buffer support enabled (it
>>>     should have).  Someone else with that platform needs to confirm whether
>>>     qtopia2 should work in its default config.
>>>
>>>     Also, please include output of what you tried on the target and any
>>>     output back (for example startx or anything else)
>>>
>>>     Regards, Stuart
>>>
>>>     Mário Henrique de Oliveira Carneiro wrote:
>>>     > Hello everybody,
>>>     > someone could tell me how to compile the kernel to start the graphical
>>>     > interface.
>>>     > I compiled with Qtopia 2 and not getting any results and when I try to
>>>     > Qtopia 4.6 presents error on fontconfig build.
>>>     > Someone already managed to install any distribution with X?
>>>     > My kit is the PHYTEC LPC3250. NXP processor.
>>>     > Please help me.
>>>     >
>>>     > Regards,
>>>     >
>>>     > Mário
>>>     >
>>>
>>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]