Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - karlto

Pages: 1 ... 21 22 [23]
Zaurus - pdaXrom / Sl6000 Wake On Alarm
« on: December 15, 2005, 09:49:40 pm »
Excellent news!

I found it - a simple line at the top of the file that turned off wakeups for RTC alarms on the tosa only! I have successfully tested it using apmsleep (not exhaustive by any means, but I am pretty sure this is it, as it lines up with the corgi etc code.)

Here it is:

- kernel patch for those who compile and for future use
- standard sl6000 rc12 tools.tar ready to flash for lazy people like me

Zaurus - pdaXrom / Sl6000 Wake On Alarm
« on: December 15, 2005, 06:23:15 pm »
Neat - I will have a look at the Sharp kernel source. I can't seem to find any source for the guylhem one though; only compiled images ready to go...

They all seem to be based on the original Sharp one, but I think that possibly one of the changes has broken SL6000 alarms (not the most common Zaurus).

Thanks for your help

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 15, 2005, 02:46:29 pm »
Hi all

Still not having any joy with the SL6000 waking up on alarm - I have started a new thread here:

SL6000 Wake On Alarm

as it is starting to get a little off topic here...

Zaurus - pdaXrom / Sl6000 Wake On Alarm
« on: December 15, 2005, 02:44:56 pm »
Hi all

The SL6000 seems to be the only Zaurus that won't wake on alarm in the latest RC12. I am keen to get your opinions and assistance to find the solution to this.

So far, I have managed to compile a kernel with debug options set in the power management section - this is a sample of the dmesg output:

Code: [Select]
queue_event: event=10
set_power_state: what=1 state=2
set_power_state: *** go into suspend
pxa_suspend: FCS : CCCR = 241
pxa_suspend: pass_charge_flag = 0
pxa_suspend: check AC-adaptor
pxa_suspend: kick charging
pxa_suspend: ac97&tc6393 down
pxa_suspend: RTAR charge = 401e3317

==== This is where sleep mode is entered ====

If there was a problem with the code after resuming from sleep, we would see messages about going back to sleep/suspend below, but we don't. So, issue must be above in telling processor how to sleep...?


pxa_suspend: ac97&tc6393 up
ac97_codec: AC97 Audio codec, id: WML18 (Wolfson WM9711/WM9712)
init TC6369 Revision 3
pxa_suspend: back the ALARM Time
sharpsl_wakeup_hook: GPLR0 = 3ef89a
key interrupt on (0001,0000)
FCS : CCCR = 161
send_event: event=3
sleeping to allow SD card to resume...
sleep complete.
wm9712_update_jack_state: HP jack state changed (Jack=0,Mic=0)

In theory, hardware wakeups that are correctly set up will resume the kernel power code from sleep at the point noted in the messages above. Things such as unplugging the power etc will also wake it up, so there is some code to send it back to sleep if no need to wake up. albertr's patch (incorporated into RC12) stopped it from going back to sleep if the alarm was set. The SL6000 doesn't actually wake at all though - it's like the hardware wakeup isn't set properly for the alarm. While the corgi (760) has the same processor, there are a number of general purpose registers (GPIO) that are used differently for the tosa, and a lot of tosa-specific code to account for this (e.g. the battery charge indicator appears to be completely opposite). I have the processor specs but not Zaurus specs.

In short, the SL6000 seems to respond to battery/AC/button events when in sleep mode, but not the alarm. This leads me to believe that the alarm isn't quite set correctly (as it is difficult to figure out the correct GPIO settings). Some possibly useful info from registers in the dmesg output above, and I can always modify to get more.

Is it possible to find original/unmodified Sharp code for the SL6000 power routines? Zaurus spec on what/how the GPIO registers are used? Does OZ or anyone else have working suspend/resume on alarm code that we can look at to get the right settings?

BTW, I am working with /arch/arm/mach-pxa/sharpsl_power.c above...

Thanks for any help or suggestions!

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 14, 2005, 01:57:06 pm »
I will echo karlto.  With a clean flash of RC12 atd works fine except it for the wake form suspend issue.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=107022\"][{POST_SNAPBACK}][/a][/div]
no running ntpd or somelike utils which can modify hardware clock?

just tried atd with SL-C760, work fine.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=107060\"][{POST_SNAPBACK}][/a][/div]

I don't have any of that running either (except atd to try it out).  I have no data to lose at present, so if there is anything you would like me to test, let me know...

Zaurus - pdaXrom / Irda Nokia Connection
« on: December 13, 2005, 03:15:47 pm »
Not quite the same hardware, but I have my (old) Nokia 6385 working fine with my SL6000 via IR. I just use the ppp dialer, but it needed patching to remove the second set of double quotes around the password (I think there is a bug report on the pdaXrom site). Also need specific initialisation string for the phone to work without hanging up (Nokia has these somewhere on the net).

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 13, 2005, 03:09:05 pm »
Thanks sash. atd works as expected on the SL6000 - no wake from suspend though.

I'm sure the wakeup issue is with the kernel, so I'll keep perservering to get one compiled...

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 11, 2005, 01:33:14 pm »

Just a quick update. The reason why I used minutes instead of a time is that it is far (FAR) easier to find the thing that is the nearest minutes away than to subtract two time+dates ;-) (IE, for the scripts in wakeup.d) using simple bash.

 - Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106538\"][{POST_SNAPBACK}][/a][/div]

Don't listen to me too much - I can't even get the thing to wake up by itself yet...

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 06, 2005, 08:20:43 pm »
pgas - thanks for the tip on the compiler (I think I have been trying various 3.x versions, but haven't gone back that far)

Because the SL6000 is a PXA255 (not PX270 as many others), I think this is why the RTC alarm wakeup problems. I have some thoughts on where to put a similar patch, so hopefully I can get a kernel to compile to test it...

plcg and desertrat seem to be getting the same behaviour as I am - everything works except the actual hardware wakeup!

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 05, 2005, 09:53:21 pm »

All this stuff is starting to look very good - having a working alarm is high on the priority list!

If you are having difficulties with apmsleep, it is quite simple to write a program that puts a specific date and time into the RTC alarm register - see the Linux kernel RTC documentation/apmsleep source for all the code you need. It can also be done using the registers.o module if you don't want to program anything (just convert date/time to hex and write to the /proc/cpu/registers/RTAR file). Personally I find it much easier to simply specify a date/time to wake up rather than figuring out the number of minutes

I have the code I was using to test my SL6000 somewhere if anyone is interested - problem is that the RTC alarm support in the pdaXrom kernel still doesn't work for the 6000! I am still trying to figure out how to get a kernel to cross compile when I have time - if anyone has any hints on which source, patches and version of the compiler I should use, please let me know!


(RC12, SL6000L)

Zaurus - pdaXrom / Ko/pi Alarm Applet Needed
« on: October 06, 2005, 11:02:51 pm »
I think I found the problem. Here's a quick and dirty fix that seems to work on my C1K:

I think the right way to fix the problem is to mask the appropriate wakeup events, but that would require reading thru sharp's messy kernel code and understand all dependancies for possible events. I just don't have time for this right now, if anyone wants to give it a shot, please feel free to provide a better fix.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98485\"][{POST_SNAPBACK}][/a][/div]

Thanks albertr - that makes some sense. I was hunting around these registers yesterday looking for issues (before my head exploded between the processor docs and the Sharp kernel source...).

I was hoping not to have to recompile a kernel, but it looks inevitable. There is a lot of specific stuff for the tosa that seems to be in Sharp's source not referred to in the pdaxrom headers I have. When I get some spare time I will download the pdaxrom kernel source and give it a bash...

Zaurus - pdaXrom / Ko/pi Alarm Applet Needed
« on: October 05, 2005, 05:01:35 pm »
I would be keen to help too - just not sure what to do next...

Does anyone know where any detailed specs are? What about source for the apm in the stock Zaurus kernel (which does wake up)?

Zaurus - pdaXrom / Ko/pi Alarm Applet Needed
« on: October 03, 2005, 11:40:20 pm »

I have an SL6000L and I have the exact same problem on RC10 and RC11 - after a lot of googling this is the first time I have found anyone with the same issue!

The problem lies with the RTC wakeup somewhere - I have used apmsleep, and even written my own test programs using the SDK and info from the Linux kernel rtc documentation. It sets the alarm time correctly, and appears to turn the alarm interrupt on - I have never seen it confirmed via /proc/driver/rtc, but I can confirm that the interrupt fires (via the count in /proc/interrupts) unless the alarm is cancelled before the time arrives.

The Zaurus just never wakes up when the interrupt fires. If this were a PC, this would normally relate to a BIOS setting telling the machine to wake on this interrupt.

Aside from this issue, pdaXrom does absolutely everything I want and I am keen to get it fixed - any ideas that I can try out to get more info (or solve the problem!) would be greatly appreciated.



I can confirm that running apmsleep +0:05  by hand works on a C860 fine (well, it wakes up with pauses but thats 'normal' and fixed by getting dpms to call apm instead).

Anyone else with a sl6000 have positive results?

 - Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98055\"][{POST_SNAPBACK}][/a][/div]

Pages: 1 ... 21 22 [23]