LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: a question for linux framebuffer driver
Date: Mon, 11 Jun 2007 10:06:23 -0600	[thread overview]
Message-ID: <fa686aa40706110906p2de5c4e3i108d67dc1fd411de@mail.gmail.com> (raw)
In-Reply-To: <20070611160313.B1A36DA8056@mail207-sin.bigfish.com>

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

      reply	other threads:[~2007-06-11 16:06 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
2007-06-11 16:06   ` Grant Likely [this message]

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=fa686aa40706110906p2de5c4e3i108d67dc1fd411de@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=stephen.neuendorffer@xilinx.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