Re: intel 2700 register values

http://www.powervr.com/Downloads/Drivers/2-01-21-0007/powervr-2.01.21-7.tgz
http://www.pvrdev.com/Pub/MBX/

http://www.khronos.org/opengles/
http://www.khronos.org/opengles/documentation/gles-1.0c.tgz

ramblings... words spewing out my ears:

I think you're right about all the draw backs about the pci/agp bus, and
it is definitely not a frame-buffer driver, and uses X's DRM.
Why is it messing with pci/agp in X at all.... memory map stuff?
Hope I am wrong about that.

Worse their License is closed, dreadful, and talks about "No Reverse
Engineering" when it is source code ;-) . This could reduce the code
to being only useful for looking at. Could looking at the code
poison a new driver's GPL status?

So what is the association between the 2700G5 and MBX-whatever?
The Intel 2700G5 incorporates the PowerVR MBX graphic core, and
PowerVR video accel (from the Internet).
So what do we do? Most of the APIs are windowblown.
Maybe a OpenGL frame-buffer driver? (I see there are some, but
possibly proprietary : Nvidia )
What about VGA?
LinuxBios (crossed with HaRET) for initializing the thing?
Why didn't using a VGA console (vgacon) on the X50v work (I tried...
but I at that point I had even less of a clue). Was it expecting PCI bus etc?
I guess the VGA resources were not mapped in, something a bios could do.
Thats enough for console until X (or something graphic) can start.

I will retry my old experiments with a new cable (travel USB cable with
Serial added, and if I get ambitious, VGA out just in case things don't
go to the right place). Another thanks to Fisherss for the pretty
cable diagram.

As a last resort, get X up as quickly as possible, and soft boot the
display ( I have a couple of old laptops like that).

        J.Currey

On Sat, Jun 25, 2005 at 08:11:49AM -0600, Richard Bateman wrote:
> These aren't memory addresses, they are the values set in the registers
> on the 2700g chip. As to how I found the memory address that I got them
> from, simplicity in itself... I already knew that the base memory
> address for video ram on the x50v is 0x0c00_0000, and according to the
> intel 2700g docs the registers are in the last 128kb of memory, which
> puts them at 0x0ffe_0000 to 0x0fff_ffff
>
> I just calculated the offset and went through and looked at all the
> memory. I learned a few entertaining tricks as well; I can turn on the
> hardware cursor, for instance, and make it blink. sure, not real useful
> to us, but I can still do it! =]
>
> So i'm positive that those are the right registers.
>
> If we can get a driver from powervr, that woudl be great, but A. they
> probably don't have a framebuffer driver, only an xwindows driver, and
> B. their driver will probably be for AGP and/or PCI on a desktop
> processor, and may or may not be easy to port.
>
> Could you drop them an email, though? When we go to make the xwindows
> driver, having a driver already made, even if it uses the wrong bus,
> could speed things up tremendously.
>
> Framebuffer driver has got to be done first, though.
>
> Richard
>
> Salem Salemixu wrote:
>
> >Hi! I wonder how did you do to get those memory addresses.
> >About the driver, wouldn't it be better to ask Intel or PowerVR about
> >them, we could have in a short time the right drivers with 3D
> >acceleration included :)
> >
> >
> >Richard Bateman wrote:
> >
> >
> >>I just finished recording the values of the registers on the 2700; I
> >>may start a framebuffer driver tomorrow, if I have time. if anyone has
> >>made any progress on one, let me know so I don't redo things =]
> >>
> >>Richard
> >>
> >>The 2700 register values on the x50v (at least mine) are:
> >>
> >>
> >>DEVICE ID: 0x01727189
> >>
> >>
> >>SYSCFG - 0x00000000
> >>PFBASE - 0x00000000
> >>PFCEIL - 0x03fdffe0
> >>SYSRST - 0x00000000
> >>
> >>
> >>NINTPW - 0x0000001c
> >>MINTENABLE- 0x0000800f
> >>MINTSTAT- 0x00000000
> >>SINTENABLE- 0x00000000
> >>SINTSTAT- 0x00000010
> >>SINTCLR - 0x00000000
> >>
> >>
> >>SYSCLKSRC-0x00000002
> >>PIXCLKSRC-0x00000001
> >>CLKSLEEP- 0x00000000
> >>COREPLL - 0x00000bb1
> >>DISPPLL - 0x00000395
> >>PLLSTAT - 0x00000005
> >>VOVRCLK - 0x00000000
> >>PIXCLK - 0x00000001
> >>MEMCLK - 0x00000001
> >>
> >>SDCLK - 0x00000001
> >>PIXCLKDIV-0x00000001
> >>
> >>
> >>LCD_CONFIG - 0x2efa0000
> >>
> >>ODFBPWR - 0x00000000
> >>
> >>
> >>PWMCFG - 0x00000003
> >>PWM0DIV - 0x00000000
> >>PWM0DUTY- 0x00000000
> >>PWM0PER - 0x00000004
> >>PWM1DIV - 0x00000000
> >>PWM1DUTY- 0x00000000
> >>PWM1PER - 0x00000004
> >>
> >>
> >>LMCFG - 0x00000027
> >>LMPWR - 0x00000000
> >>LMPWRSTAT-0x00000000
> >>LMCEMR - 0x00000000
> >>LMTYPE - 0x00000ac8
> >>LMTIM - 0x00073392
> >>LMREFRESH-0x00000615
> >>LMPROTMIN-0x00000000
> >>LMPROTMAX-0x03fdfffc
> >>LMPROTCFG-0x00000000
> >>LMPROTERR-0x00000000
> >>
> >>
> >>DSCTRL - 0x8000002a
> >>DHT01 - 0x00400288
> >>DHT02 - 0x00500050
> >>DHT03 - 0x02300230
> >>
> >>DVT01 - 0x00020284
> >>DVT02 - 0x00030003
> >>DVT03 - 0x02830283
> >>
> >>DVECTRL - 0x02830283
> >>DHDET - 0x00500230
> >>DVDET - 0x00030283
> >>
> >>DODMSK - 0x00000000
> >>
> >>
> >>DBCOL - 0x00000000
> >>DSIG(RO)- 0xe2ce15ab
> >>DVLNUM - 0x000001a6 (422)
> >>
> >>DMCTRL - 0x10303010
> >>DINTRS - 0x00000015
> >>DINTRE - 0x00000000
> >>
> >>DINTRCNT- 0x00000000
> >>DLSTS - 0x00800000
> >>
> >>
> >>VIDGAM[0:16]
> >>0ffe2200 | 0x00000000 0x00101010 0x00202020 0x00303030
> >>0ffe2210 | 0x00404040 0x00505050 0x00606060 0x00707070
> >>0ffe2220 | 0x00808080 0x00909090 0x00a0a0a0 0x00b0b0b0
> >>0ffe2230 | 0x00c0c0c0 0x00cfcfcf 0x00e0e0e0 0x00f0f0f0
> >>0ffe2240 | 0x00ffffff
> >>
> >>GFXGAM[0:16]
> >>0ffe2250 | 0x00000000 0x00101010 0x00202020 0x00303030
> >>0ffe2260 | 0x00404040 0x00505050 0x00606060 0x00707070
> >>0ffe2270 | 0x00808080 0x00909090 0x00a0a0a0 0x00b0b0b0
> >>0ffe2280 | 0x00c0c0c0 0x00cfcfcf 0x00e0e0e0 0x00f0f0f0
> >>0ffe2290 | 0x00ffffff
> >>
> >>Plane Control:
> >>
> >>GSCTRL - 0x3c0efa7f
> >>GBBASE - 0x00000000
> >>GDRCTRL - 0x00ffffff
> >>GSCADR - 0x80000000
> >>GSADR - 0x0ec00000
> >>GPLUT - 0x00000000
> >>
> >>Video Display
> >>VSCTRL - 0x0600780f
> >>VBBASE - 0x00000000
> >>VCMSK - 0x00ffffff
> >>VSCADR - 0x01000000
> >>VUBASE - 0x00000000
> >>VVBASE - 0x00000000
> >>VSADR - 0x00000000
> >>_______________________________________________
> >>Aximx30-port mailing list
> >>Aximx30-port_at_handhelds.org
> >>https://www.handhelds.org/mailman/listinfo/aximx30-port
> >>
> >>
> >>
>
> _______________________________________________
> Aximx30-port mailing list
> Aximx30-port_at_handhelds.org
> https://www.handhelds.org/mailman/listinfo/aximx30-port
>
>
Received on Wed Jun 29 2005 - 21:49:56 EDT