List Info

Thread: DirectFB on PS3Linux
DirectFB on PS3Linux
user name
 2007-04-09 11:12:30 

  


  

    
Hi All:

   I've  built DirectFB on FC5 running on PS3. Now there's no problem
to direct DFB app to X11 or SDL output. But the crash was immediately
occurred if set back to FBDev output,even invoking simple "dfbinfo". 
Here's the error log (I added some simple log marked as red):




.....




(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;         init_devices( 0x10017388 )

(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'WM97xx Touchscreen
Driver'...

(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'SonyPI Jogdial
Driver'...


(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'PenMount 9509'...


(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'MuTouch'...

(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'Serial Mouse
Driver'...

(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> probing 'PS/2 Mouse
Driver'...

(-) [Main Thread       0.790] (13349)
Core/Input:    ;           ;           -> 1 available device(s)

provided by 'PS/2 Mouse Driver'.


(*) open number:0,/dev/input/mice input mouse

(*) mouse: PS2_IMPS2

(-) [PS/2 Input ;       0.840] (13353) Direct/Signals:   ; Blocking all
signals from now on!

(*) Start read mouse data

(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349)
Core/Input:    ;           ;           ;  make_id( 0x01 )

(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)

(-) [Main Thread       0.840] (13349)
Core/Input:    ;           ;           ;  input_add_device( 0x1001e9d0 )

(-) [Main Thread       0.840] (13349)
Core/Input:    ;           ;           -> probing 'LIRC Driver'...

(-) [Main Thread       0.840] (13349)
Core/Input:    ;           ;           -> probing 'Linux Input
Driver'...

(*) Linux Input: Driver_get_available Enter

(*) get input device info

(*) get_device_info call

(*) get_device_info enter

(*) Get deviceell Dell USB Mouse

(*) test_bit evbit

(*) touchpad:0

(*) get_device_info leave

(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid
address) <--

(-) [13349: -STACK- ]

  #0  0x0f69bbd0 in signal_handler () from
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]

  #1  0x0f1bdce0 in driver_get_available () from
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so

[0xf1b9000]

  #2  0x0ff5f060 in init_devices () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #3  0x0ff5f5c0 in dfb_input_initialize () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #4  0x0ff52740 in dfb_core_part_initialize () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #5  0x0ff51d80 in dfb_core_initialize () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #6  0x0ff52000 in dfb_core_arena_initialize () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #7  0x0f6d3700 in fusion_arena_enter () from
/usr/local/lib/libfusion-1.0.so.0 [0xf6cf000]

  #8  0x0ff515c0 in dfb_core_create () from
/usr/local/lib/libdirectfb-1.0.so.0 [0xfeed000]

  #9  0x10002a30 in DirectFBCreate () from df_window [0x10000000]

(-) [13352: -STACK- 'VT Switcher']

  #0  0x0f27af20 in vt_thread () from
/usr/local/lib/directfb-1.0-0/systems/libdirectfb_fbdev.so [0xf270000]



(-) [13353: -STACK- 'PS/2 Input']

  #0  0x0f172d50 in ps2mouseEventThread () from
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_ps2mouse.so
[0xf170000]




(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.209] (13349)
DirectFB/Core: &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; dfb_core_destroy...


(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.209] (13349)
Direct/Signals: &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  Removing handler 0xff50ed0

for signal -1 with context 0x10017388...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.209] (13349)
DirectFB/Core: &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp; Shutting down...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.209] (13349)
Core/Parts:&nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  Going to shutdown
'system' core...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.210] (13349)
FBDev/VT:&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; dfb_vt_shutdown()

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.210] (13349)
Direct/Thread: &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  Canceling 13352.

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.253] (13349)
FBDev/VT:&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; -> switching

back...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.253] (13349)
FBDev/VT:&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; -> switched
back...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.297] (13349)
FBDev/VT:&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; vt_set_fb( 8, 0 )

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.316] (13349)
Core/Parts:&nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  Going to shutdown
'colorhash' core...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.316] (13349)
Core/Parts:&nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  Going to shutdown
'clipboard' core...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.316] (13349)
Direct/Main:  ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; direct_shutdown() called...

(-) [Main Thread&nbsp; &nbsp; &nbsp;  1.316] (13349)
Direct/Main:  ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; ...1 references left.

Aborted



  ; &nbsp; The crash happened when get_device_info got returned. I guess
,also doubt that there's anything to do with the gcc on PS3Linux.&nbsp;
Anyone knows this issue ? &nbsp; I use DirectFB-1.0.0.RC4





Cheers

Sakur



  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-09 05:04:03
  


  

    
Sakur schrieb:
> Hi All:
>    I've  built DirectFB on FC5 running on PS3. Now
there's no problem to 
> direct DFB app to X11 or SDL output. But the crash was
immediately 
> occurred if set back to FBDev output,even invoking
simple "dfbinfo".  
> Here's the error log (I added some simple log marked as
red):
> 
> .....
> 
> (-) [Main Thread       0.790] (13349) Core/Input:      
                 
> init_devices( 0x10017388 )
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'WM97xx Touchscreen 
> Driver'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'SonyPI Jogdial Driver'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'PenMount 9509'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'MuTouch'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'Serial Mouse Driver'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> probing
'PS/2 Mouse Driver'...
> (-) [Main Thread       0.790] (13349) 
> Core/Input:                          -> 1 available
device(s) provided 
> by 'PS/2 Mouse Driver'.
> (*) open number:0,/dev/input/mice input mouse
> (*) mouse: PS2_IMPS2
> (-) [PS/2 Input        0.840] (13353) Direct/Signals:  
 Blocking all 
> signals from now on!
> (*) Start read mouse data
> (*) Direct/Thread: Running 'PS/2 Input' (INPUT,
13353)...
> (-) [Main Thread       0.840] (13349) 
> Core/Input:                            make_id( 0x01 )
> (*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
> (-) [Main Thread       0.840] (13349) 
> Core/Input:                           
input_add_device( 0x1001e9d0 )
> (-) [Main Thread       0.840] (13349) 
> Core/Input:                          -> probing
'LIRC Driver'...
> (-) [Main Thread       0.840] (13349) 
> Core/Input:                          -> probing
'Linux Input Driver'...
> (*) Linux Input: Driver_get_available Enter
> (*) get input device info
> (*) get_device_info call
> (*) get_device_info enter
> (*) Get deviceell Dell
USB Mouse
> (*) test_bit evbit
> (*) touchpad:0
> (*) get_device_info leave
> (!) [13349:    0.840] --> Caught signal 11 (at
(nil), invalid address) <--
> (-) [13349: -STACK- ]
>   #0  0x0f69bbd0 in signal_handler () from 
> /usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
>   #1  0x0f1bdce0 in driver_get_available () from 
>
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux
_input.so 
> [0xf1b9000]

               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

-- 
Best regards,
  Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/
                |
"------------------------------------------"

_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-09 13:42:43
  


  

    

  


  

    
Denis Oliver Kropp wrote:

directfb.org" type="cite">
  
Sakur schrieb:
  

  

    
Hi All:
   I've  built DirectFB on FC5 running on PS3. Now there's no problem to 
direct DFB app to X11 or SDL output. But the crash was immediately 
occurred if set back to FBDev output,even invoking simple "dfbinfo".  
Here's the error log (I added some simple log marked as red):

.....

(-) [Main Thread       0.790] (13349) Core/Input:                        
init_devices( 0x10017388 )
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'WM97xx Touchscreen 
Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'SonyPI Jogdial Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PenMount 9509'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'MuTouch'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'Serial Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PS/2 Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> 1 available device(s) provided 
by 'PS/2 Mouse Driver'.
(*) open number:0,/dev/input/mice input mouse
(*) mouse: PS2_IMPS2

(-) [PS/2 Input        0.840] (13353) Direct/Signals:    Blocking all 
signals from now on!
(*) Start read mouse data
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349) 
Core/Input:                            make_id( 0x01 )
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(-) [Main Thread       0.840] (13349) 
Core/Input:                            input_add_device( 0x1001e9d0 )
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'LIRC Driver'...
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'Linux Input Driver'...
(*) Linux Input: Driver_get_available Enter
(*) get input device info
(*) get_device_info call
(*) get_device_info enter
(*) Get deviceell Dell USB Mouse
(*) test_bit evbit
(*) touchpad:0
(*) get_device_info leave
(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid address) <--
(-) [13349: -STACK- ]
  #0  0x0f69bbd0 in signal_handler () from 
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
  #1  0x0f1bdce0 in driver_get_available () from 
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so 
[0xf1b9000]
    

  

  

               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

  



Hi,Denis:

&nbsp;  I've traced at the crashed point. The crash happened when
"get_device_info" function returned.&nbsp; Seemed the return address was
invalid.Even I put a log right after get_device_info call. No any
output  got shown after "get_device_info".

  ; Also,I removed some maybe unsupported CFLAGS to build. The crash
still occurred at the same point. I believe PS3Linux gcc will generate
32-bit mode objects (Actually just similar as gcc for PowerPC).So what
might be the cause?



Br

Sakur 

 &nbsp; 

 &nbsp; 


  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-09 09:56:13
  


  

    
Sakur schrieb:
> Denis Oliver Kropp wrote:
>> Sakur schrieb:
>>   
>>> Hi All:
>>>    I've  built DirectFB on FC5 running on PS3.
Now there's no problem to 
>>> direct DFB app to X11 or SDL output. But the
crash was immediately 
>>> occurred if set back to FBDev output,even
invoking simple "dfbinfo".  
>>> Here's the error log (I added some simple log
marked as red):
>>>
>>> .....
>>>
>>> (-) [Main Thread       0.790] (13349)
Core/Input:                        
>>> init_devices( 0x10017388 )
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'WM97xx Touchscreen 
>>> Driver'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'SonyPI Jogdial Driver'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'PenMount 9509'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'MuTouch'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'Serial Mouse Driver'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          ->
probing 'PS/2 Mouse Driver'...
>>> (-) [Main Thread       0.790] (13349) 
>>> Core/Input:                          -> 1
available device(s) provided 
>>> by 'PS/2 Mouse Driver'.
>>> (*) open number:0,/dev/input/mice input mouse
>>> (*) mouse: PS2_IMPS2
>>> (-) [PS/2 Input        0.840] (13353)
Direct/Signals:    Blocking all 
>>> signals from now on!
>>> (*) Start read mouse data
>>> (*) Direct/Thread: Running 'PS/2 Input' (INPUT,
13353)...
>>> (-) [Main Thread       0.840] (13349) 
>>> Core/Input:                            make_id(
0x01 )
>>> (*) DirectFB/Input: IMPS/2 Mouse 1.0
(directfb.org)
>>> (-) [Main Thread       0.840] (13349) 
>>> Core/Input:                           
input_add_device( 0x1001e9d0 )
>>> (-) [Main Thread       0.840] (13349) 
>>> Core/Input:                          ->
probing 'LIRC Driver'...
>>> (-) [Main Thread       0.840] (13349) 
>>> Core/Input:                          ->
probing 'Linux Input Driver'...
>>> (*) Linux Input: Driver_get_available Enter
>>> (*) get input device info
>>> (*) get_device_info call
>>> (*) get_device_info enter
>>> (*) Get deviceell Dell
USB Mouse
>>> (*) test_bit evbit
>>> (*) touchpad:0
>>> (*) get_device_info leave
>>> (!) [13349:    0.840] --> Caught signal 11
(at (nil), invalid address) <--
>>> (-) [13349: -STACK- ]
>>>   #0  0x0f69bbd0 in signal_handler () from 
>>> /usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
>>>   #1  0x0f1bdce0 in driver_get_available ()
from 
>>>
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux
_input.so 
>>> [0xf1b9000]
>>>     
>>
>>                get_device_info( fd, &info );
>>
>>                ioctl( fd, EVIOCGRAB, 0 );
>>                close( fd );
>>
>>                if
(!dfb_config->linux_input_ir_only ||
>>                    (info.desc.type &
DIDTF_REMOTE))
>>                     device_nums[num_devices++] =
i;
>>
>> It could only be that dfb_config is NULL. That is
when
>> dfb_config_init() was not called (by
DirectFBInit()).
>>
>> But DirectFBCreate() checks that.
>>
>>   
> Hi,Denis:
>    I've traced at the crashed point. The crash happened
when 
> "get_device_info" function returned.  Seemed
the return address was 
> invalid.Even I put a log right after get_device_info
call. No any 
> output  got shown after "get_device_info".
>    Also,I removed some maybe unsupported CFLAGS to
build. The crash 
> still occurred at the same point. I believe PS3Linux
gcc will generate 
> 32-bit mode objects (Actually just similar as gcc for
PowerPC).So what 
> might be the cause?

     unsigned int  num_keys     = 0;
     unsigned int  num_ext_keys = 0;
     unsigned int  num_buttons  = 0;
     unsigned int  num_rels     = 0;
     unsigned int  num_abs      = 0;

     unsigned long evbit[NBITS(EV_MAX)];
     unsigned long keybit[NBITS(KEY_MAX)];
     unsigned long relbit[NBITS(REL_MAX)];
     unsigned long absbit[NBITS(ABS_MAX)];


I thought it could be that the stack limit is too low, but
these local variables would occupy only about 100 bytes.

-- 
Best regards,
  Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/
                |
"------------------------------------------"

_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-10 06:23:07
  


  

    

  


  

    
Denis Oliver Kropp wrote:

directfb.org" type="cite">
  
Sakur schrieb:
  

  

    
Denis Oliver Kropp wrote:
    

    

      
Sakur schrieb:
  
      

      

        
Hi All:
   I've  built DirectFB on FC5 running on PS3. Now there's no problem to 
direct DFB app to X11 or SDL output. But the crash was immediately 
occurred if set back to FBDev output,even invoking simple "dfbinfo".  
Here's the error log (I added some simple log marked as red):

.....

(-) [Main Thread       0.790] (13349) Core/Input:                        
init_devices( 0x10017388 )
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'WM97xx Touchscreen 
Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'SonyPI Jogdial Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PenMount 9509'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'MuTouch'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'Serial Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PS/2 Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> 1 available device(s) provided 
by 'PS/2 Mouse Driver'.
(*) open number:0,/dev/input/mice input mouse
(*) mouse: PS2_IMPS2

(-) [PS/2 Input        0.840] (13353) Direct/Signals:    Blocking all 
signals from now on!
(*) Start read mouse data
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349) 
Core/Input:                            make_id( 0x01 )
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(-) [Main Thread       0.840] (13349) 
Core/Input:                            input_add_device( 0x1001e9d0 )
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'LIRC Driver'...
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'Linux Input Driver'...
(*) Linux Input: Driver_get_available Enter
(*) get input device info
(*) get_device_info call
(*) get_device_info enter
(*) Get deviceell Dell USB Mouse
(*) test_bit evbit
(*) touchpad:0
(*) get_device_info leave
(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid address) <--
(-) [13349: -STACK- ]
  #0  0x0f69bbd0 in signal_handler () from 
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
  #1  0x0f1bdce0 in driver_get_available () from 
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so 
[0xf1b9000]
    
        

      

      
               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

  
      

    

    
Hi,Denis:

   I've traced at the crashed point. The crash happened when 
"get_device_info" function returned.  Seemed the return address was 
invalid.Even I put a log right after get_device_info call. No any 
output  got shown after "get_device_info".
   Also,I removed some maybe unsupported CFLAGS to build. The crash 
still occurred at the same point. I believe PS3Linux gcc will generate 
32-bit mode objects (Actually just similar as gcc for PowerPC).So what 
might be the cause?
    

  

  

     unsigned int  num_keys     = 0;
     unsigned int  num_ext_keys = 0;
     unsigned int  num_buttons  = 0;
     unsigned int  num_rels     = 0;
     unsigned int  num_abs      = 0;

     unsigned long evbit[NBITS(EV_MAX)];
     unsigned long keybit[NBITS(KEY_MAX)];
     unsigned long relbit[NBITS(REL_MAX)];
     unsigned long absbit[NBITS(ABS_MAX)];


I thought it could be that the stack limit is too low, but
these local variables would occupy only about 100 bytes.

  



Hi,Denis:

&nbsp;  I found the crash was related with "test_bits" Macro. If the
"get_device_info" function body contains "test_bits" Macro, the program
would crash as I reported ,but if not ,the call is absolutely OK! 

However,this macro seemed doing not invalid memory operation . What's
your opinion ? Thanks



Sakur   

 &nbsp; 


  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-10 07:00:48
  


  

    

  


  

    
Denis Oliver Kropp wrote:

directfb.org" type="cite">
  
Sakur schrieb:
  

  

    
Denis Oliver Kropp wrote:
    

    

      
Sakur schrieb:
  
      

      

        
Hi All:
   I've  built DirectFB on FC5 running on PS3. Now there's no problem to 
direct DFB app to X11 or SDL output. But the crash was immediately 
occurred if set back to FBDev output,even invoking simple "dfbinfo".  
Here's the error log (I added some simple log marked as red):

.....

(-) [Main Thread       0.790] (13349) Core/Input:                        
init_devices( 0x10017388 )
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'WM97xx Touchscreen 
Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'SonyPI Jogdial Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PenMount 9509'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'MuTouch'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'Serial Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PS/2 Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> 1 available device(s) provided 
by 'PS/2 Mouse Driver'.
(*) open number:0,/dev/input/mice input mouse
(*) mouse: PS2_IMPS2

(-) [PS/2 Input        0.840] (13353) Direct/Signals:    Blocking all 
signals from now on!
(*) Start read mouse data
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349) 
Core/Input:                            make_id( 0x01 )
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(-) [Main Thread       0.840] (13349) 
Core/Input:                            input_add_device( 0x1001e9d0 )
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'LIRC Driver'...
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'Linux Input Driver'...
(*) Linux Input: Driver_get_available Enter
(*) get input device info
(*) get_device_info call
(*) get_device_info enter
(*) Get deviceell Dell USB Mouse
(*) test_bit evbit
(*) touchpad:0
(*) get_device_info leave
(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid address) <--
(-) [13349: -STACK- ]
  #0  0x0f69bbd0 in signal_handler () from 
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
  #1  0x0f1bdce0 in driver_get_available () from 
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so 
[0xf1b9000]
    
        

      

      
               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

  
      

    

    
Hi,Denis:

   I've traced at the crashed point. The crash happened when 
"get_device_info" function returned.  Seemed the return address was 
invalid.Even I put a log right after get_device_info call. No any 
output  got shown after "get_device_info".
   Also,I removed some maybe unsupported CFLAGS to build. The crash 
still occurred at the same point. I believe PS3Linux gcc will generate 
32-bit mode objects (Actually just similar as gcc for PowerPC).So what 
might be the cause?
    

  

  

     unsigned int  num_keys     = 0;
     unsigned int  num_ext_keys = 0;
     unsigned int  num_buttons  = 0;
     unsigned int  num_rels     = 0;
     unsigned int  num_abs      = 0;

     unsigned long evbit[NBITS(EV_MAX)];
     unsigned long keybit[NBITS(KEY_MAX)];
     unsigned long relbit[NBITS(REL_MAX)];
     unsigned long absbit[NBITS(ABS_MAX)];


I thought it could be that the stack limit is too low, but
these local variables would occupy only about 100 bytes.

  



Hi:

  Sorry, I ignored another key point which I confirmed causing the
crash after further investigation.

&nbsp; 



&nbsp; ioctl(fd,EVIOCGBIT(0,EV_MAX),evbit)



&nbsp; The return value for this call is "31" == EMLINK. 



&nbsp; 



  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux
  


  

     user name

     2007-04-10 08:05:32
  


  

    

  


  

    
Sakur wrote:

gmail.com" type="cite">
  
Denis Oliver Kropp wrote:
  
directfb.org" type="cite">
    
Sakur schrieb:
  

    

      
Denis Oliver Kropp wrote:
    

      

        
Sakur schrieb:
  
      

        

          
Hi All:
   I've  built DirectFB on FC5 running on PS3. Now there's no problem to 
direct DFB app to X11 or SDL output. But the crash was immediately 
occurred if set back to FBDev output,even invoking simple "dfbinfo".  
Here's the error log (I added some simple log marked as red):

.....

(-) [Main Thread       0.790] (13349) Core/Input:                        
init_devices( 0x10017388 )
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'WM97xx Touchscreen 
Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'SonyPI Jogdial Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PenMount 9509'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'MuTouch'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'Serial Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PS/2 Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> 1 available device(s) provided 
by 'PS/2 Mouse Driver'.
(*) open number:0,/dev/input/mice input mouse
(*) mouse: PS2_IMPS2

(-) [PS/2 Input        0.840] (13353) Direct/Signals:    Blocking all 
signals from now on!
(*) Start read mouse data
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349) 
Core/Input:                            make_id( 0x01 )
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(-) [Main Thread       0.840] (13349) 
Core/Input:                            input_add_device( 0x1001e9d0 )
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'LIRC Driver'...
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'Linux Input Driver'...
(*) Linux Input: Driver_get_available Enter
(*) get input device info
(*) get_device_info call
(*) get_device_info enter
(*) Get deviceell Dell USB Mouse
(*) test_bit evbit
(*) touchpad:0
(*) get_device_info leave
(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid address) <--
(-) [13349: -STACK- ]
  #0  0x0f69bbd0 in signal_handler () from 
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
  #1  0x0f1bdce0 in driver_get_available () from 
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so 
[0xf1b9000]
    
        

        

        
               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

  
      

      

      
Hi,Denis:

   I've traced at the crashed point. The crash happened when 
"get_device_info" function returned.  Seemed the return address was 
invalid.Even I put a log right after get_device_info call. No any 
output  got shown after "get_device_info".
   Also,I removed some maybe unsupported CFLAGS to build. The crash 
still occurred at the same point. I believe PS3Linux gcc will generate 
32-bit mode objects (Actually just similar as gcc for PowerPC).So what 
might be the cause?
    

    

    

     unsigned int  num_keys     = 0;
     unsigned int  num_ext_keys = 0;
     unsigned int  num_buttons  = 0;
     unsigned int  num_rels     = 0;
     unsigned int  num_abs      = 0;

     unsigned long evbit[NBITS(EV_MAX)];
     unsigned long keybit[NBITS(KEY_MAX)];
     unsigned long relbit[NBITS(REL_MAX)];
     unsigned long absbit[NBITS(ABS_MAX)];


I thought it could be that the stack limit is too low, but
these local variables would occupy only about 100 bytes.

  

  

Hi:

&nbsp; Sorry, I ignored another key point which I confirmed causing the
crash after further investigation.

&nbsp; 

  

  ioctl(fd,EVIOCGBIT(0,EV_MAX),evbit)

  

  The return value for this call is "31" == EMLINK. 

  

  

  


Sorry:

   ; Return "31" means 31 tytes copied,not EMLINK. But the crash
occurred at this call. ; Any help ? Thanks



Cheers

Sakur


  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 08:47:36
  


  

    

  


  

    
Sakur wrote:

gmail.com" type="cite">
  
Denis Oliver Kropp wrote:
  
directfb.org" type="cite">
    
Sakur schrieb:
  

    

      
Denis Oliver Kropp wrote:
    

      

        
Sakur schrieb:
  
      

        

          
Hi All:
   I've  built DirectFB on FC5 running on PS3. Now there's no problem to 
direct DFB app to X11 or SDL output. But the crash was immediately 
occurred if set back to FBDev output,even invoking simple "dfbinfo".  
Here's the error log (I added some simple log marked as red):

.....

(-) [Main Thread       0.790] (13349) Core/Input:                        
init_devices( 0x10017388 )
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'WM97xx Touchscreen 
Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'SonyPI Jogdial Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PenMount 9509'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'MuTouch'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'Serial Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> probing 'PS/2 Mouse Driver'...
(-) [Main Thread       0.790] (13349) 
Core/Input:                          -> 1 available device(s) provided 
by 'PS/2 Mouse Driver'.
(*) open number:0,/dev/input/mice input mouse
(*) mouse: PS2_IMPS2

(-) [PS/2 Input        0.840] (13353) Direct/Signals:    Blocking all 
signals from now on!
(*) Start read mouse data
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 13353)...

(-) [Main Thread       0.840] (13349) 
Core/Input:                            make_id( 0x01 )
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(-) [Main Thread       0.840] (13349) 
Core/Input:                            input_add_device( 0x1001e9d0 )
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'LIRC Driver'...
(-) [Main Thread       0.840] (13349) 
Core/Input:                          -> probing 'Linux Input Driver'...
(*) Linux Input: Driver_get_available Enter
(*) get input device info
(*) get_device_info call
(*) get_device_info enter
(*) Get deviceell Dell USB Mouse
(*) test_bit evbit
(*) touchpad:0
(*) get_device_info leave
(!) [13349:    0.840] --> Caught signal 11 (at (nil), invalid address) <--
(-) [13349: -STACK- ]
  #0  0x0f69bbd0 in signal_handler () from 
/usr/local/lib/libdirect-1.0.so.0 [0xf68e000]
  #1  0x0f1bdce0 in driver_get_available () from 
/usr/local/lib/directfb-1.0-0/inputdrivers/libdirectfb_linux_input.so 
[0xf1b9000]
    
        

        

        
               get_device_info( fd, &info );

               ioctl( fd, EVIOCGRAB, 0 );
               close( fd );

               if (!dfb_config->linux_input_ir_only ||
                   (info.desc.type & DIDTF_REMOTE))
                    device_nums[num_devices++] = i;

It could only be that dfb_config is NULL. That is when
dfb_config_init() was not called (by DirectFBInit()).

But DirectFBCreate() checks that.

  
      

      

      
Hi,Denis:

   I've traced at the crashed point. The crash happened when 
"get_device_info" function returned.  Seemed the return address was 
invalid.Even I put a log right after get_device_info call. No any 
output  got shown after "get_device_info".
   Also,I removed some maybe unsupported CFLAGS to build. The crash 
still occurred at the same point. I believe PS3Linux gcc will generate 
32-bit mode objects (Actually just similar as gcc for PowerPC).So what 
might be the cause?
    

    

    

     unsigned int  num_keys     = 0;
     unsigned int  num_ext_keys = 0;
     unsigned int  num_buttons  = 0;
     unsigned int  num_rels     = 0;
     unsigned int  num_abs      = 0;

     unsigned long evbit[NBITS(EV_MAX)];
     unsigned long keybit[NBITS(KEY_MAX)];
     unsigned long relbit[NBITS(REL_MAX)];
     unsigned long absbit[NBITS(ABS_MAX)];


I thought it could be that the stack limit is too low, but
these local variables would occupy only about 100 bytes.

  

  

Hi:

&nbsp; Sorry, I ignored another key point which I confirmed causing the
crash after further investigation.

&nbsp; 

  

  ioctl(fd,EVIOCGBIT(0,EV_MAX),evbit)

  

  The return value for this call is "31" == EMLINK. 

  

  

  


Hi, I got the crash reason :

   ; ioctl( fd, EVIOCGBIT(0, EV_MAX), evbit )  ==>&nbsp; the second arg
for EVIOCGBIT macro is bad here,which should be "sizeof(evbit)". This
might cause ; memory overflow (the returned "31" bytes copied into
actual 4 bytes array).&nbsp; But I  am confused&nbsp; why the issue is not
detected on i386. ; Anyway, Thanks for all 



Cheers

Sakur


  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 01:08:25
  


  

    
Sakur schrieb:
> Hi, I got the crash reason :
>     ioctl( fd, EVIOCGBIT(0, EV_MAX), evbit )  ==> 
the second arg for 
> EVIOCGBIT macro is bad here,which should be
"sizeof(evbit)". This might 
> cause  memory overflow (the returned "31"
bytes copied into actual 4 
> bytes array).  But I  am confused  why the issue is not
detected on 
> i386.  Anyway, Thanks for all

Maybe the stack is growing upward on PS3 and it didn't crash
with stacks
growing downward, like i386.

-- 
Best regards,
  Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/
                |
"------------------------------------------"

_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 01:13:43
  


  

    
>  Hi, I got the crash reason :
>      ioctl( fd, EVIOCGBIT(0, EV_MAX), evbit )  ==> 
the second arg for
> EVIOCGBIT macro is bad here,which should be
"sizeof(evbit)". This might
> cause  memory overflow (the returned "31"
bytes copied into actual 4 bytes
> array).  But I  am confused  why the issue is not
detected on i386.  Anyway,

This looks like a good catch.  I guess the i386 driver isn't
writing
beyond the end of the bits or the order of memory use on the
stack is
different enough to avoid this being a problem.

_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 10:29:06
  


  

    
Ben Combee wrote:
>>  Hi, I got the crash reason :
>>      ioctl( fd, EVIOCGBIT(0, EV_MAX), evbit ) 
==>  the second arg for
>> EVIOCGBIT macro is bad here,which should be
"sizeof(evbit)". This might
>> cause  memory overflow (the returned "31"
bytes copied into actual 4 
>> bytes
>> array).  But I  am confused  why the issue is not
detected on i386.  
>> Anyway,
>
> This looks like a good catch.  I guess the i386 driver
isn't writing
> beyond the end of the bits or the order of memory use
on the stack is
> different enough to avoid this being a problem.
>
   Actually, the stack on PS3Linux  is growing  downward as
on i386.  
The 32-bit mode program  uses SYS V ABI  for PowerPC,while 
64-bit mode  
program uses  IBM OpenAIX ABI. Maybe the PS3Linux driver
doesn't have a 
write protection mechanism.
   Hereby now, even no crash occurred and sample DFB
application could 
run. But  I just saw from the Sony PS3Linux development
document that 
the frame buffer on PS3 platform has been implemented as
virtual frame 
buffer allocated on main memory. see:
   
http://www.louiscandell.com/ps3/doc/Ap
plicationProgrammingEnvironment.html
   So does this mean that I still need do some port work
specific to PS3 
Vitual FB following  the provided programming procedures? 
Any suggest? 

Cheers
Sakur

_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 03:48:31
  


  

    
> http://www.louiscandell.com/ps3/doc/Ap
plicationProgrammingEnvironment.html
>    So does this mean that I still need do some port
work specific to PS3 
> Vitual FB following  the provided programming
procedures?  Any suggest? 
>   
They did some weird stuff to hide the hardware from beeing
exploited.
basically single buffer mode should be transparent to the
user, and
might not require changes to DirectFB.

In double buffer mode you have to use some special IOCTL for
flipping.
We use FBIOPAN_DISPLAY, they use PS3FB_IOCTL_FSEL.

Why dont you just try what happens? /dev/fb0 should be
already there ;)


andi


_______________________________________________
directfb-dev mailing list
directfb-devdirectfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/
directfb-dev



  


  

    
  

  
  
   
     
    

  

    Re:  DirectFB on PS3Linux (Fixed it Now)
  


  

     user name

     2007-04-10 13:00:41
  


  

    

  


  

    
Andreas wrote:

fischlustig.de" type="cite">
  

    
http://www.louiscandell.com/ps3/doc/ApplicationProgrammingEnvironment.html

   So does this mean that I still need do some port work specific to PS3 
Vitual FB following  the provided programming procedures?  Any suggest? 
  
    

  

  
They did some weird stuff to hide the hardware from beeing exploited.
basically single buffer mode should be transparent to the user, and
might not require changes to DirectFB.


In double buffer mode you have to use some special IOCTL for flipping.

We use FBIOPAN_DISPLAY, they use PS3FB_IOCTL_FSEL.

Why dont you just try what happens? /dev/fb0 should be already there ;)


andi


  



hi,

 &nbsp; Thanks for your help.

&nbsp;  Actually,I've tried already. I used 1080i ; YUV60HZ&nbsp; video mode. ; 

 &nbsp; I'll do further test. Thank you very much! 



Sakur


  

  
  
   
     
    






 [1-13]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )