Author Topic: Cydia  (Read 12542 times)

0 Members and 1 Guest are viewing this topic.

Offline AssemblyBandit

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 374
  • Rating: +60/-1
  • ~AssemblyBandit~
    • View Profile
    • briandm82.com
Re: Cydia
« Reply #30 on: April 25, 2010, 12:40:11 pm »
Well, i have a couple of complaints, first why does the include file have ram start at $8000? If someone swaps pages (which they will because theres no point in having duplicate pages) then they will get messed up. Correct me if im wrong but doesnt the ram start on page 0 (permanently mapped at $c000)? Second, Ive been trying to get some flickerless grayscale and it doesnt seem to want to work with me. I got some source code for this so called "4 level grayscale" but the guy really didnt seem to understand how grayscale actually works, he was just flashing two layers on and off at equal increments which just equates to 3 level grayscale? (that flickers like crazy.) Ive gotten some values that work good but even then theres this slow flicker that goes through. Ill try some more tonight using im2 but i cant stand the way ti did away with the memory mapped display, I just cant see why they would change it. they are anti grayscale though, so i guess that probably had something to do with it.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Cydia
« Reply #31 on: April 25, 2010, 12:47:23 pm »
Unfortunately I cannot help much x.x but if Revsoft was still around, I would have redirected you to their grayscale package. Both theirs and Durk Kingma packages do it right, except the later is not well optimized and slows down games a lot. Grayscale on the 82/84 series is different from 85/86 since the screen is not memory-mapped. Usually the newer grayscale packages adds some sort of interlacing in grayscale display to minimize the flicker effect. As for RAM pages I doN,t know x.x, you may need to wait until someone who knows ASM awnser.

For what shell/kernel are you compiling for, by the way? I think under Ion and no-stub there's a 8 KB executable code limit.

Offline ztrumpet

  • The Rarely Active One
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5712
  • Rating: +364/-4
  • If you see this, send me a PM. Just for fun.
    • View Profile
Re: Cydia
« Reply #32 on: April 25, 2010, 01:33:09 pm »
I don't know much, but I just saw the answer to this in Asm in 28:
For what shell/kernel are you compiling for, by the way? I think under Ion and no-stub there's a 8 KB executable code limit.
You can use some incredibly tricky code to get around this.  I'm pretty sure it works for no-stub, but as always, I'm not sure. ;D

Offline mapar007

  • LV7 Elite (Next: 700)
  • *******
  • Posts: 550
  • Rating: +28/-5
  • The Great Mata Mata
    • View Profile
Re: Cydia
« Reply #33 on: April 26, 2010, 01:28:16 pm »
84+ screen sucks (that's why your grayscale doesn't work, probably :) ). I've never done grayscale, so I can't help that much here.
You can get around the executable code limit by copying pieces of code to system ram and calling them over there. Page 80h  (or 0 if you want) in RAM is permanently mapped at $c000, but it's non-executable. Page 81h is the default in $8000. That's just, well, yeah, TI style :)

Offline AssemblyBandit

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 374
  • Rating: +60/-1
  • ~AssemblyBandit~
    • View Profile
    • briandm82.com
Re: Cydia
« Reply #34 on: April 26, 2010, 06:23:29 pm »
The bastards!

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Cydia
« Reply #35 on: April 26, 2010, 11:26:13 pm »
Indeed D:

Heck just to tell how bad the 83x LCDs are, even grayscale in BASIC with ASM libs looks better on 6 MHz calcs than 15 MHz ones if not modified. The picosecond it starts updating too quick, it looks terrible