Well, actually the 32kb limit is NOT that true... at least with the new Palm OS 3.3,
which promises to make the heap grow proportionally with memory upgrades (actually
being, AFAIK, 32kb for 2MB, 48kb for 4MB, and +/- 64 kb for 8MB). Moreover, the
actual size of the
window where my project can draw (I still didn't decided how to call it, some help
please?) need not be 160 x 160 pix. always; and AFAIK most of the buffers needed for
GL
operation seems to depend on that window's size. So, Brian (I know you told me about
that before), memory is not, by now, my primary
concern, because it can be tied to programmer-user requirements. What annoys me a
little bit
is the complete absence of hardware floating-point support. I know of two ways for
overcoming that problem: 1. Use of the floating-point emulation library (somewhat
large, and slow, but it gives exactly what is needed), 2. Use of fixed-point
arithmetic
(EEEAGH!! :) (although I must say I'm using it, internally). Hmmm, it would be
interesting to
allow (or not) using of floating-point arithmetic
by using #ifdef's, to only let access to functions requiring GLbyte, GLshort, GLint
parameters; or
even better, to use #ifdefs for switching between floating-point or fixed-point
arithmetic for parameter specification at compile time. Anyway, I will look further to
the source code of Mesa which I downloaded 2 weeks ago to find if I can integrate my
current project in a smooth way. BTW, is there a document where I can find out how
the current Mesa source is organized, to make me easier to navigate through it? Or,
better yet, can someone explain me it (off list, of course)? Be sure I will post to
this list often to inform you of the status of my project. See you later!
- izhido
([EMAIL PROTECTED])
--
On Mon, 15 Nov 1999 09:52:57 Stephen J Baker wrote:
>On Mon, 15 Nov 1999, Brian Paul wrote:
>
>> However, as I understand it, the system is limited to 32KB code
>> and data segments. Mesa's code is much larger and often
>> allocates buffers larger than 32KB.
>>
>> It may be pretty hard to squeeze Mesa into the Palm. Also, I really
>> don't want to see the Mesa code littered with Palm-specific work-
>> arounds.
>
>I agree - if there are more than a handful of #ifdef's...but
>I suspect Palm pilots have come on quite a way since the 32Kb
>restriction. There was something on slashdot a while back
>about some Linux subset running on one of the Palm series
>machines...it's hard to imagine that with a 32k restriction.
>
>Steve Baker (817)619-2657 (Vox/Vox-Mail)
>Raytheon Systems Inc. (817)619-2466 (Fax)
>Work: [EMAIL PROTECTED] http://www.hti.com
>Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
>
>
>
>_______________________________________________
>Mesa-dev maillist - [EMAIL PROTECTED]
>http://lists.mesa3d.org/mailman/listinfo/mesa-dev
>
theglobe.com
Your friendly full-service integrated online community.
http://www.theglobe.com
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
