How to get ALSA kernel patch that fits in patches.common
Hi, I'm new to SuSE, but not to Linux, and I know how to build my own kernels. That's not the issue. I want to replace the ALSA in kernel-source-2.4.20.SuSE and build my own k_athlon.rpm. The src.rpm contains patches.common.tar.bz2 which includes an old version of ALSA. And I need a newer version to get support for the via8235 chipset, and I want to try out 0.9.4. Does anyone know how this alsa patch was created? Notice that it is not the same as the alsa-driver package. Somehow it is derived from that. But how was that done? Thanks for any hints. Kees
On Tue, 1 Jul 2003 21:52:39 +0200
Kees Bakker
Hi,
I'm new to SuSE, but not to Linux, and I know how to build my own kernels. That's not the issue.
I want to replace the ALSA in kernel-source-2.4.20.SuSE and build my own k_athlon.rpm. The src.rpm contains patches.common.tar.bz2 which includes an old version of ALSA. And I need a newer version to get support for the via8235 chipset, and I want to try out 0.9.4.
Does anyone know how this alsa patch was created? Notice that it is not the same as the alsa-driver package. Somehow it is derived from that. But how was that done?
I'm not sure about this, but I've been compiling my kernels, and putting in the newest alsa. All you have to do is compile your kernel, and include sound as "module". Then make a symlink to your kernel source directory called "linux", so alsa can find it. After you compile and install the kernel, you do the alsa stuff. Get the latest alsa-driver-0.94 and unpack it in /usr/src/alsa. Then just run configure,make,make install and it will find your kernel sources, make all the alsa modules, and install them into the proper /lib/modules directory for the kernel. It's almost automatic, it's so easy. The patch you are talking about may be for something else pertaining to some aspect of alsa, there are patches galore out there now. -- use Perl; #powerful programmable prestidigitation
On Tuesday 01 July 2003 23:06, zentara wrote:
On Tue, 1 Jul 2003 21:52:39 +0200 [...]
Does anyone know how this alsa patch was created? Notice that it is not the same as the alsa-driver package. Somehow it is derived from that. But how was that done? [...]
The patch you are talking about may be for something else pertaining to some aspect of alsa, there are patches galore out there now.
But still. Why is SuSE so secretive about this? Are the SuSE developers listening in on this mailing list? I just want to know how they did this. And I want a clean build of the k_athon package with the new ALSA. That's my nature of dealing with software patches.
use Perl; #powerful programmable prestidigitation
There 's nothing wrong with python! I have passed the Perl station.
Kees Bakker
But still. Why is SuSE so secretive about this?
Because we don't talk about things until the feature list has been decided on. It's that simple.
And I want a clean build of the k_athon package with the new ALSA.
Then you are on your own to enable this. We can't and won't support compiling the kernel with anything else then we supply, meaning in this case the older ALSA version. BTW, compiling your own kernel has been unsupported from day one, at least without paying for support. Philipp -- Philipp Thomas work: pthomas@suse.de SuSE Linux AG private: philipp.thomas@t-link.de
On Thursday 03 July 2003 22:27, Philipp Thomas wrote:
Kees Bakker
[Thu, 3 Jul 2003 22:15:28 +0200]: But still. Why is SuSE so secretive about this?
Because we don't talk about things until the feature list has been decided on. It's that simple.
Relax. I'm not asking for a new feature. I want to know how the ALSA patch was created for the existing kernel. I don't even need all the details, just roughly how it was done.
And I want a clean build of the k_athon package with the new ALSA.
Then you are on your own to enable this. We can't and won't support compiling the kernel with anything else then we supply, meaning in this case the older ALSA version. BTW, compiling your own kernel has been unsupported from day one, at least without paying for support.
I have built my own kernels since 0.99pl15. But, being new to SuSE, I'd like to build a clean kernel, same as k_athlon-2.4.20-86, only with a newer ALSA. BTW. The reason I do this is that my in-laws have a new computer with an ASUS A7V8X-X with onboard sound. To bad the sound doesn't work with the SuSE8.2 kernel. This mobo has a VIA8235 which may (or may not) be supported with the newer ALSA. -- Kees (registered Linux user #2395)
On Thu, 3 Jul 2003 22:47:07 +0200
Kees Bakker
On Thursday 03 July 2003 22:27, Philipp Thomas wrote:
Kees Bakker
[Thu, 3 Jul 2003 22:15:28 +0200]: But still. Why is SuSE so secretive about this?
Because we don't talk about things until the feature list has been decided on. It's that simple.
Relax. I'm not asking for a new feature. I want to know how the ALSA patch was created for the existing kernel. I don't even need all the details, just roughly how it was done.
Maybe go to : http://infolinux.de/jp/index.html and get the jp patch set. It has an alsa kernel patch similar to what suse does. Notice the complexity of all the patches...it isn't easy, and the patch will only work on the -pre2 kernal. Patching the kernel is getting more and more complex as the kernel complexity increases. If you apply one patch, then another may not work, or may take "custom manual patching". Doing this without breaking something, takes alot of knowledge. One of the best things about SuSE is the all-purpose kernel, and I admire Hubert Mantel for being able to keep all this stuff together. It's relatively easy to compile a kernel for a specific system. But making a general purpose kernal that works for everyone, is pretty difficult. Check out http://www.kernelnewbies.org -- use Perl; #powerful programmable prestidigitation
participants (3)
-
Kees Bakker
-
Philipp Thomas
-
zentara