On Tue, 10 Feb 2015, Michael Tessier wrote:
> > > Okay; I did my homeworks. We've loaded kernel V3.16 (Oct 14th, 2015)
> > > on an i.MX51 plattform and the problem is still there. Unless an
> > > important change occured in V3.19, it appears that the latest kernel
> > > is not the solution for
> > Okay; I did my homeworks. We've loaded kernel V3.16 (Oct 14th, 2015)
> > on an i.MX51 plattform and the problem is still there. Unless an
> > important change occured in V3.19, it appears that the latest kernel
> > is not the solution for us. So we're still not able to use 4 codecs on
> > o
On Mon, 9 Feb 2015, Michael Tessier wrote:
> Okay; I did my homeworks. We've loaded kernel V3.16 (Oct 14th, 2015)
> on an i.MX51 plattform and the problem is still there. Unless an
> important change occured in V3.19, it appears that the latest kernel
> is not the solution for us. So we're still n
> > > > > > That is interresting, however, I have an older kernel running
> > > > > > an OHCI driver which is able to handle 4 codecs. Same usb
> > > > > > hardware (codecs and hub), but older kernel on a different
> > > > > > CPU, with much less power. This makes me believe that there's a
> >
On Wed, Jan 7, 2015 at 2:22 AM, Alan Stern wrote:
> On Tue, 6 Jan 2015, Michael Tessier wrote:
>
>> > > > > That is interresting, however, I have an older kernel running an
>> > > > > OHCI driver which is able to handle 4 codecs. Same usb hardware
>> > > > > (codecs and hub), but older kernel on a
On Tue, 6 Jan 2015, Michael Tessier wrote:
> > > > > That is interresting, however, I have an older kernel running an
> > > > > OHCI driver which is able to handle 4 codecs. Same usb hardware
> > > > > (codecs and hub), but older kernel on a different CPU, with much
> > > > > less power. This m
> > > > That is interresting, however, I have an older kernel running an
> > > > OHCI driver which is able to handle 4 codecs. Same usb hardware
> > > > (codecs and hub), but older kernel on a different CPU, with much
> > > > less power. This makes me believe that there's a solution to make it
> > If sound is ok when using only 1 codec and becomes choppy when adding
> > a second codec, then it means that this issue is still in the 3.x
> > kernel. This answer will tell me if it is worth working on using a newer
> > kernel or not.
> > I have to say that I'm not a linux expert, so I see
On Tue, 6 Jan 2015, Michael Tessier wrote:
> > > That is interresting, however, I have an older kernel running an OHCI
> > > driver which is able to handle 4 codecs. Same usb hardware (codecs and
> > > hub), but older kernel on a different CPU, with much less power. This
> > > makes me believe
> > > > Hi,
> > > >
> > > > I am dealing with a USB EHCI driver bug. Here is the info:
> > > >
> > > > My configuration:
> > > > -
> > > >
> > > > Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host
> > > > controller) Linux kernel: 2.6.31, using EHCI USB driver
> > >
> > >
On Mon, Jan 5, 2015 at 1:12 PM, Michael Tessier
wrote:
> If sound is ok when using only 1 codec and becomes choppy when adding a
> second codec, then it means that this issue is still in the 3.x kernel. This
> answer will tell me if it is worth working on using a newer kernel or not.
> I have to
On Mon, 5 Jan 2015, Michael Tessier wrote:
> > > Hi,
> > >
> > > I am dealing with a USB EHCI driver bug. Here is the info:
> > >
> > > My configuration:
> > > -
> > >
> > > Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
> > > Linux kernel: 2.6.31, using E
>
> On Mon, 15 Dec 2014, Michael Tessier wrote:
>
> > Hi,
> >
> > I am dealing with a USB EHCI driver bug. Here is the info:
> >
> > My configuration:
> > -
> >
> > Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
> > Linux kernel: 2.6.31, using EHCI USB driv
On Mon, 15 Dec 2014, Michael Tessier wrote:
> Hi,
>
> I am dealing with a USB EHCI driver bug. Here is the info:
>
> My configuration:
> -
>
> Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
> Linux kernel: 2.6.31, using EHCI USB driver
As mentioned by othe
>>
>> My configuration:
>> -
>>
>> Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
>> Linux
>> kernel: 2.6.31, using EHCI USB driver
>> Hub: 4-PORT USB 1.1 HUB (Texas Instruments PN: tusb2046b)
>> Devices: 4 USB 1.1 audio codecs (Texas Instruments PN: pcm2901
>
> My configuration:
> -
>
> Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller) Linux
> kernel: 2.6.31, using EHCI USB driver
> Hub: 4-PORT USB 1.1 HUB (Texas Instruments PN: tusb2046b)
> Devices: 4 USB 1.1 audio codecs (Texas Instruments PN: pcm2901)
>
> Not
On Mon, Dec 15, 2014 at 6:53 PM, Michael Tessier
wrote:
> Before attempting to upgrade to an earlier kernel driver (this is
> a fairly big amount of work), I would really like to know if this
> problem would still be in the 3.x kernels. Has anyone seen that
> issue in 3.x kernels?
In fact it is
On Mon, Dec 15, 2014 at 08:53:20PM +, Michael Tessier wrote:
> <5>Linux version 2.6.31-770-g0e46b52-0897
> (michael.tess...@vsvr-compile-01.pocatec.com) (gcc version 4.1.2) #12 PREEMPT
> Mon Nov 24 18:34:19 EST 2014
That is a _very_ old and obsolete kernel version, you need to get
support fr
18 matches
Mail list logo
