Re: New alsa-driver for rhel6

On Mon, May 30, 2011 at 11:08 AM, Paulo Cavalcanti <[email protected]> wrote:

>
>
> On Sun, May 29, 2011 at 4:48 AM, Axel Thimm <[email protected]> wrote:
>
>> On Fri, 2011-05-27 at 08:21 -0300, Paulo Cavalcanti wrote:
>>
>> >         I see what is happening. F12 and F13 also use kernel 2.6.32.
>> >         However, their kernels have not been patched by RedHat.
>> >
>> >         Therefore, the adriver patch should not be applied to F12 and
>> >         F13.
>> >         The simplest way is adding a bcond something. Nonetheless, F12
>> >         is dead
>> >         and F13 is going to die soon. Should we just let them rest in
>> >         peace??
>>
>> It also affects all RHEL5 kernels but the very latest. RHEL is a slow
>> upgrading platform for most users, so the support of at least a few
>> kernels is a must.
>>
>
> But rhel5 still uses the kernel 2.6.18.
>
> The change was just lowering from kernel 2.6.35/2.6.37 to 2.6.32.  It
> should affect only
> F12 (2.6.32), F13 (2.6.34) and previous rhel6 versions only. I do not see
> how
> rhel5 was affected ....
>
> The adriver patch is listed below:
>
>
> ---------------------------------------------------------------------------------------------------------
>
> diff -Naur alsa-driver-1.0.24/include/adriver.h
> alsa-driver-1.0.24-new/include/adriver.h
> --- alsa-driver-1.0.24/include/adriver.h    2011-01-27 10:09:20.000000000
> -0200
> +++ alsa-driver-1.0.24-new/include/adriver.h    2011-05-20
> 18:41:26.108621169 -0300
> @@ -1909,7 +1909,7 @@
>  #endif
>
>  /* hex_to_bin() */
> -#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 35)
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 32)
>  static inline int hex_to_bin(char c)
>  {
>      if (c >= '0' && c <= '9')
> @@ -1923,7 +1923,7 @@
>  #endif
>
>  /* vzalloc() wrapper */
> -#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 37)
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 32)
>  #include <linux/vmalloc.h>
>  static inline void *vzalloc(unsigned long size)
>
>  {
>
>
By the way. I do not understand why the driver is in bleeding.

It is exactly the same driver as before: patches 0, 2, 6 are now
patches 0,2,6,7,8. Patch 6 is the new adriver patch and patches 7 and 8
affect only two specific mobo models when the driver is loaded using
non-default options.
It just remaps some pins on two of my sound cards, and will not hurt anybody
....

-- 
Paulo Roma Cavalcanti
LCG - UFRJ