**** BEGIN LOGGING AT Sat Oct 31 02:59:57 2009
Oct 31 04:44:20 <Psi> i dont think gta01 is actually using the timing values from fb.modes
Oct 31 04:44:43 <Psi> even if i change the clock alot there is no visible effect on the lcd
Oct 31 04:45:15 <UndrWater1> how about mplayer?
Oct 31 04:45:32 <Psi> does mplayer change the lcd res automatically?
Oct 31 04:46:17 <UndrWater1> it will use the fb.modes to play at the specified res if you tell it to in mplayer.conf
Oct 31 04:47:28 * Psi looks up what the settings are
Oct 31 04:47:40 <UndrWater1> i'm talking vids of course ;)
Oct 31 04:48:04 <Psi> ya, i have a 240x320 vid, but it plays in mplayer at 480x640
Oct 31 04:48:20 <Psi> as a 240x320 picture with black boarders
Oct 31 04:49:01 <UndrWater1> mplayer -vo fbdev -fbmode qvga
Oct 31 04:49:23 <UndrWater1> should be full screen
Oct 31 04:49:32 * Psi tries
Oct 31 04:49:33 <UndrWater1> with the appropriate fb.modes 
Oct 31 04:52:05 <UndrWater1> that also assumes "qvga" is a modeline in that file :)
Oct 31 04:52:13 <Psi> heres what i go http://pastebin.com/m30cdb6b6
Oct 31 04:52:16 <Psi> *got
Oct 31 04:52:39 <Psi> there is a qvga line in fb.modes
Oct 31 04:52:44 <Psi> if thats what you mean
Oct 31 04:53:06 <UndrWater1> is it a section?
Oct 31 04:53:22 <UndrWater1> try:
Oct 31 04:53:44 <Psi> http://pastebin.com/m10afd4ec
Oct 31 04:53:49 <Psi> thats what my fb.modes is
Oct 31 04:53:58 <Psi> its the default one shr unstable comes with
Oct 31 04:54:10 <UndrWater1> mplayer -vm fbdev -fbmode qvga
Oct 31 04:54:10 <Psi> for gta01 atleast
Oct 31 04:54:11 <UndrWater1> right
Oct 31 04:54:16 <UndrWater1> good...that's correct
Oct 31 04:54:33 <UndrWater1> so try -vm instead of -vo
Oct 31 04:54:45 * Psi tries
Oct 31 04:55:29 <Psi> plays at 480x640 with black borders
Oct 31 04:56:28 <UndrWater1> i think you're right...something is hard coded maybe for vga
Oct 31 04:56:39 <Psi> http://pastebin.com/m525bb63a
Oct 31 04:56:47 <Psi> [VO_XV] It seems there is no Xvideo support for your video card available.
Oct 31 04:58:06 <UndrWater1> are you on shr?
Oct 31 04:58:16 <Psi> shr unstable image from buildhost
Oct 31 04:58:45 <Psi> i suspect its a gta01 issue
Oct 31 04:58:57 <UndrWater1> what's the graphics chip?
Oct 31 04:59:15 <Psi> chipset one, instead of glamo
Oct 31 04:59:40 <UndrWater1> mplayer -vo help
Oct 31 05:00:20 <Psi> http://pastebin.com/m5506479b
Oct 31 05:01:08 <UndrWater1> i doubt you'll get anywhere, but try -vo x11
Oct 31 05:01:40 <Psi> same thing
Oct 31 05:02:27 <UndrWater1> i'm no expert but it looks like the chip can't do the scaling
Oct 31 05:02:56 <Psi> im sure ive had it in 240x320 before, on a really old build, maybe om2007
Oct 31 05:03:38 <Psi> and the display does atleast try to change to 240x320 if i go 'fbset qvga'
Oct 31 05:03:53 <UndrWater1> then what happens?
Oct 31 05:04:10 <Psi> ya get a really messed up desktop, like the clockrate is wrong
Oct 31 05:04:15 <Psi> but it can be random
Oct 31 05:04:29 <Psi> i can take a pic if you want
Oct 31 05:05:02 <UndrWater1> that's ok...
Oct 31 05:05:20 <UndrWater1> i'd follow up on that post
Oct 31 05:05:26 <UndrWater1> or start a new one
Oct 31 05:05:52 <Psi> which one
Oct 31 05:06:06 <Psi> the one i did on the mailing list a few days ago
Oct 31 05:06:08 <Tulga> is it possible to change GSM to CDMA?
Oct 31 05:06:49 <UndrWater1> Psi: the coolness of graphics hardware or something like that? or the qvga one?
Oct 31 05:07:33 <UndrWater1> Tulga: have you heard that's possible?
Oct 31 05:07:34 <Psi> i asked for help a few days ago, title was "QVGA 240x320 in GTA01 in SHR"
Oct 31 05:07:47 <Psi> no responce yet
Oct 31 05:07:50 <Tulga> UndrWater1: no, asking first time
Oct 31 05:08:02 <UndrWater1> i think i saw that one...post your experience so far...i think some folks are interested and lurking
Oct 31 05:08:25 <Psi> ok
Oct 31 05:08:29 <Psi> will do, thanks
Oct 31 05:08:41 <Psi> maybe some pics in the email will help
Oct 31 05:08:45 <UndrWater1> Tulga: i've never head that that's possible...and if it were, you'd need to take the phone in to register it
Oct 31 05:08:49 <UndrWater1> yeah
Oct 31 05:10:58 <Psi> the only remotly do'able way i can think of to change a neo from gsm to cdma would be to take it apart, cut away all of the pcb parts needed for GSM (to make room) and then somehow fit the pcb from a CDMA usb dongle (that has working linux voice drivers) inside the phone and wire it up to usb
Oct 31 05:12:17 <Psi> would be pretty hard, but would atleast be possible
Oct 31 09:56:07 <PBeck> hi
Oct 31 09:56:14 <Heinervdm> moin
Oct 31 10:06:50 <PaulFertser> Does anyone in here ride a fixie?
Oct 31 10:06:57 * PaulFertser wished to know how it feels like
Oct 31 10:07:11 * Weiss isn't even quite sure what that question means :o
Oct 31 10:20:42 <PaulFertser> Weiss: a bike without gears and even freewheel whatsoever. Used for track competitions and also by some messengers :)
Oct 31 10:21:17 <SpeedEvil> Also unicyclists
Oct 31 10:51:39 <panicking> hi lindi- :)
Oct 31 10:52:48 <lindi-> panicking: evening
Oct 31 10:54:22 <panicking> lindi-, I think that is possible to work in other frequency range too
Oct 31 10:54:58 <MarcelloB> hello
Oct 31 10:55:17 <MarcelloB> I have some bad blocks on NAND
Oct 31 10:55:28 <MarcelloB> can I Format  all 256 Mb of the NAND ?
Oct 31 10:55:37 <SpeedEvil> Bad blocks are expected.
Oct 31 10:56:01 <SpeedEvil> The spec of the NAND is that after 100000 writes to every block, 256M or over of memory will function.
Oct 31 10:56:10 <MarcelloB> ok but if i reformat all FLASH NAND ?
Oct 31 10:56:16 <PaulFertser> panicking: hey
Oct 31 10:56:28 <SpeedEvil> There start out to be spare blocks, and they are expected to fail in normal use
Oct 31 10:56:38 <SpeedEvil> And be dealt with.
Oct 31 10:57:14 <panicking> PaulFertser, hi
Oct 31 10:57:23 <PaulFertser> MarcelloB: also NAND comes with factory-programmed data about bad blocks, you're supposed to value that info :)
Oct 31 10:57:28 <MarcelloB> ok if I start linux from the SD .. i can format the NAND?
Oct 31 10:58:27 <SpeedEvil> Why do you want to format it?
Oct 31 10:58:29 <PaulFertser> MarcelloB: what are you trying to archive???
Oct 31 10:58:36 <SpeedEvil> Formating doesn't help.
Oct 31 10:59:11 <MarcelloB> I know .. the NAND have some BLOKS from factory yes there is a lot of time thet read on wiki ok but nobody format the NAND? never?
Oct 31 10:59:43 * PaulFertser got so frustrated he can't spell
Oct 31 10:59:59 <PaulFertser> MarcelloB: scrub command in u-boot does that
Oct 31 11:00:21 <SpeedEvil> PaulFertser: you have a really good excuse though.
Oct 31 11:01:16 <MarcelloB> have seriously problems whith flashing now maybe there are tomuch bloks
Oct 31 11:01:20 <MarcelloB> bad
Oct 31 11:01:45 <SpeedEvil> What problems are these causing?
Oct 31 11:02:17 <MarcelloB> i now I reinstall the same stable version of SHR 2009.05 crashed too much times
Oct 31 11:02:42 <MarcelloB> 1 2 3 100 times ever the same problem
Oct 31 11:03:35 * PaulFertser wished MarcelloB expressed his problems in a clearer and more transparent way
Oct 31 11:06:00 <MarcelloB> the bad bloks is a phisical ploblem?
Oct 31 11:06:11 <PaulFertser> MarcelloB: right
Oct 31 11:06:21 <MarcelloB> really?
Oct 31 11:06:23 <PaulFertser> MarcelloB: unless you do tricks to mark bad blocks by mistake
Oct 31 11:06:55 <PaulFertser> MarcelloB: like marking using nandwrite -m without running flasherase_all beforehand.
Oct 31 11:07:37 <SpeedEvil> There really are bad blocks. They should be dealt with appropriately in the normal case.
Oct 31 11:07:43 <SpeedEvil> How is SHR crashing?
Oct 31 11:08:55 <MarcelloB> SHR have problems whith some windows are invisible ... for example the window of logout
Oct 31 11:09:31 <MarcelloB> when push the right button compare a vertical line on center
Oct 31 11:09:46 <MarcelloB> and crashed
Oct 31 11:10:40 <MarcelloB> so then reinstall the image or other image but the problem is the same ... some modules corupted ... or other things
Oct 31 11:11:45 <MarcelloB> but is doungerous format a NAND?
Oct 31 11:12:51 <MarcelloB> if I start the boot image and the sistem from SD? I can try to format nand flash.. ann then reinstall all by flashing?
Oct 31 11:13:12 <PaulFertser> MarcelloB: how many times should we repeat the same thing so you will start describe your problems properly and finally explain why are you talking about bad blocks?
Oct 31 11:13:50 <PaulFertser> meh, bad grammar now, also sounds offensive. /me should better stfu
Oct 31 11:15:44 <PaulFertser> WTF?
Oct 31 11:19:18 <PaulFertser> SpeedEvil: was it too offensive and unhelpful from my side? I thought people coming to irc asking stupid question should expect to be treated a bit tough, no?
Oct 31 11:28:16 <SpeedEvil> I don't think so really
Oct 31 11:29:27 <PaulFertser> Ok, thanks :)
Oct 31 11:30:00 <PaulFertser> Haha, your reply can be considered as an answer to either part of my question which makes it a bit ambigous :)
Oct 31 11:30:29 <SpeedEvil> I don't think you were out of line.
**** ENDING LOGGING AT Sat Oct 31 11:39:06 2009

**** BEGIN LOGGING AT Sat Oct 31 11:39:30 2009
Oct 31 13:17:25 <Guest34298> Hi all. Is there a time line for when SHR-Unstable will be updated?
Oct 31 13:32:16 <Heinervdm> Guest34298: as soon as it isn't segfaulting anymore
Oct 31 15:56:42 <panicking> hi, PaulFertser 
Oct 31 15:58:21 <panicking> I'm trying to cleanup the fiq
Oct 31 15:58:30 <panicking> part but I have few question for you
Oct 31 15:58:48 <panicking> I have rebased all the om-2.6.31 gta02 on the latest linux git repository
Oct 31 15:59:00 <panicking> because I need all the recent feature of linux
Oct 31 15:59:11 <panicking> I have resolved all the compilation issue
Oct 31 16:08:30 <panicking> The timer3 is used by the vibrator and what is its relation with the FIQ code
Oct 31 16:08:31 <panicking> ?
Oct 31 16:08:34 <panicking> do you know?
Oct 31 16:16:29 <CIA-52> freesmartphone.org: 03mickey 07cornucopia * r1cc8bb407238 10/fsogsmd/ (23 files in 8 dirs): fsogsmd: shuffle code around and disable SMS support for now in order to prepare for the new SmsStorage abstraction
Oct 31 16:48:43 <brian_> panicking  can we install android-letest to nand only?
Oct 31 16:50:16 <panicking> The problem can be only the data directory
Oct 31 16:56:25 <panicking> that must go on the sdcard
Oct 31 16:56:29 <panicking> audio file, video
Oct 31 16:59:55 <brian_> ok
Oct 31 17:00:17 <brian_> thanks for all u do for us
Oct 31 17:08:28 <Gabrys> hey guys
Oct 31 17:09:10 <iscape2> hello Gabrys 
Oct 31 17:10:13 <lord-carlos> mhh .. why cant SHR mount my USB stick? It was working some minutes ago, but know i get an error:  mount: /media/sda/ is not a block device
Oct 31 17:10:38 <Gabrys> lord-carlos:  how do you try to mount it?
Oct 31 17:13:00 <lord-carlos> Gabrys: mount /media/sda/ test/
Oct 31 17:13:18 <Gabrys>  /media/sda is not block device 
Oct 31 17:13:29 <lord-carlos> it was working some minutes ago
Oct 31 17:13:32 <Gabrys> you should mount /dev/mmcblk0p1 or something 
Oct 31 17:15:07 <lord-carlos> that sound like the SD card
Oct 31 17:15:21 <lord-carlos> dmesg tells me he found the sda device
Oct 31 17:15:40 <panicking> larsc, Hi
Oct 31 17:15:48 <Gabrys> so you should mount /dev/sda 
Oct 31 17:16:00 <Gabrys>  /media/sda is just a directory at least
Oct 31 17:16:06 <panicking> larsc, do you have time to talk about vibrator and hdq
Oct 31 17:16:06 <panicking> ?
Oct 31 17:17:00 <lord-carlos> Gabrys: doh .. fuck .. you are totally right ...
Oct 31 17:17:04 <lord-carlos> how could i not see that 
Oct 31 17:17:29 <lord-carlos> it works now
Oct 31 17:40:46 <lord-carlos> i just installed Android .. works great :0
Oct 31 17:45:28 <bumbl> lord-carlos: what is the current available android version?
Oct 31 17:47:04 <lord-carlos> android-on-freerunner-cupcake-week-2009-44.tar.gz 
Oct 31 17:48:42 <bumbl> ah cupcake - still no donut (not to talk about the upcoming eclair)
Oct 31 18:08:18 <lxuser_> can the Wikireader hardware write to the SD card, or is it read only storage?
Oct 31 18:10:58 <lord-carlos> whats the name of the Freerunner android channel?
Oct 31 18:11:22 <Rakhun> #and2moko
Oct 31 18:12:33 <panicking> :) I can confirm :D
Oct 31 18:13:06 <lord-carlos> thanks
Oct 31 18:13:08 <panicking> lindi-, do you have try the patch?
Oct 31 18:13:24 <panicking> The cpufreq can now be used in android
Oct 31 18:13:35 <panicking> I just send the change in the init script
Oct 31 18:13:45 <panicking> and put an uImage in my download area
Oct 31 18:14:47 <Gabrys> hi again, I'm going back to my GPS problem
Oct 31 18:15:43 <Gabrys> I managed to get my location coordinates with settings >> position, but neither tangogps nor navit seem to get the location info
Oct 31 18:17:04 <radekp> hi, anybody uses the new 2.6.31 kernel already?
Oct 31 18:17:25 <radekp> i am testing it now, but i am unable to make sound system working
Oct 31 18:17:50 <radekp> e.g. when starting alsamixer:
Oct 31 18:17:51 <radekp> alsamixer: function snd_ctl_open failed for default: No such file or directory
Oct 31 18:18:17 <panicking> Yes there is a patch that I made
Oct 31 18:18:19 <panicking> for 2.6.29
Oct 31 18:18:28 <panicking> that you must apply in that tree
Oct 31 18:18:42 <panicking> The problem was the long name now supported by the kernel
Oct 31 18:18:48 <panicking> so it's a stupid issue
Oct 31 18:18:52 <panicking> or change the asound.conf
Oct 31 18:18:56 <panicking> with the long name
Oct 31 18:19:00 <panicking> instead of short version
Oct 31 18:19:58 <radekp> i fogot to add that the 2.6.30 kernel from OpenWrt does not have this problem and works just fine
Oct 31 18:21:22 <radekp> panicking: you think that the problem is with long names? i think it's somewhere in lower level...
Oct 31 18:22:20 <panicking> git log sound/soc/
Oct 31 18:22:30 <panicking> and take a look there is somenthing related to the long name
Oct 31 18:22:33 <panicking> :)
Oct 31 18:22:37 <radekp> this is what i get when i try load the module:
Oct 31 18:22:39 <radekp> neo:~# modprobe snd-soc-neo1973-wm8753
Oct 31 18:22:41 <radekp> FATAL: Error inserting snd_soc_neo1973_wm8753 (/lib/modules/2.6.31/kernel/sound/soc/s3c24xx/snd-soc-neo1973-wm8753.ko): Invalid argument
Oct 31 18:22:51 <panicking> that is an other problem
Oct 31 18:22:52 <panicking> :)
Oct 31 18:24:37 <lindi-> panicking: not yet. does it apply against andy-tracking? does gps work after resume?
Oct 31 18:28:01 <radekp> this is what i have in dmesg: http://pastebin.com/m65c9962d
Oct 31 18:28:27 <panicking> Yes on andy-tracking
Oct 31 18:28:42 <panicking> I have no application installed over android
Oct 31 18:28:47 <panicking> but I can read from the serial
Oct 31 18:28:52 <panicking> the incoming message
Oct 31 18:30:01 <panicking> Ok I know the problem
Oct 31 18:34:14 <panicking> there is a patch for 2.6.31
Oct 31 18:35:55 <panicking> http://pastebin.com/m335fee3c
Oct 31 18:36:02 <panicking> check if you have this change
Oct 31 18:36:05 <panicking> :)
Oct 31 18:36:07 <panicking> I must go now
Oct 31 19:13:21 <Gabrys> I managed to fix my problem with GPS
Oct 31 19:13:32 <Gabrys> it was gpsd running and not fso-gpsd
Oct 31 19:42:09 <panicking> radekp, do you have resolve?
Oct 31 19:44:46 <radekp> panicking: yes, but only temporary
Oct 31 19:45:23 <panicking> so what was the problem?
Oct 31 19:46:13 <radekp> gpio_request(GTA02_GPIO_HP_IN, "GTA02_HP_IN");
Oct 31 19:46:22 <radekp> returns -22
Oct 31 19:46:45 <radekp> and the driver fails to initialize
Oct 31 19:47:02 <panicking> ok
Oct 31 19:47:11 <panicking> so that pin is request by another driver
Oct 31 19:49:03 <panicking> strange
Oct 31 19:49:15 <panicking> I think that is not request by other subsystem
Oct 31 19:49:19 <panicking> I don't find it
Oct 31 19:50:34 <panicking> Ok, I understand
Oct 31 19:50:36 <panicking> maybe
Oct 31 19:57:40 <larsc> the pin is not registered to gpio lib
Oct 31 20:03:06 <panicking> larsc, nice to hear you
Oct 31 20:03:30 <panicking> I have rebase the gta02-2.6.31 to the linux-2.6 official tree
Oct 31 20:03:44 <panicking> I just skeep too patches and cleapup a little bit the code
Oct 31 20:04:00 <panicking> I would like to know if hdq and vibrator share the same timer
Oct 31 20:04:04 <panicking> or PWM
Oct 31 20:04:10 <panicking> the 3 pwm
Oct 31 20:04:15 <larsc> they do
Oct 31 20:04:53 <larsc> although i'm not sure if it's necessary
Oct 31 20:06:52 <panicking> I think that the vibrator can work on other pwm
Oct 31 20:06:59 <panicking> and the hdq request the second one
Oct 31 20:07:09 <larsc> no, the vibrator is bound to 3
Oct 31 20:07:17 <panicking> yes I know
Oct 31 20:07:24 <panicking> sorry the hdq for bitbanging
Oct 31 20:07:30 <panicking> I saw the schematic
Oct 31 20:07:50 <larsc> yes, i don't know why they choose to use the same timer for both
Oct 31 20:07:51 <panicking> Now move the hdq can semplify and clean the design
Oct 31 20:08:11 <larsc> the vibrator could be easily driven by hw pwm
Oct 31 20:08:55 <panicking> Can we use the pwm_request and pwm_config function
Oct 31 20:09:19 <panicking> to use the vibrator? They are thinking to route the signal out to the TOUT3 pin
Oct 31 20:09:20 <panicking> ?
Oct 31 20:11:24 <larsc> we can. if we move the hdq to a different timer.
Oct 31 20:11:45 <panicking> ok, the hdq request must move
Oct 31 20:12:06 <panicking> file has only some stuff function
Oct 31 20:12:16 <panicking> but a better approch is to register a platform device
Oct 31 20:12:21 <panicking> that request a timer
Oct 31 20:12:43 <panicking> the hdq bitbang use the service of the other platform device
Oct 31 20:16:05 <panicking> I would like in the next week to move to the latest linux-kernel
Oct 31 20:16:16 <panicking> so I can take a look to the runtime pm framework
Oct 31 20:16:24 <larsc> i guess at the time the hdq was written the timer platform device didn't exist
Oct 31 20:17:28 <panicking> To have a better mobile I think that we need the async resume
Oct 31 20:17:30 <panicking> patch
Oct 31 20:17:45 <panicking> I notice that the resume time increase if the bluetooth is on
Oct 31 20:17:50 <panicking> maybe because it's on the usb
Oct 31 20:18:04 <panicking> so the resume is fast without the bluetooth device on
Oct 31 20:18:34 <larsc> maybe.
Oct 31 20:18:48 <panicking> Ok I just rebase on the latest kernel
Oct 31 20:18:53 <panicking> there are only some change
Oct 31 20:19:00 <panicking> I need to fix the accelerometer
Oct 31 20:19:06 <panicking> again in your version rebased
Oct 31 20:19:21 <panicking> and try to clean the hdq
Oct 31 20:19:49 <larsc> btw. do you think it's fast enough if the accelerometer uses a threaded irq?
Oct 31 20:20:02 <panicking> Do you think about using a tasklet
Oct 31 20:20:02 <panicking> ?
Oct 31 20:20:14 <panicking> and a tasklet_schedule
Oct 31 20:20:17 <panicking> I don't know
Oct 31 20:20:21 <panicking> if spi can be run
Oct 31 20:20:33 <panicking> on a tasklet I must take a look at the code
Oct 31 20:20:59 <larsc> threaded irqs run the bottom half in it's own thread
Oct 31 20:22:03 <larsc> and in our case the tophalf would be empty
Oct 31 20:22:33 <panicking> tasklet are softirq and they are executed at every end of interrupt
Oct 31 20:22:40 <panicking> or by the ksoftirqd
Oct 31 20:22:43 <panicking> so they are fast
Oct 31 20:23:01 <panicking> but I don't know if the spi_transfer can be call in the tasklet
Oct 31 20:23:03 <panicking> path
Oct 31 20:24:22 <larsc> yes, but its encouraged not to use taskets anymore, as long as they are not absolutly necessary.
Oct 31 20:25:02 <panicking> But do you want to increase the performance on the accelerometer
Oct 31 20:25:06 <panicking> that was the question
Oct 31 20:25:18 <panicking> We must try using a game
Oct 31 20:25:35 <panicking> but I think that in android they are usefull just to automic turn the display
Oct 31 20:25:50 <panicking> Can we rebase on the latest kernel insted using merge
Oct 31 20:25:50 <panicking> ?
Oct 31 20:26:02 <larsc> yes you can
Oct 31 20:26:24 <panicking> :)
Oct 31 20:26:28 <panicking> I have just done it
Oct 31 20:26:35 <larsc> ok
Oct 31 20:26:41 <panicking> but I would like to cleanup the hdq
Oct 31 20:27:02 <panicking> and the other stuff on the latest one, it's a problem for you to create
Oct 31 20:27:04 <panicking> a branch
Oct 31 20:27:10 <panicking> aling with linux tree
Oct 31 20:27:11 <panicking> ?
Oct 31 20:27:13 <larsc> yes
Oct 31 20:27:56 <panicking> ok, I will provide one on my website
Oct 31 20:29:45 <larsc> the question regarding the acceleromater was, whether the performence difference between taskelts and threaded irqs is significant enough to justify using a tasklet
Oct 31 20:31:14 <panicking> Depends on the number of interupt on the system :) and the hrtimer enqueued
Oct 31 20:31:25 <panicking> so yes
Oct 31 20:31:33 <radekp> btw any idea why touchscreen does not work in 2.6.31? the device file in /dev/input is not created at all for it
Oct 31 20:31:59 <panicking> This is my opinion
Oct 31 20:32:28 <radekp> i have CONFIG_TOUCHSCREEN_S3C2410=y
Oct 31 20:32:29 <panicking> and the frequnecy is not so high
Oct 31 20:32:37 <panicking> og the tasklet of accelerometer
Oct 31 20:32:44 <panicking> you just increase the response time
Oct 31 20:33:08 <panicking> I will do some test move the hdq on an other timer like 2
Oct 31 20:33:17 <panicking> and clean up the interface
Oct 31 20:33:23 <larsc> two is used for something else i think
Oct 31 20:33:29 <panicking> 4 is timer
Oct 31 20:33:37 <larsc> ok
Oct 31 20:33:40 <panicking> 3 is the vibrator
Oct 31 20:33:43 <panicking> 2 is?
Oct 31 20:33:59 <panicking> Maybe the pin is used
Oct 31 20:34:07 <panicking> I must check in the schematic
Oct 31 20:34:11 <panicking> if the pin is used
Oct 31 20:35:10 <larsc> doesn't matter
Oct 31 20:35:23 <panicking> GPB2 is not used
Oct 31 20:35:29 <larsc> you have to configure the pin to output the pwm signal
Oct 31 20:35:37 <larsc> otherwise it's a normal gpio
Oct 31 20:35:42 <panicking> I don't need the output
Oct 31 20:35:46 <larsc> yes
Oct 31 20:35:53 <panicking> hdq is bitbanging
Oct 31 20:35:55 <panicking> on other pin
Oct 31 20:35:59 <larsc> but even if the pin was used it wouldn't matter
Oct 31 20:36:12 <larsc> radekp: no error messages?
Oct 31 20:36:25 <panicking> Ok, you are agree to use the TIMER2
Oct 31 20:36:27 <panicking> for hdq
Oct 31 20:36:31 <panicking> instead of TIMER3
Oct 31 20:36:36 <panicking> and remove hdq dependence
Oct 31 20:36:38 <panicking> in vibrator
Oct 31 20:36:42 <larsc> if it's not used for anything else
Oct 31 20:36:46 <radekp> larsc: i see nothing, trying now as module with verbose loglevel
Oct 31 20:37:08 <larsc> the vibrator driver should be replaced with the leds_pwm platform driver
Oct 31 20:37:19 <larsc> as it has been done for gta01
Oct 31 20:37:27 <panicking> ok
Oct 31 20:37:38 <panicking> so mondey I move the driver to the new interface
Oct 31 20:37:43 <panicking> and try to cleanup the hdq
Oct 31 20:37:53 <panicking> part for 2.6.3x kernel 
Oct 31 20:37:55 <larsc> if you want to i can try to get rid of the gta02 vibrator now
Oct 31 20:38:04 <panicking> ok
Oct 31 20:38:13 <panicking> You can send me the patch then
Oct 31 20:38:23 <larsc> i'll commit it
Oct 31 20:38:24 <panicking> So I can apply to my repo too and move to redisgn the hdq
Oct 31 20:38:43 <panicking> or you are thinking to redisgn the hdq too
Oct 31 20:38:50 <panicking> so I don't have anything todo :D
Oct 31 20:39:07 <panicking> just git am your two latest patch
Oct 31 20:39:12 <panicking> :)
Oct 31 20:39:53 <panicking> I must go, I will take a look to the repository on mondey and apply
Oct 31 20:39:56 <panicking> your latest chaneg
Oct 31 20:40:09 <panicking> I have done some work related to the frequency scaling too
Oct 31 20:40:29 <panicking> Now I must think how to wakeup at highter frequency
Oct 31 20:40:45 <larsc> nice to hear :)
Oct 31 20:40:58 <panicking> because the ondemand is ok, but not when I recevie a call
Oct 31 20:41:03 <panicking> I need all the cpu power
Oct 31 20:41:04 <panicking> :)
Oct 31 20:41:27 <panicking> to wakeup all the application in a few millisecond
Oct 31 20:41:49 <panicking> Android is not shr so i don'tknow exaclty when the system go up
Oct 31 20:41:52 <panicking> and go down
Oct 31 20:42:05 <panicking> So I don't know exacly how can I manage it
Oct 31 20:42:21 <panicking> maybe change the ondemand governator
Oct 31 20:42:36 <panicking> during resume phase to burst the cpu immidiatelly
Oct 31 20:42:57 <panicking> Ok see you larsc 
Oct 31 20:42:57 <panicking> :(
Oct 31 20:42:59 <panicking> :)
Oct 31 20:43:01 <panicking> sorry
Oct 31 20:43:31 <larsc> see you
Oct 31 20:58:24 <lxuser_> anyone here?
Oct 31 20:58:28 <radekp> larsc: i tried as module: modprobe s3c2410_ts 
Oct 31 20:58:44 <radekp> larsc: but dmesg showed nothing
Oct 31 20:59:09 <larsc> hm
Oct 31 20:59:29 <larsc> radekp: does the sysfs node exist?
Oct 31 20:59:50 <larsc> /sys/class/input/...
Oct 31 21:01:21 <radekp> larsc: no just inputs for buttons are there
Oct 31 21:05:29 <larsc> oh... looks like I forgot to commit the patch adding ts support to the gta02 machine file
Oct 31 21:10:19 <radekp> larsc: great, i will try when it's commited then
Oct 31 21:16:45 * radekp needs some sleep ;-) cu and thanks Lars
Oct 31 21:58:54 <pieterc> quit sleepy
Nov 01 02:00:31 <xxtjaxx_> say anybody got an update on the xglamo bug that makes the screen go cheesy when you swap the orientation??
**** ENDING LOGGING AT Sun Nov 01 02:59:56 2009