On Monday 05 June 2006 1:57 pm, Paul Serice wrote:
> I'm not sure why my email to and from the list is delayed, but I sent
> a corrected patch to the list almost two days ago that hasn't been
> posted yet. The reason for the correction is that I messed up my
> merge with HEAD (as caught by Pete Za
On Saturday 03 June 2006 12:17 am, Paul Serice wrote:
> The workaround in commit f7201c3dcd7799f2aa3d6ec427b194225360ecee
> broke. The work around requires memory for DMA transfers for some
> NVidia EHCI controllers to be below 2GB, but recent changes have
> caused the DMA memory to be allocated b
I'm not sure why my email to and from the list is delayed, but I sent
a corrected patch to the list almost two days ago that hasn't been
posted yet. The reason for the correction is that I messed up my
merge with HEAD (as caught by Pete Zaitcev). I accidentally I had
this in my patch:
-
> Wait a second, what about this part which you removed:
Your absolutely right. I was working with 2.6.16.18 which didn't have
that chunk of code, and I messed up the merge. I will resend the patch
with the correction.
Thanks,
Paul
___
linux-usb-d
The workaround in commit f7201c3dcd7799f2aa3d6ec427b194225360ecee
broke. The work around requires memory for DMA transfers for some
NVidia EHCI controllers to be below 2GB, but recent changes have
caused the DMA memory to be allocated before the DMA mask is set.
Signed-off-by: Paul Serice <[EMAIL
On Sat, 03 Jun 2006 02:17:48 -0500, Paul Serice <[EMAIL PROTECTED]> wrote:
> The workaround in commit f7201c3dcd7799f2aa3d6ec427b194225360ecee
> broke. The work around requires memory for DMA transfers for some
> NVidia EHCI controllers to be below 2GB, but recent changes have
> caused the DMA me
The workaround in commit f7201c3dcd7799f2aa3d6ec427b194225360ecee
broke. The work around requires memory for DMA transfers for some
NVidia EHCI controllers to be below 2GB, but recent changes have
caused the DMA memory to be allocated before the DMA mask is set.
Signed-off-by: Paul Serice <[EMAIL
