Clemens Ladisch wrote:
Busy means that it's there, but already being used. Many motherboard
BIOSes do not initialize the third HPET interrupt, and the first two are
taken by the kernel.
I would like to make a test song using HR timer, but unfortunately I'm
not able to close a project and
Ralf Mardorf wrote:
Clemens Ladisch wrote:
Busy means that it's there, but already being used. Many motherboard
BIOSes do not initialize the third HPET interrupt, and the first two are
taken by the kernel.
I would like to make a test song using HR timer, but unfortunately I'm
hollun...@gmx.at wrote:
hollun...@gmx.at wrote:
It seems I needed to modprobe snd-hrtimer
Now oom pretty much freezes as well when I tell it to use that,
Does oom or the entire system freeze?
Haven't tried this yet since I'm not sure it makes sense:
chgrp audio /dev/hpet
So even
On Tue, 10 Nov 2009 10:03:34 +0100
Clemens Ladisch clem...@ladisch.de wrote:
hollun...@gmx.at wrote:
hollun...@gmx.at wrote:
It seems I needed to modprobe snd-hrtimer
Now oom pretty much freezes as well when I tell it to use that,
Does oom or the entire system freeze?
In my case the
Thanks Clemens,
you wrote in an unrelated thread:
dmesg | grep -i hpet
I wasn't clever enough to use -i (ignore case) when I checked whether
hpet=force worked.
$ dmesg | grep -i hpet
Kernel command line:
root=/dev/disk/by-uuid/3e47466f-5ca1-499b-85fc-152074f36364 ro hpet=force
pci
hollun...@gmx.at wrote:
$ dmesg | grep -i hpet
Kernel command line:
root=/dev/disk/by-uuid/3e47466f-5ca1-499b-85fc-152074f36364 ro hpet=force
pci :00:11.0: Failed to force enable HPET
/dev/hpet was still created,
Then you have it. The message is probably because it doesn't need
to
On Tue, 10 Nov 2009 12:48:42 +0100
Clemens Ladisch clem...@ladisch.de wrote:
hollun...@gmx.at wrote:
$ dmesg | grep -i hpet
Kernel command line:
root=/dev/disk/by-uuid/3e47466f-5ca1-499b-85fc-152074f36364 ro
hpet=force pci :00:11.0: Failed to force enable HPET
/dev/hpet was
Since hrtimer uses hpet if available and apps use hrtimer, why would I
need to allow some audio group to access hpet directly?
Because it offers memory-mappable access to the actual timer hardware,
significantly lowering overhead and latency for reading the value.
This system has no
On Tue, Nov 10, 2009 at 07:53:19PM +0200, Jussi Laako wrote:
Brokenness is that JACK is not interested on those sub-timers and the
driver should allocate those only via corresponding ioctl() and give
unlimited read access to the global timer value without failing early...
If hpet services are
On Tue, Nov 10, 2009 at 1:06 PM, f...@kokkinizita.net wrote:
On Tue, Nov 10, 2009 at 07:53:19PM +0200, Jussi Laako wrote:
Brokenness is that JACK is not interested on those sub-timers and the
driver should allocate those only via corresponding ioctl() and give
unlimited read access to the
On Tue, Nov 10, 2009 at 1:33 PM, f...@kokkinizita.net wrote:
What I don't see is how e.g. MIDI generators can use it
in this way to get accurate event timing. Either they are
spinning (evil), or they'd need a system call anyway, and
it that case they should use kernel services instead.
On Tue, Nov 10, 2009 at 3:58 PM, f...@kokkinizita.net wrote:
All perfectly logical. But what then is stopping the driver devs
from providing just read access to the main counter ? Who could
object to read-only access to a device register (if reading it
has no side effects) ?
probably
Thanx to everybody :). JACK can use hpet and hrtimer is available in
Qtractors options :).
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
On Mon, 9 Nov 2009 17:43:12 +0100
hollun...@gmx.at wrote:
On Mon, 9 Nov 2009 16:47:07 +0100
hollun...@gmx.at wrote:
On Mon, 09 Nov 2009 16:40:41 +0100
Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
Emanuel Rumpf wrote:
Opening the hr-timer with rosegarden freezes my whole system
2009/11/10 hollun...@gmx.at
On Mon, 9 Nov 2009 17:43:12 +0100
hollun...@gmx.at wrote:
On Mon, 9 Nov 2009 16:47:07 +0100
hollun...@gmx.at wrote:
On Mon, 09 Nov 2009 16:40:41 +0100
Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
Emanuel Rumpf wrote:
Opening the hr-timer
On Sat, Nov 07, 2009 at 02:42:56PM +0100, Ralf Mardorf wrote:
spinymouse-s...@64studio:~$ ll /dev/hpet
bash: ll: command not found
See below.
spinymouse-s...@64studio:~$ ls /dev | grep hpet
hpet
Useless Use Of Pipe.
spinymouse-s...@64studio:~$ cat /boot/config-2.6.29-1-multimedia-amd64
2009/11/8 Ray Rashif schivmeis...@gmail.com
2009/11/8 Adrian Knoth a...@drcomp.erfurt.thur.de
On Sat, Nov 07, 2009 at 02:42:56PM +0100, Ralf Mardorf wrote:
spinymouse-s...@64studio:~$ ll /dev/hpet
bash: ll: command not found
See below.
spinymouse-s...@64studio:~$ ls /dev | grep hpet
On Sun, Nov 8, 2009 at 2:46 PM, Ray Rashif schivmeis...@gmail.com wrote:
2009/11/8 Adrian Knoth a...@drcomp.erfurt.thur.de
[...]
[0] http://en.wikipedia.org/wiki/Cat_%28Unix%29#Useless_use_of_cat
Holy shit, wait, is that one a demonstration of a useless use of reply in
e-mail? Good one!
Hi
I'm confused about all the timers.
There is:
- system timer
- hpet (high precision event timer)
- hr-timer (high resolution timer)
- rtc (real time clock)
- cyclic (what's that? a coded loop?)
- anything else ?
What is the relation of all these ?
Which hardware devices are actually used by
Emanuel Rumpf wrote:
Hi
I'm confused about all the timers.
There is:
- system timer
- hpet (high precision event timer)
- hr-timer (high resolution timer)
- rtc (real time clock)
- cyclic (what's that? a coded loop?)
- anything else ?
What is the relation of all these ?
Which
: Re: [LAD] timers
To: Emanuel Rumpf xb...@web.de
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 7:04 AM
Emanuel Rumpf wrote:
Hi
I'm confused about all the timers.
There is:
- system timer
- hpet (high precision event timer)
- hr-timer (high resolution
:
From: James Warden warj...@yahoo.com
Subject: Re: [LAD] timers
To: Emanuel Rumpf xb...@web.de, Ralf Mardorf
ralf.mard...@alice-dsl.net
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 7:34 AM
Hi guys,
Here is what I have:
$ cat /proc/asound/timers
G0
Warden warj...@yahoo.com
Subject: Re: [LAD] timers
To: Emanuel Rumpf xb...@web.de, Ralf Mardorf
ralf.mard...@alice-dsl.net
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 7:34 AM
Hi guys,
Here is what I have:
$ cat /proc/asound/timers
G0: system timer
| grep timer
snd_hrtimer 2148 0 ## not used
snd_timer 17408 3 snd_hrtimer,snd_seq,snd_pcm
J.
--- On Sat, 11/7/09, James Warden warj...@yahoo.com wrote:
From: James Warden warj...@yahoo.com
Subject: Re: [LAD] timers
To: Emanuel Rumpf xb...@web.de, Ralf
is not set
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_HRTIMER=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
J.
--- On Sat, 11/7/09, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
From: Ralf Mardorf ralf.mard...@alice-dsl.net
Subject: Re: [LAD] timers
To: James Warden warj...@yahoo.com
Cc: Emanuel
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_HRTIMER=m
and forgot about it :)
J.
--- On Sat, 11/7/09, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
From: Ralf Mardorf ralf.mard...@alice-dsl.net
Subject: Re: [LAD] timers
To:
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 8:52 AM
James Warden wrote:
Ralf,
It depends
yeps, forgot to copy this part of the config here, thanks :)
J.
--- On Sat, 11/7/09, Ray Rashif schivmeis...@gmail.com wrote:
From: Ray Rashif schivmeis...@gmail.com
Subject: Re: [LAD] timers
To: Linux Audio Developers linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 8
is using hr-timer by
default. I wrote this script quite some time ago and forgot about it :)
J.
--- On Sat, 11/7/09, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
From: Ralf Mardorf ralf.mard...@alice-dsl.net
Subject: Re: [LAD] timers
To:
Cc: linux-audio-dev@lists.linuxaudio.org
Date
: Re: [LAD] timers
To: James Warden warj...@yahoo.com
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 8:57 AM
Thank you very much James and Ray
:).
Ralf
James Warden wrote:
yeah, I have added a few things in a startup script.
Among other things, I have
2009/11/7 James Warden warj...@yahoo.com:
You can read more at
http://en.wikipedia.org/wiki/High_Precision_Event_Timer
Thanks for your interrest.
I found some kernel docu:
http://www.mjmwired.net/kernel/Documentation/timers/
And:
http://lwn.net/Articles/167897/
Looks like HPET and RTC are
On Sat, Nov 7, 2009 at 2:51 PM, Emanuel Rumpf xb...@web.de wrote:
Looks like HPET and RTC are hardware devices, where HPET is meant
to be superior and replace the RTC.
correct, to a large extent.
I still don't get: What is the HR-timer ?
I mean how does it compare to the HPET ?
When to
ralf.mard...@alice-dsl.net
Subject: Re: [LAD] timers
To: Paul Davis p...@linuxaudiosystems.com, Emanuel Rumpf
xb...@web.de, James Warden warj...@yahoo.com
Cc: linux-audio-dev@lists.linuxaudio.org
Date: Saturday, November 7, 2009, 4:40 PM
Summarized:
I guess my mobo supports hpet :).
$ dmesg
33 matches
Mail list logo
