--- In "Charlie Wallace" <> wrote:
THanks for the reply, Charlie, but it's still not clear.
Which is Peter's sample? There is a circle.c in the Example Code directory,
which is
identical to the circle_7kv.c I was referring to.
By 565, do you actually mean 6 bits of green resolution? I though that was the
best way to
use 16 bits, as the eye is most sensitive to colour in the green part of the
spectrum.
>
>
>
> > Is there any more documentation on the TS7KV than provided in
> > gs_ts7kv.pdf, Getting
> > Started with TS-7KV?
> >
> I used Peter Elliots sample on the archives of this group for some more info
>
> > Firstly, is it a 16 bit or 15 bit colour device? Are the lower 6 bits for
> > blue? Or is bit 6
> > (counting from 0) not used?
> >
>
> I'm using it as a 565 RGB on the TS7300, i can't find the transparency
> enable bit though if it exists in the 640x480 framebuffer driver. I had
> asked a few days ago but no luck so far. Its talked about in the 800x600
> driver but i can't find info on that either.
>
> > The circles program maps both regs and fb to the same address,
> > 0x2180_0000. It then uses
> > regs to set VIDCTRL, I think, and fb as a raw area of memory to address
> > pixels.
> >
>
> Its page flipped, there are 7 pages of video memory and you can set which
> one is displayed, and which one is writeable over the bus. there are two
> sets of 3 bits that control which is displayed and which is writeable
>
> > According to the document, VIDCTRL is BASE+8, or 0x2180_0008, but the
> > program sets regs
> > to 0x2180_0000 + 0x30 then references it as regs[4], which would be
> > 0x2180_0038. Whilst
> > using the same addresses as a frame buffer.
> >
> > What am I missing?
> >
>
> You're missing that the documents are in byte(8 bit) offsets, and that the
> software is in WORD(16 bits) addressing so in the manual +8 bytes equates to
> +4 words, since each register is a 16 bit entry. The 0x30 offset is correct
> too.
>
I'm still stuck on this. I understand C pointer and array addressing, so if
your pointer is
declared pointer to short int, p++ will increment it by 2 bytes. The bit I am
confused
about it, is where the same area, 0x21800000, is mmap'ed twice and used as if
one
instance (regs) refers to control registers, and the other instance (fb) is a
raw area of
shorts as the framebuffer.
And why is the 0x30 offset correct? I can't see any reference to it in the
docs. They say
BASE = 0x2180_0000 and VIDCTRL = BASE + 8. If you declared short int * BASE,
then
VIDCTRL would be BASE[4].
Admittedly my TS7KV hasn't arrived yet, but I have no expectation of it
arriving with better
documentation than the Getting Started PDF I have been referring to.
Thank in advance,
Martin
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|