| Summary: | ASTERISK-01694: [patch] ztdummy driver for 2.6.x | ||
| Reporter: | Tony Hoyle wibble wibble wibble (tonyhoyle) | Labels: | |
| Date Opened: | 2004-05-26 10:06:58 | Date Closed: | 2004-09-25 02:40:21 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This rips out the depency on USB and uses a kernel timer. The timers on 2.6.x are much higher resolution than 2.4.x and this seems to be enough without extra synchronisation ****** ADDITIONAL INFORMATION ****** Patch is on http://www.nodomain.org/asterisk/ztdummy.diff | ||
| Comments: | By: Mark Spencer (markster) 2004-05-26 11:45:05 This would break ztdummy with 2.4 though, obviously... By: Tony Hoyle wibble wibble wibble (tonyhoyle) 2004-05-26 12:04:00 Yes...:) Perhaps it should be called something else (the alternative being to #ifdef the whole thing which would be a mess as they have little in common). By: Mark Spencer (markster) 2004-05-26 21:33:06 I can't reasonably put it in unless it works with both 2.4 and 2.6... What does the new kernel use for a timer? Is it really 1000 Hz? I thought you could only get multiples of 2 hz off the PC timer... Try running "zttest" when you get a chance using your new code and let me know what numbers it gives you. By: Tony Hoyle wibble wibble wibble (tonyhoyle) 2004-05-27 07:12:48 --- Results after 14 passes --- Best: 99.975586 -- Worst: 99.975586 If you don't want it in that's fine I can just host it on my website... some people have asked for it but I realize the majority of * users are probably on 2.4 at the moment. By: Mark Spencer (markster) 2004-05-30 01:33:58 Actually 99.97 isn't terrible. I bet it's at least as good as the uhci one. My tor2 on an 800 Mhz pentium only gets 99.987. If you can supply a patch that will #ifdef LINUX26 the right behavior i'll be happyt o merge it. By: Tony Hoyle wibble wibble wibble (tonyhoyle) 2004-05-31 17:37:52 This version uses either ztdummy24.c or ztdummy26.c depending on the platform - (the output is still ztdummy.o/ztdummy.ko). I tried with a single file using #ifdef and this seems cleaner, since the only code they share really is about half a dozen lines. By: bk (bk) 2004-06-17 19:28:19 The ifdef/else at the bottom of ztdummy.c needs a sex change. By: wsuff (wsuff) 2004-06-21 13:41:12 from dmesg ztdummy: Unknown symbol fill_td ztdummy: Unknown symbol insert_td_horizontal ztdummy: Unknown symbol uhci_devices ztdummy: Unknown symbol uhci_interrupt ztdummy: Unknown symbol alloc_td ztdummy: Unknown symbol unlink_td ztdummy: Unknown symbol delete_desc hmm don't see why ztdummy doesn't like me. Compiles fine but errors when i modprobe it By: bk (bk) 2004-06-21 15:50:46 Take a look at the ifdef at the bottom of ztdummy.c You are building a 2.4 and trying to load it on 2.6. As I said before, the ifdef needs a sex change. By: wsuff (wsuff) 2004-06-21 16:09:16 Thanks. Works nicely now By: Mark Spencer (markster) 2004-06-26 16:56:42 Merged into CVS | ||