On Tue, 2 Apr 2002, Stanley Silverspeed wrote:
> Uh oh. Many new things to learn :-). So I got the .pdfs about
> SED1375/SED1376.
yep.. they have a nice resting place on my harddrive too :)
soon, i'll be announcing something in which we can have some
fun with a Palm m505:
http://www.mobilewizardry.com/
:) i'll send an official announcement out as soon as i have
finalized the details *g* [hopefully today] - but, here are
some teasers:
---
http://mobilewizardry.com/palm/contest/images/demos/palmos-plasma.gif
http://mobilewizardry.com/palm/contest/images/demos/palmos-snow.gif
http://mobilewizardry.com/palm/contest/images/demos/palmos-stars.gif
http://mobilewizardry.com/palm/contest/images/demos/palmos-tvstatic.gif
---
i'll give you a hint - these binaries are *small* :)
> Well, It looks these chips have all nesessery features - wide virtual
> screens and 80K looks enough for 3 160x160x8bpp pages in VRAM.
yeah, device is capable of 160x160x16bpp.. pity it wasn't 120K :P
> Well, for next few days I am learning from this documents and experiment.
> The problem is: what if Palm will use another chips in it's new devices?
> And what about licensed color devices - do they have these SEDs on-board?
different licensee's use different controllers..
so far, handspring prism, palm IIIc, palm m505, palm m515 use sed
controllers.. not too sure about m130 (aint got my hands on one yet)
but.... the sony units dont use the SED controllers.
> So do I understand the proposed strategy properly:
>
> 1. I should check color capabilities of the device using
> WinScreenMode(winScreenModeGetSupportedDepths...).
> 2. If it's monochrome (no 8 bpp mode), then the processor controls
> the screen and I have to use LSSA and other DragonBall regs.
> 3 Else I must suggest SED1375/SED1376 onboard (check 0x1F00000)
> and use corresponding routines for these chips?
beware.. poking at 0x1f000000 may not be safe if the SED controller
isn't there.. *g* you might get a FATAL EXCEPTION on a sony unit
for example.. this may happen if the os doesn't map the 0x1f00000
memory section... [i haven't tried it]
thats the whole reason why i would like then to "do" something :)
one way you could check, is call WinScreenLock(winLockDontCare)
and WinScreenUnlock() and check if the pointer is 0x1f...... :)
that might be some use, as then you can poke around that memory
location(s)
// az
[EMAIL PROTECTED]
http://www.ardiri.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
