Thread: [Mesa3d-dev] to Implement on new GPUs

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

dear all ,

Would any one suggest me.
How to implement es into new GPU's ?

thanking you
regards
Nitesh Suthar

On Sat, Apr 10, 2010 at 11:09 AM, nitesh suthar <nit...@gm...> wrote:
> dear all ,
> Would any one suggest me.
> How to implement es into new GPU's ?
>

Please could you elaborate on "implement es into new GPU's"?

> thanking you
> regards
> Nitesh Suthar
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Mesa3d-dev mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
>
>

hello all,

thank you for reply

Actually I am working on arm board which support OpenGLES 1.1 and OpenGLES
2.0.
which provides hardware acceleration for redering images.
What my objective is that I want to implement this OpenGLES 2.0 into mesa
for interactive graphics with hardware acceleration to use Mesa in arm board
with this suppurted OpenGLES libraries.

how could I proceed for implement OpenGLES 2.0 in Mesa ?

thanking you
Nitesh Suthar

On Sun, Apr 11, 2010 at 5:14 PM, PLUG GULP <plu...@gm...> wrote:

> On Sat, Apr 10, 2010 at 11:09 AM, nitesh suthar <nit...@gm...>
> wrote:
> > dear all ,
> > Would any one suggest me.
> > How to implement es into new GPU's ?
> >
>
> Please could you elaborate on "implement es into new GPU's"?
>
>
> > thanking you
> > regards
> > Nitesh Suthar
> >
> ------------------------------------------------------------------------------
> > Download Intel&#174; Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Mesa3d-dev mailing list
> > Mes...@li...
> > https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
> >
> >
>

On Mon, Apr 12, 2010 at 9:13 PM, nitesh suthar <nit...@gm...> wrote:
> hello all,
> thank you for reply
> Actually I am working on arm board which support OpenGLES 1.1 and OpenGLES
> 2.0.
> which provides hardware acceleration for redering images.
> What my objective is that I want to implement this OpenGLES 2.0 into mesa
> for interactive graphics with hardware acceleration to use Mesa in arm board
> with this suppurted OpenGLES libraries.
> how could I proceed for implement OpenGLES 2.0 in Mesa ?

GL and GLES are programming APIs, not hardware APIs. In order to
support your hardware, you will have to write a backend driver which
interfaces with that hardware for Mesa.

We're not all embedded developers, but some of us might be familiar
with your hardware. Which chipset and board is this?

~ C.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<Mos...@gm...>

>GL and GLES are programming APIs, not hardware APIs. In order to
>support your hardware, you will have to write a backend driver which
>interfaces with that hardware for Mesa.

  thanks,
  yes I know these are programming APIs,

 so how could I start developing this backend driver which interfaces with
that hardware for Mesa. Is there any fix architecture to interface that
driver to Mesa lib or mesa's function ?
and What is procedure for implementing such interface in my backend driver
so that
it can interact with Mesa lib.

>We're not all embedded developers, but some of us might be familiar
>with your hardware. Which chipset and board is this?

I am using SOC  S3C6410 .

thanking you
Nitesh Suthar

On Tue, Apr 13, 2010 at 11:27 PM, Corbin Simpson
<mos...@gm...>wrote:

> On Mon, Apr 12, 2010 at 9:13 PM, nitesh suthar <nit...@gm...>
> wrote:
> > hello all,
> > thank you for reply
> > Actually I am working on arm board which support OpenGLES 1.1 and
> OpenGLES
> > 2.0.
> > which provides hardware acceleration for redering images.
> > What my objective is that I want to implement this OpenGLES 2.0 into mesa
> > for interactive graphics with hardware acceleration to use Mesa in arm
> board
> > with this suppurted OpenGLES libraries.
> > how could I proceed for implement OpenGLES 2.0 in Mesa ?
>
> GL and GLES are programming APIs, not hardware APIs. In order to
> support your hardware, you will have to write a backend driver which
> interfaces with that hardware for Mesa.
>
> We're not all embedded developers, but some of us might be familiar
> with your hardware. Which chipset and board is this?
>
> ~ C.
>
> --
> When the facts change, I change my mind. What do you do, sir? ~ Keynes
>
> Corbin Simpson
> <Mos...@gm...>
>

On Thu, Apr 15, 2010 at 7:12 AM, nitesh suthar <nit...@gm...> wrote:
> I am using SOC  S3C6410 .

Google doesn't tell me much about this chip other than that it's made
by Samsung and it powers some Android devices. A few posts suggest
that it's either a Samsung original, or an SGX-based core.

If it's the latter, you are out of luck. SGX does not have any
open-source code or free datasheets, and they actively discourage
reverse-engineering by levying strong licensing requirements on their
binary drivers.

Your best bet at this stage may well be to contact Samsung.

At any rate, Mesa drivers are implemented by writing code that uses
the hooks in the general driver context. src/mesa/drivers are all the
drivers, and src/mesa/drivers/dri may be of particular use if you are
planning on doing GL with X.

~ C.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<Mos...@gm...>

Hi there,

You could try to contact OpenMoko Inc for specifications regarding
S3C6410. They forwarded the  specs  they received for their previous
device to developers that signed an NDA. Before they stopped plans to
develop another open linux phone, they were working with the S3C6410
platform. At least you can try ...

http://wiki.openmoko.org/wiki/GTA03_revisions

But maybe you already have detailed specifications about the 3D processor?

2010/4/15 nitesh suthar <nit...@gm...>:
>
>>GL and GLES are programming APIs, not hardware APIs. In order to
>>support your hardware, you will have to write a backend driver which
>>interfaces with that hardware for Mesa.
>
>   thanks,
>   yes I know these are programming APIs,
>  so how could I start developing this backend driver which interfaces with
> that hardware for Mesa. Is there any fix architecture to interface that
> driver to Mesa lib or mesa's function ?
> and What is procedure for implementing such interface in my backend driver
> so that
> it can interact with Mesa lib.

You would need a drm kernel driver, some extension to the drm to allow
platfrom devices to provde drm drivers - not only pci dvices. User
spaces parts of the DRM  module in libdrm for your hardware. ...
Something similar had been done for another embedded gpu: smedia
glamo:

 http://www.bitwiz.org.uk/s/dri-for-the-freerunner.html

>>We're not all embedded developers, but some of us might be familiar
>>with your hardware. Which chipset and board is this?
> I am using SOC  S3C6410 .
> thanking you

regards
Andreas Pokorny