GPIO status

Kernel development related

Re: GPIO status

Postby Dopi » Thu Feb 10, 2011 5:48 pm

sploutch wrote:
Jose_Paramore wrote:How did you changed the brightness settings? I can't do this :S

I use the Jetplatform0.3pre1
kernel : latest experimental-2.6.29-dopi

Put JetDroid in sleep mode, then wake up him, go to the settings and adjust the brightness

I also can't change it although I shoule have the same setup as you. There must be something special about your system ;) We need to narrow down what it is. Changing brightness would be brilliant.

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Advertisement

       

Re: GPIO status

Postby MadRocker » Fri Feb 11, 2011 12:10 am

Think he has the 4feb or 5feb init.rc in there and possibly the 29Jan kernel or 1Feb kernel, same with 1Feb kernel bundle + 8feb video patch.
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am

Re: GPIO status

Postby Dopi » Fri Feb 11, 2011 5:48 pm

MadRocker wrote:Think he has the 4feb or 5feb init.rc in there and possibly the 29Jan kernel or 1Feb kernel, same with 1Feb kernel bundle + 8feb video patch.

Do you mean the difference is related to different init.rc versions? We should be able to test if changing the init.rc makes a difference.

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby MadRocker » Fri Feb 11, 2011 8:04 pm

Possibly the init.rc is helping with the brightness working or activating the modules something that was active but not able to work as some part was not called.

That 2 versions is about where I started to see the brightness and have not tracked it back to older versions / where it gets lost to find what is causing it to work, it could be the kernel or module or init.rc or a .conf file or a combination. I have suspected even a ../lib file helping with his so far.

Untested:
Some other init.rc's I looked at has this for gpio, it might be usefull:
Code: Select all
    # acquire gpio for GSM modem
    chown radio system /dev/s3c_serial0
    chmod 0777 /dev/s3c_serial0
    write /sys/class/gpio/export 2
    write /sys/class/gpio/export 3
    write /sys/class/gpio/export 30
    write /sys/class/gpio/export 141
    write /sys/class/gpio/gpio2/direction in
    write /sys/class/gpio/gpio3/direction out
    write /sys/class/gpio/gpio30/direction out
    write /sys/class/gpio/gpio141/direction out
    chmod 0777 /sys/class/gpio/gpio2/value
    chmod 0777 /sys/class/gpio/gpio3/value
    chmod 0777 /sys/class/gpio/gpio30/value
    chmod 0777 /sys/class/gpio/gpio141/value
    mkdir /data/ppp 0777 system system


PMEM:
Code: Select all
    chmod 664 system/usr/keychars/qwerty.kcm.bin               
    chmod 777       /dev/video0
    chmod 777       /dev/video1         
    chmod 777       /dev/video14           
    chmod 777       /dev/graphics/fb0
    chmod 777       /dev/graphics/fb1
    chmod 777       /dev/graphics/fb2
    chmod 777       /dev/graphics/fb3
    chmod 777       /dev/graphics/fb4                     
    chmod 777       /dev/s3c-cmm                                           
    chmod 777       /dev/s3c-g2d                                           
    chmod 777       /dev/s3c-g3d                                           
    chmod 777       /dev/s3c-jpg                                           
    chmod 777       /dev/s3c-mem                                           
    chmod 777       /dev/s3c-mfc                                           
    chmod 777       /dev/s3c-pp                                             
    chmod 777       /dev/s3c-rotator                                       
    chmod 777       /dev/s3c_serial0                   
    chmod 777       /dev/s3c_serial1                   
    chmod 777       /dev/s3c_serial2               
    chmod 777       /dev/s3c_serial3
    chmod 777       /dev/controlC0
    chmod 777       /dev/pcmC0D0c
    chmod 777       /dev/pcmC0D0p
    chmod 777       /dev/dsp
    chmod 777       /dev/pmem
    chmod 777       /dev/pmem_picture
    chmod 777       /dev/pmem_render
    chmod 777       /dev/pmem_jpeg
    chmod 777       /dev/pmem_preview
    chmod 777       /dev/lis302dl


PS> I am going to spend more time on the 2.6.3* kernel as I see tom3q is also porting the 2.6.35 so we should be able to combine forces with him on this.
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am

Re: GPIO status

Postby MadRocker » Mon Feb 14, 2011 3:11 am

Not sure if anyone can use this for the GSM.
This could likely happen in Froyo and eclair as well, did not check them yet.
I noticed in Froyo that my time was corrected on each boot even though my wifi was not connected.
Kernel + modules 1Feb.

Android.log JetGinger 2.3.3
GSM:
Code: Select all
D/CallManager( 1881): registerPhone(GSM Handler{4055ee70})
D/CallManager( 1919): registerPhone(GSM Handler{4055eb48})
D/CallManager( 1887): registerPhone(GSM Handler{4055e718})
I/GsmServiceStateTracker( 1887): Auto time state changed


GPRS ?
Code: Select all
I/TelephonyRegistry( 1850): notifyServiceState: 1 home null null null  Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 1850): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=radioTurnedOff interfaceName=null networkType=0
I/TelephonyRegistry( 1850): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=gprsDetached interfaceName=null networkType=0
MadRocker
Dev Team
Dev Team
 
Posts: 528
Joined: Sun Dec 12, 2010 7:15 am

Previous

Return to JetKernel

Who is online

Users browsing this forum: No registered users and 1 guest

  • Advertisement
cron