Markus Rechberger a écrit : > On 9/10/07, David & Anne-Sophie <[EMAIL PROTECTED]> wrote: > >> David & Anne-Sophie a écrit : >> >>> Hello all, >>> I am trying to use my hybrid USB tuner on my NSLU2. >>> Tuner=Terratec cinergy XS >>> Driver=http://mcentral.de/wiki/index.php/Em2880 >>> I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB >>> hard-disk that contains the filesystems. >>> >>> The driver compiles fine on the standard debian etch kernel, and loads >>> perfectly. >>> I just did a minor patch of this driver around a udelay(2500); -> >>> udelay(2000);udelay(500); (2500 is a too big value for the ARM >>> architecture, see bad_udelay). >>> >>> When I try tzap to activate the dvb-t stream, I get those errors: >>> ehci_hcd 0000:00:01.2: alloc_safe_buffer: could not alloc dma memory >>> (size=36096) >>> ehci_hcd 0000:00:01.2: map_single: unable to map unsafe buffer ffc2c000! >>> many times (I think one per USB packet). >>> And the tuner does not stream anything... >>> >>> I did not modify anything in the NSLU2 (neither RAM or frequency), just >>> upgraded to debian etch arm architecture following the nslu2-linux.org >>> tutorials. >>> Do you know what it means and how to solve the issue? >>> Do not hesitate to ask for specific information. >>> >>> Thanks! >>> Cheers, >>> David. >>> [EMAIL PROTECTED] >>> >>> >>> >>> _______________________________________________ >>> Em28xx mailing list >>> Em28xx@mcentral.de >>> http://mcentral.de/mailman/listinfo/em28xx >>> >>> >>> >>> >> I have some informations that can help you to resolve my problem. These >> informations comes from the newlist of debian-arm : >> In this forum, I said that the driver works correctly on a PC with >> ubuntu, and the response is : >> "Working on a PC does not mean the driver is correct. On a PC physical >> addresses match the kernel's point of view in general, while on the arm >> everything goes through interesting mappings, which make is essential >> for the driver to correctly use readX/writeX calls along with ioremap >> calls. Any attemps to directly access anything will fail on the arm >> while it almost always works on a PC. Not sure quite how that might >> impact a USB device, but even there the driver has to do DMA setup with >> corrected addresses, which again is not necesary on a PC but is on the >> arm. " >> >> > > i'm at the suse conference this week there are some interesting people > around who're into the usb subsystem. > The em28xx driver makes use of the usb subsystem (which also includes > allocation of memory) > I'll try to get some answers tomorrow about this issue. > > Markus > > > Hello Markus,
Do you have news about my problem ? Thanks David _______________________________________________ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
