From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.224]) by ozlabs.org (Postfix) with ESMTP id 792FFDDEC4 for ; Tue, 12 Jun 2007 02:06:26 +1000 (EST) Received: by nz-out-0506.google.com with SMTP id v1so1228001nzb for ; Mon, 11 Jun 2007 09:06:24 -0700 (PDT) Message-ID: Date: Mon, 11 Jun 2007 10:06:23 -0600 From: "Grant Likely" Sender: glikely@secretlab.ca To: "Stephen Neuendorffer" Subject: Re: a question for linux framebuffer driver In-Reply-To: <20070611160313.B1A36DA8056@mail207-sin.bigfish.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed References: <1316548361.5052161181391690811.JavaMail.coremail@bj163app129.163.com> <20070611160313.B1A36DA8056@mail207-sin.bigfish.com> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 6/11/07, Stephen Neuendorffer 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