Results 1 to 11 of 11
  1.    #1  
    DO NOT RUN THIS KERNEL etc.

    This is the same configuration as the previous 1.4.1.6-9 but with gcc optimisations applied for a careful perusal of arm options. Note that some apps may fail; I haven't found one yet but since I am intermixing CPU instruction sets there is a non-zero chance this may occur. I would be interested in knowning of any apps that have this issue.

    There is one known issue so far; first time around a 3D app may be flicker, particularly when run soon after bootup. I would again be interest of knowing of any apps that do or do not display this behaviour.

    www.fop.ns.ca/pre/uImage.1.4.1-6.9.ricer for the kernel image.

    Cheers, Steve
  2.    #2  
    Quote Originally Posted by gsx62391@yahoo.com View Post
    more info?
    What info are you looking for?

    Cheers, Steve
  3. #3  
    It has been known that scaling makes several apps flicker, not too bad, but just annoying
    I'd rather prefer 500-800mhz than 125-800mhz, but that's just my opinion.

    Running this right now, will report results
  4.    #4  
    Quote Originally Posted by NuttyBunny View Post
    It has been known that scaling makes several apps flicker, not too bad, but just annoying
    I'd rather prefer 500-800mhz than 125-800mhz, but that's just my opinion.

    Running this right now, will report results
    echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
    echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

    Should lock the frequency range for you.

    Cheers, Steve
  5. #5  
    Quote Originally Posted by sbromwich View Post
    echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
    echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

    Should lock the frequency range for you.

    Cheers, Steve
    I know, I know

    Done, hope it helps.
  6.    #6  
    Quote Originally Posted by NuttyBunny View Post
    I know, I know

    Done, hope it helps.
    Sorry, I'm getting too many people needing to be spoonfed and forgot you had clue

    Dicker with up_threshold too. Also I'd be interested if dmesg reports prcm timeouts anywhere.

    Cheers, Steve
  7. #7  
    Quote Originally Posted by sbromwich View Post
    Sorry, I'm getting too many people needing to be spoonfed and forgot you had clue

    Dicker with up_threshold too. Also I'd be interested if dmesg reports prcm timeouts anywhere.

    Cheers, Steve
    Well, I do have a recent timeout, gimme a half hour to park in a safe spot to get the log, too bad I can copy in Terminal on the Pre
  8. #8  
    [44599.500000] Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
    [44646.510000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44682.100000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44701.630000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44733.640000] MAXIM7359: Two key down events (missing up). (idx=14, time=40)
    [44733.640000] MAXIM7359: Rejecting key down bounce. (idx=14)
    [44747.740000] MAXIM7359: Two key down events (missing up). (idx=19, time=130)
    [44747.740000] MAXIM7359: Rejecting key down bounce. (idx=19)
    [44769.230000] Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
    [44771.440000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44845.110000] Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1
    [44941.270000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44958.040000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44998.330000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3

    But I was not doing much, just checking the browser and Terminal
  9.    #9  
    Quote Originally Posted by NuttyBunny View Post
    [44599.500000]
    [44701.630000] Timeout in prcm_check_power_domain_status(), domain 9, desired state 1, current state 3
    [44733.640000] MAXIM7359: Two key down events (missing up). (idx=14, time=40)
    [44733.640000] MAXIM7359: Rejecting key down bounce. (idx=14)
    [44747.740000] MAXIM7359: Two key down events (missing up). (idx=19, time=130)
    [44747.740000] MAXIM7359: Rejecting key down bounce. (idx=19)
    [44769.230000] Timeout in prcm_check_clock_domain_status(), domainid 9, desired state 0, current state 1

    But I was not doing much, just checking the browser and Terminal
    This bit is particularly interesting to me. I don't suppose by any chance you recall which buttons you were pressing?

    Cheers, Steve
  10. #10  
    Quote Originally Posted by sbromwich View Post
    This bit is particularly interesting to me. I don't suppose by any chance you recall which buttons you were pressing?

    Cheers, Steve
    Could have been Orange+. , Orange+, or Shift+. , for getting <,> and | on Terminal
  11.    #11  
    Quote Originally Posted by NuttyBunny View Post
    Could have been Orange+. , Orange+, or Shift+. , for getting <,> and | on Terminal
    Ahhh... not what I thought then, I was wondering if the hardware itself was having debounce issues with power/volume/other buttons. I'd appreciate it if you could keep an eye on it in case you see that error when you're not in terminal. Thanks!

    Cheers, Steve

Posting Permissions