On Sunday, May 20, 2007, David Brownell
> On Sunday 20 May 2007, Pete Zaitcev wrote:
> > On Fri, 18 May 2007 14:23:43 -0700, "Mark Miesfeld" <[EMAIL PROTECTED]>
wrote:
> >
> > And this is the part which implements poking:
> >
> > > +++ b/drivers/usb/host/ohci-ppc-soc.c
> > > @@ -20,6 +20,37 @@ #
On Sunday, May 20, 2007, Pete Zaitcev wrote:
> On Sun, 20 May 2007 21:55:58 -0700, David Brownell
> <[EMAIL PROTECTED]> wrote:
>
> > If you're going to turn on the OHCI hardware, do it the
> > normal way; don't bypass its driver.
>
> How exactly do you suggest we do this?
>
> The problem is no
On Sunday, May 20, 2007, Pete Zaitcev wrote:
> On Fri, 18 May 2007 14:23:43 -0700, "Mark Miesfeld" <[EMAIL PROTECTED]> wrote:
>
> > There is a published errata for the PPC440EPX, USBH_23: EHCI and OHCI
> > Linux module contention.
>
> So, you're set for the classic (and unsoluble) inter-module
On Sun, 20 May 2007 21:55:58 -0700, David Brownell <[EMAIL PROTECTED]> wrote:
> If you're going to turn on the OHCI hardware, do it the
> normal way; don't bypass its driver.
How exactly do you suggest we do this?
The problem is not quite dissimilar to that of BIOS handoff. There,
we solved the
On Sunday 20 May 2007, Pete Zaitcev wrote:
> On Fri, 18 May 2007 14:23:43 -0700, "Mark Miesfeld" <[EMAIL PROTECTED]> wrote:
>
> And this is the part which implements poking:
>
> > +++ b/drivers/usb/host/ohci-ppc-soc.c
> > @@ -20,6 +20,37 @@ #include
> > /* always called with process context; sl
On Fri, 18 May 2007 14:23:43 -0700, "Mark Miesfeld" <[EMAIL PROTECTED]> wrote:
> There is a published errata for the PPC440EPX, USBH_23: EHCI and OHCI
> Linux module contention. The overview states: When running Linux with
> both EHCI and OHCI modules loaded, the EHCI module experiences a fatal
>
