From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m13-129.163.com (m13-129.163.com [220.181.13.129]) by ozlabs.org (Postfix) with SMTP id 3F924DDF91 for ; Sat, 9 Jun 2007 22:38:40 +1000 (EST) Date: Sat, 9 Jun 2007 20:21:30 +0800 (CST) From: silicom To: linuxppc-embedded@ozlabs.org Message-ID: <1316548361.5052161181391690811.JavaMail.coremail@bj163app129.163.com> Subject: a question for linux framebuffer driver MIME-Version: 1.0 Content-Type: multipart/Alternative; boundary="----=_Part_502267_1006930903.1181391690810" List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_502267_1006930903.1181391690810 Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 7bit 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? ------=_Part_502267_1006930903.1181391690810 Content-Type: text/html; charset=gbk Content-Transfer-Encoding: quoted-printable
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 fr= amebuffer not registered yet, no devices founded(but I have connected the m= onitor). I want to know when will xilinxfb_drv_probe be called?
 
 
 


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 ------=_Part_502267_1006930903.1181391690810--