summaryrefslogtreecommitdiffstats
path: root/hw/net
diff options
context:
space:
mode:
authorLaurent Vivier <lvivier@redhat.com>2015-08-24 19:29:45 +0200
committerLaurent Vivier <lvivier@redhat.com>2015-09-25 14:52:17 +0200
commit9491e9bc019a365dfa9780f462984a0d052f4c0d (patch)
treea4d36d9ecda0e7f129ded20072e572bf9a141785 /hw/net
parent8a47d575dfac0f6675e2ac56c5921cc520d021a6 (diff)
downloadhqemu-9491e9bc019a365dfa9780f462984a0d052f4c0d.zip
hqemu-9491e9bc019a365dfa9780f462984a0d052f4c0d.tar.gz
i6300esb: remove muldiv64()
Originally, timers were ticks based, and it made sense to add ticks to current time to know when to trigger an alarm. But since commit: 7447545 change all other clock references to use nanosecond resolution accessors All timers use nanoseconds and we need to convert ticks to nanoseconds, by doing something like: y = muldiv64(x, get_ticks_per_sec(), PCI_FREQUENCY) where x is the number of device ticks and y the number of system ticks. y is used as nanoseconds in timer functions, it works because 1 tick is 1 nanosecond. (get_ticks_per_sec() is 10^9) But as PCI frequency is 33 MHz, we can also do: y = x * 30; /* 33 MHz PCI period is 30 ns */ Which is much more simple. This implies a 33.333333 MHz PCI frequency, but this is correct. Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Diffstat (limited to 'hw/net')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud