a question for linux framebuffer driver

a question for linux framebuffer driver

[silicom]

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

Hello,
Now I'm porting framebuffer driver for ml403 in linux 2.6.17.1, but I find after registering the driver using driver_register function in xilinxfb_int, the xilinxfb_drv_probe function has not been called, so framebuffer not registered yet, no devices founded(but I have connected the monitor). I want to know when will xilinxfb_drv_probe be called?
   

[-- Attachment #2: Type: text/html, Size: 720 bytes --]

RE: a question for linux framebuffer driver

[Stephen Neuendorffer]

The kernel has to be informed of the device itself using =
platform_device_register.
I believe in the kernel you have you'll have to add code to do this, and =

/arch/ppc/platforms/4xx/virtex.c is a reasonable place.=20

Steve

> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org
> =20
> [mailto:linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@oz
> labs.org] On Behalf Of silicom
> Sent: Saturday, June 09, 2007 5:22 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: a question for linux framebuffer driver
>=20
> Hello,
> Now I'm porting framebuffer driver for ml403 in linux=20
> 2.6.171, but I find after registering the driver using=20
> driver_register function in xilinxfb_int, the=20
> xilinxfb_drv_probe function has not been called, so=20
> framebuffer not registered yet, no devices founded(but I have=20
> connected the monitor). I want to know when will=20
> xilinxfb_drv_probe be called?
>=20
> =20
> =20
> =20
>=20
>=20
> ________________________________
>=20
> 150 =CD=F2 =C8=CB =CD=AC =CA=B1 =D4=DA =CD=E6 =B5=C4 =CD=F8 =
=D3=CE=A3=AC=C4=E3 =B2=BB =CA=D4 =CA=D4 =C2=F0 =A3=BF=20
> <http://event.mail.163.com/chanel/xyq.htm?from=3D163_NO1>=20
>=20

Re: a question for linux framebuffer driver

[Grant Likely]

On 6/11/07, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
>
> The kernel has to be informed of the device itself using platform_device_register.
> I believe in the kernel you have you'll have to add code to do this, and
> /arch/ppc/platforms/4xx/virtex.c is a reasonable place.

In more recent kernels, look at arch/ppc/syslib/virtex_devices.c

g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195