From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.161]) by ozlabs.org (Postfix) with ESMTP id E1EB267B77 for ; Sun, 3 Dec 2006 20:20:38 +1100 (EST) Date: Sun, 3 Dec 2006 10:13:41 +0100 (MET) From: Nicolas DET To: Sven Luther Subject: Re: [PATCH 1/2] Fixed compiled issue tu to new of_platform.h header Message-Id: <20061203101343.6ceda991.nicolas@det-net.org> In-Reply-To: <20061203082303.GA9129@powerlinux.fr> References: <1164403145.5653.93.camel@localhost.localdomain> <20061203082303.GA9129@powerlinux.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linux-usb-devel@lists.sourceforge.net, Greg KH , sl@bplan-gmbh.de, linuxppc-dev@ozlabs.org, Alan Stern List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 3 Dec 2006 09:23:03 +0100 S0ven Luther wrote: > > Not that I know. But we could have a cleaner approach. The #include one > > dates a bit... we could have for example an ohci-core.ko with the core > > bits, and ochi-pci.ko, ohci-patform.ko etc... be separate modules linked > > on the first and instanciating it. > > > > I'll have a look and will come up with either solution. > In my mind, this is the correct approch. > Hi, ... > > I am just wondering if i got dropped from the CCs or if there was no further > discussion on this. > > The 2.6.19 kernel doesn't build when the efika patches are applied and the > ohci modules are built. We need a solution for this. Even disabling the patch > for ohci fails to build the ohci driver, but this could be a bad manipulation. > "Efika OHCI patches" does not exist. There is a new OHCI glue for OpenFrimware. > Is there any hint on the right way to go for this ? > I'm currently running on 2.6.19 (the whole USB in kernel not kmod). It compiles and works fine. Regards.