Re: HEADSUP: pca driver being retired.
On Wed, Aug 13, 2003 at 11:02:23AM +0200, Poul-Henning Kamp wrote: I plan to remove the pca driver in about a week. Protest only from actual users respected. Not really 'actual', only 'old'. A lot of time ago I sent a message about lost speaker (IIRC) because having both devive in the kernel (pca and speaker) hide the second. Don't really remember the thread. (or maybe a PR? it was on early 2002, I found only this pointer: http://www.gufi.org/ricerca.php3?mode=showid=freebsd:current:15870) # pca: PCM audio through your PC speaker ## :-( device pca # it break speaker At that time I removed pca and never tryed to re-add. This is just a 'bye-bye pca :'-( -- Riccardo. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
On Thu, 14 Aug 2003, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Mark Murray wr ites: Would it be a useful exercise for the minority(?) of users who use this driver to either see if it can be effectively newbussed or turned into a port or both? The main problem is the code which hi-jacks the i8254 and kicks off up to 2 interrupts per second. What problem is this, except that 2 interrupts per second is too small for current hardware? Hmm, use of the interrupts has been broken in -current by incompletely turning clkintr() into a fast interrupt handler. pcaintr() is not a fast interrupt handler, but clkintr() just calls it if pca is active. pca uses splhigh() for locking, but splhigh is null in -current and doesn't lock out fast interrupts anyway. If pca were locked by Giant, then the large interrupt latency of Giant would show up as large distortion. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
Mark Murray wrote: I see considerable scope for an infrastructure that would allow drivers to be ports. _Easily_. This is a good idea. I think if this infrastructure already existed, then many people would make their drivers into ports. Until then, though, the drivers will likely have to be part of the kernel. Would it be a useful exercise for the people who want drivers to be ports instead of being in the kernel to provide this facility for driver writers to use? 8^p. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
On Friday 15 August 2003 16:45, Terry Lambert wrote: Mark Murray wrote: I see considerable scope for an infrastructure that would allow drivers to be ports. _Easily_. This is a good idea. I think if this infrastructure already existed, then many people would make their drivers into ports. Until then, though, the drivers will likely have to be part of the kernel. Would it be a useful exercise for the people who want drivers to be ports instead of being in the kernel to provide this facility for driver writers to use? See comms/ltmdm, x11/nvidia-driver, audio/aureal-kmod, comms/mwavem etc.. They already build fine.. The problem I find is that when you update your kernel the port doesn't get rebuilt, so reasonably often this results in your machine going *boom* when the port loads its module. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
On Wed, 13 Aug 2003, Julian Elischer wrote: Well I'm not too happy about this.. It's the only audio I have on my TI-810 laptop. That is however not running -current yet. I'm also not pleased from the perspective that this is the only major example in the tree of how to use the clock-speedup code in i386/isa/clock.c. A very nice piece of functionality I use quite often. I use pca only to exercise the clock-speedup code. I use the clock (interrupt) speedup code mainly for generating interrupt load for stress testing. I could easily replace this by a sysctl. [Context lost to top posting.] Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
In message: [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: : In message [EMAIL PROTECTED], Mark Murray wr : ites: : : Would it be a useful exercise for the minority(?) of users who use this : driver to either see if it can be effectively newbussed or turned into : a port or both? : : The main problem is the code which hi-jacks the i8254 and kicks off : up to 2 interrupts per second. That sounds lame, even as a port Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
Well I'm not too happy about this.. It's the only audio I have on my TI-810 laptop. That is however not running -current yet. I'm also not pleased from the perspective that this is the only major example in the tree of how to use the clock-speedup code in i386/isa/clock.c. A very nice piece of functionality I use quite often. What is youir reason for shooting a working piece of code? (well it works in 4.x.. I haven't tried it in 5.x?) (other than it offends you in some way) On Wed, 13 Aug 2003, Poul-Henning Kamp wrote: I plan to remove the pca driver in about a week. Protest only from actual users respected. If you don't know what pca is or what it does, do not even send email. Thank you! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
In message [EMAIL PROTECTED], Mark Murray wr ites: Would it be a useful exercise for the minority(?) of users who use this driver to either see if it can be effectively newbussed or turned into a port or both? The main problem is the code which hi-jacks the i8254 and kicks off up to 2 interrupts per second. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
In the last episode (Aug 13), Julian Elischer said: Well I'm not too happy about this.. It's the only audio I have on my TI-810 laptop. That is however not running -current yet. I'm also not pleased from the perspective that this is the only major example in the tree of how to use the clock-speedup code in i386/isa/clock.c. A very nice piece of functionality I use quite often. It's also handy if you don't have external speakers hooked up to a machine, and want something better than beeps. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: pca driver being retired.
I plan to remove the pca driver in about a week. Protest only from actual users respected. If you don't know what pca is or what it does, do not even send email. Thank you! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
It's also handy if you don't have external speakers hooked up to a machine, and want something better than beeps. Would it be a useful exercise for the minority(?) of users who use this driver to either see if it can be effectively newbussed or turned into a port or both? i'd quite like to see it reimplemented as a pcm driver; it's been on the todo list for years and should be quite simple. pca at present supports a very limited subset of the oss interface, where as a pcm driver it would behave the same as any other sound device. -cg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP: pca driver being retired.
Dan Nelson writes: In the last episode (Aug 13), Julian Elischer said: Well I'm not too happy about this.. It's the only audio I have on my TI-810 laptop. That is however not running -current yet. I'm also not pleased from the perspective that this is the only major example in the tree of how to use the clock-speedup code in i386/isa/clock.c. A very nice piece of functionality I use quite often. It's also handy if you don't have external speakers hooked up to a machine, and want something better than beeps. Would it be a useful exercise for the minority(?) of users who use this driver to either see if it can be effectively newbussed or turned into a port or both? I see considerable scope for an infrastructure that would allow drivers to be ports. _Easily_. M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
