[okl4-developer] vLCD Server: virtual_lcd_set_fb_impl

[Geoffrey Lee]

On Thu, Jul 10, 2008 at 02:42:26PM +0200, Lukas HANEL wrote:
> Hi,

Hi Lukas

> 
> in my quest to port an LCD driver to OKL4 I have now passed the
> initialization of my driver code. I am now at the point, where the vlcd
> client provides the physical memory region to the fb. In the vlcd-server
> the function
> > new_paddr = memsection_virt_to_phys(new_vaddr, &new_size);
> returns an error value.
> 
> What to do?

How did you obtain the new_vaddr address?  Is it an address previously
created using the memsection APIs?  If so which one?


> 
> First of all, I extended the drivers example with the code provided by
> the driver porting tutorial. What seems odd to me is, that a client
> virtual address is transfered via IPC to the server. Afterwords, the
> function
> > iguana_memsection_virt_to_phys_impl
> returns with
> > interfaces = security_check(thread_lookup(_caller)->owner, 
> (uintptr_t)ms);
> > if (interfaces == L4_NoAccess){
> >        return -2;
> >    }
> 


As Iguana by default provides the concept of a single address space,
the memory objects as they appear in that single address space
is consistent across all programs running in the system.  Protection
is enforced by the MMU.  It is hence OK to pass the virtual address
around.

> What should I do? In how far is the current code for vlcd server + some
> client(okl4-2.1) running?
> 

The code for vLCD server should compile, as it is in the standard
distribution for the GTA01 board.  There may be minor things that
need updating, however.


> thanks,
> Lukas Hänel

	-gl

> 
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

--