From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from metis.extern.pengutronix.de (metis.extern.pengutronix.de [83.236.181.26]) by ozlabs.org (Postfix) with ESMTP id 125EDDDE17 for ; Thu, 25 Sep 2008 01:16:51 +1000 (EST) Received: from themisto.extern.pengutronix.de ([83.236.181.29] helo=jupiter.intranet.kreuzholzen.de) by metis.extern.pengutronix.de with esmtp (Exim 4.63) (envelope-from ) id 1KiW6X-0004Dr-3A for linuxppc-dev@ozlabs.org; Wed, 24 Sep 2008 17:16:43 +0200 From: Juergen Beisert To: linuxppc-dev@ozlabs.org Date: Wed, 24 Sep 2008 17:16:34 +0200 References: <200809221556.34353.jbe@pengutronix.de> <48D807C5.4070002@genesi-usa.com> <200809231334.19175.jbe@pengutronix.de> In-Reply-To: <200809231334.19175.jbe@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <200809241716.35285.jbe@pengutronix.de> Subject: Re: MPC5200 PCI interrupt routing List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Dienstag, 23. September 2008, Juergen Beisert wrote: > Matt, > > On Montag, 22. September 2008, Matt Sealey wrote: > > Juergen Beisert wrote: > > > Hi, > > > $ lspci > > > 00:18.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > > > Controller (rev 61) 00:18.1 USB Controller: VIA Technologies, Inc. > > > VT82xxxxx UHCI USB 1.1 Controller (rev 61) 00:18.2 USB Controller: VIA > > > Technologies, Inc. USB 2.0 (rev 63) > > > > > > USB driver (endianess???) or oftee or hardware problem? > > > > > > Anyone experience with VIA USB hardware on PowerPc? > > > > The USB driver should work fine, I have an Efika (MPC5200B) with that > > exact USB controller and revision and it's just fine and dandy. We also > > used to ship Via-based USB cards in the Pegasos Open Desktop Workstation > > (using Marvell Discovery II northbridge). > > > > The major difference here would be that PCI tree entries were created > > by a real OF implementation so may have reflected some hardware better; > > it is dynamically created on boot to a certain point, rather than a fix= ed > > device tree which may contain some "errors". There seems to be a lot le= ss > > data in our tree... > > What Kernel do you run on your target? On my hardware a 2.6.23 still work > as expected, but a 2.6.26 fails all the time. One should enable the internal USB clock. If done, it works... In 2.6.23 is= =20 was done in mpc52xx_common.c. It was removed in 2.6.24. Juergen =2D-=20 Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de =C2=A0Pengutronix - Linux Solutions for Science and Industry =C2=A0 Handelsregister: Amtsgericht Hildesheim, HRA 2686 =C2=A0 =C2=A0 =C2=A0 Vertretung Sued/Muenchen, Germany Phone: +49-8766-939 228 | Fax: +49-5121-206917-9