Re: MFC: src/sys/i386/conf/GENERIC and sound support
It'll be in loader.conf, actually. That's also a fine place to load modules. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC: src/sys/i386/conf/GENERIC and sound support
I noticed that this still hasn't been MFCed, even though it makes a lot of sense for regular users (that is, those that do not recompile their kernel regularily): revision 1.289 date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 In the year 2000, I think it's perfectly reasonable to include audio support by default in GENERIC. It would be nice, but it's also just too late to change this for 4.3 given that we wouldn't have enough testing time to ensure that enabling sound didn't break something else. We'll just have to shoot for 4.4. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support)
I like mine red. On 15 Jan, Michael C . Wu wrote: Can we please stop this bikeshed? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support
On 15 Jan, John Baldwin wrote: On 15-Jan-01 [EMAIL PROTECTED] wrote: Baseless, my eye you pinhead. Our company has been doing sound for over 10 years. I've witnessed this lockup many times. So get off it. :-) So this code infringes on your market and its in your best interest to discredit it. Ok. FWIW, Cameron Grant has been writing sound drivers for 10 years, so this isn't an amateurish attempt. Also, I have _yet_ to have a problem with pcm hanging during probe. Ever. On both ISA and PCI cards. Hardly, we use the sound drivers that come with FreeBSD As a matter of fact, we contributed back when we needed a fix to the sound driver. BTW, your good luck does not translate to good luck by others. We have been able to get sound cards to work the first time out, but we'd had enough that have not to know better. Someone suggested that it go into KLM. That's a good suggestion. That has been done. GENERIC and kld's (d, not m) are two different things however. Yes, thank you for that corrections. If memory servers me well, LKM is Novell (ala Kernel Loadable Module). Thanks again for that correction. Jessem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC? src/sys/i386/conf/GENERIC and sound support
"Michael C . Wu" wrote: "Fully functional" for a desktop implies a working sound card too. This is one of of those things that does not really matter very much. A good server admin will recompile and customize his kernel. And a desktop user probably does not know how to compile a kernel. Are you telling me that, in your consultancy, you just keep GENERIC? There is no need for this bikeshed. Whether pcm is included in GEERIC or not does not really hurt anybody either way. FreeBSD is most often used as a server, not a desktop. Why exactly is sound needed for a first install? If nothing else, PCM could be loaded via a kernel module. Optional stuff usually should not be statically linked into the kernel, but should be placed in KLD's. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC? src/sys/i386/conf/GENERIC and sound support
Donn Miller wrote: "Michael C . Wu" wrote: "Fully functional" for a desktop implies a working sound card too. This is one of of those things that does not really matter very much. A good server admin will recompile and customize his kernel. And a desktop user probably does not know how to compile a kernel. Are you telling me that, in your consultancy, you just keep GENERIC? There is no need for this bikeshed. Whether pcm is included in GEERIC or not does not really hurt anybody either way. FreeBSD is most often used as a server, not a desktop. Why exactly is sound needed for a first install? If nothing else, PCM could be loaded via a kernel module. Optional stuff usually should not be statically linked into the kernel, but should be placed in KLD's. While this is true, the GENERIC kernel is supposed to support as much hardware "out of the box" as possible, so a user can install and not have to worry about setting up devices... Why should FreeBSD be used only as a server? There are plenty of linux desktops around, and FreeBSD can be used just as well, even better maybe! I dont see why sound shouldnt be in the GENERIC kernel, since if we decide what should be "generic" based on what a server will use then maybe we should take out mouse and USB support as well? What about all these ata devices? Any self respecting server would use SCSI! As you can see, that is a bit extreme... But you would have to say that sound is pretty much "generic" these days, so really belongs in the GENERIC kernel... Just my 2c, Kal. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC? src/sys/i386/conf/GENERIC and sound support
Donn Miller wrote: While this is true, the GENERIC kernel is supposed to support as much hardware "out of the box" as possible, so a user can install and not have to worry about setting up devices... So a user can *install* and not have to worry about setting up devices. You don't need a soundcard to do an install. Once you've done the installation you can build a kernel which supports your soundcard. If it's causing problems on installs maybe it should be disabled by default, even if it is built into the kernel. --Ben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC? src/sys/i386/conf/GENERIC and sound support
On Thu, Dec 28, 2000 at 03:17:10PM -0800, [EMAIL PROTECTED] wrote: On 28 Dec, Gerald Pfeifer wrote: Having been hit by this today, how about MFCing the following change? revision 1.289 date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 In the year 2000, I think it's perfectly reasonable to include audio support by default in GENERIC. I can't answer for JKH or others but audio has had a history of problems, especially durning the boot-up probe stage. Problems such that it might lock up the machine under certain conditions. Perhaps this is the reason sound may never make it into GENERIC. And sound has still problems. Example, on my laptop sound has always worked since 3.* But having upgraded to 4.2-RELEASE i get the following: pcm0: Neomagic 256AV (non-ac97) at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x320-0x321 irq 5 drq 0,1 on isa0 pcm0: play interrupt timeout, channel dead Apparently sound died after suspend and resume, which was not the case previously. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: MFC? src/sys/i386/conf/GENERIC and sound support
Having been hit by this today, how about MFCing the following change? revision 1.289 date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 In the year 2000, I think it's perfectly reasonable to include audio support by default in GENERIC. I can't answer for JKH or others but audio has had a history of problems, especially durning the boot-up probe stage. Problems such that it might lock up the machine under certain conditions. Perhaps this is the reason sound may never make it into GENERIC. Huh!!?? What are you talking about? The commit mail quoted above is sound going into GENERIC! M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
