LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "silicom" <silicom@163.com>, <linuxppc-embedded@ozlabs.org>
Subject: RE: a question for linux framebuffer driver
Date: Mon, 11 Jun 2007 09:03:11 -0700	[thread overview]
Message-ID: <20070611160313.B1A36DA8056@mail207-sin.bigfish.com> (raw)
In-Reply-To: <1316548361.5052161181391690811.JavaMail.coremail@bj163app129.163.com>


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

  reply	other threads:[~2007-06-11 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-09 12:21 a question for linux framebuffer driver silicom
2007-06-11 16:03 ` Stephen Neuendorffer [this message]
2007-06-11 16:06   ` Grant Likely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070611160313.B1A36DA8056@mail207-sin.bigfish.com \
    --to=stephen.neuendorffer@xilinx.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=silicom@163.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox