On Mon, 11 Feb 2002, Hal Mueller wrote:
> >A lot of people have questions about the right way to "check the
> >hardware". Do you have any guidelines on that? For instance, I
> >know of at least six different LCD controllers for Palm devices; how
> >does one write code to recognize those?
>
> I'm not Aaron, but, if the LCD controller is tied to particular
> models, I've been collecting the specs on how to check that. There
> was no central registry of the values for sysFtrNumOEMDeviceID and
> sysFtrNumOEMCompanyID, so I created one. It's at
> http://www.mobilegeographics.com/dev/devices.html
eek.. thats nasty man :) we only need two features!
sysFtrLCDControllerType --> return an ID of the controller
sysFtrLCDMemoryBase --> the base memory mapping for registers
as requested way back in Jul 31, 2001 on the forum here:
http://www.escribe.com/computing/pcpqa/m44786.html
wouldn't that be easier? first id the chip, and, get the address
of the register mapping.. then, poke, poke, poke.. :) [of course,
i wouldn't guarentee stability in the operating system - but, you
could do some fun stuff]
most commonly used feature would be setting display address to
ram or some vram - without the complexities of WinScreenLock
[which also have problems with certain licensee's (sony + handspring)]
i personally dont trust the licensee's implementation and, i prefer
to do the hard work myself - at least then, i know it'll work and
wont have any garbage (unecessary checking code etc) around it.
// 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/tech/support/forums/
