[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uclinux-dev
Subject:    Re: [uClinux-dev] framebuffer for a MCF5272C3 with CRT
From:       "nafiton smith" <jose.ferreiro () horushardware ! com>
Date:       2003-05-29 13:19:19
[Download RAW message or body]

Hello again

----- Original Message ----- 
From: "nafiton smith" <jose.ferreiro@horushardware.com>
Sent: Wednesday, May 28, 2003 7:41 PM


> Hello Heiko
>
> ----- Original Message ----- 
> From: "Heiko Degenhardt" <heiko.degenhardt@sentec-elektronik.de>
> Sent: Tuesday, May 27, 2003 2:00 PM
>
>
> > Hi Nafiton,
> >
> > * On Tue, May 27, 2003 at 12:19:00PM +0200, nafiton smith wrote:
> > > I think I explain myself badly. What I meant is that I can read/write
the
> > > video memory directly accesing to physical address. I didnīt try to do
this
> > > through the framebuffer yet.
> > > However cat /proc/fb shows:
> > > 0 s1d13xxx
> >
> > That seems to be the ID of your framebuffer for framebuffer 0 (but
> > imho you should/could change the ID to s1d13806 or something).
> > I could send you my driver for the 13806, too, if you like
> > (though it's currently not tested that deep. But it works on
> > our board).
> >
> > > I think to read/write through the fb, first I must generate a
> > > /dev/fb0
> >
> > Yes.
> >
> > > with the mknod instruction. I am looking for a way to activate
> > > this at uclinux also.
> >
> > Have a look at vendors/senTec/COBRA5272/Makefile in the newest
> > dist (or in cvs).
> >
>
> It was easy ... after I look at it directly ;o)
>
> I downloaded the new dist and recompiled the kernel with microwindows
> activated.
> I had some problems with mw because the ARCH variable took  a value of
> m68knommu and the Makefile files didnīt put the right tools with that
value.
> Perhaps I missed something. At the end,  I decided to add the prefix tools
> manually.
>
> I have now the uclinux kernel running. The device /dev/fb0 exists and the
> 'cat /proc/fb' command shows:
> 0 s1d13806
> but if I try to do a 'cp /dev/fb0 /var/myfile' I get a 'bad format frame'
> exception.
> I f I try to run the nano-X server, it crash with the same exception.
>
> I suppose it is so because I am using the epson driver almost as I
> downloaded it. I can see your 13706 driver have important changes. Can you
> send me your LCD 13806 driver? I  will take it as a more direct reference
to
> make my CRT work. In the meantime I will begin to change the epson 13806
> driver to make it more similar to yours.
>

After I changed my driver, the exception keep going. I traced it to the
memcpy function. It had resulted to be a hardware problem: my graphical
board has a 16 bits data bus. When I try to manage the video memory access
with WAIT signal, I must have done some error. I am trying to resolve it.

Until then, I set up a fixed number of WAIT states on the CS for the13806.
With this configuration I can do the copy to and from /dev/fb0. nano-X does
not start .... yet :o)  It gives me a 'no driver for screen ...' message

thank you,
nafiton


_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
[prev in list] [next in list] [prev in thread] [next in thread]