summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authortzafrir <tzafrir@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2008-01-08 21:38:53 +0000
committertzafrir <tzafrir@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2008-01-08 21:38:53 +0000
commitff8f331457d228145dd50da5293b7ec449e95463 (patch)
tree944df0f4c0bac7b2b4355d40dc7dc075575e812e /README
parenteb3c91a69f0068e22ec515705eab97bcb8a3a7d8 (diff)
Documentation updates.
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3626 5390a7c7-147a-4af0-8ec9-7488f05a26cb
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 8 insertions, 4 deletions
diff --git a/README b/README
index 0641d73..a62302b 100644
--- a/README
+++ b/README
@@ -96,16 +96,20 @@ If you build a custom kernel, note the following configuration items:
- CONFIG_CRC_CCITT must be enabled ('y' or 'm'). On 2.6 kernels this can
be selected These can be selected from the "Library Routines" submenu
during kernel configuration via "make menuconfig".
-- If you don't have any zaptel hardware, you need ztdummy.
+- If you don't have any zaptel hardware, you need ztdummy. ztdummy takes
+ its timing from the kernel. It can use either of the following:
* ztdummy on i386/x86_64 with kernels >= 2.6.22 can (and should) use
high resolution times (CONFIG_HIGH_RES_TIMERS), and (if available,
- the system HPET.
+ the system HPET. This shows as "source: HRTimer". This is
+ recommended.
* ztdummy on i386/x86_64 and later kernels (>= 2.6.15) can use the
- system's RTC (Real Time Clock).
+ system's RTC (Real Time Clock). This shows as "source: RTC".
+ * Failing that, on Linux 2.6 kernels with HZ=1000 (was the default
+ before 2.6.13). This shows as "source: Linux26".
* Alternatives to that for ztdummy are a UHCI USB controller (USB
controllers made by Intel or VIA) or a kernel that has HZ=1000
(default on kernels 2.6.0-2.6.12, optional on newer kernels. Not
- possible on 2.4).
+ possible on 2.4). This shows as: "source: UHCI".
A Build System