Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Balaguru Nallathambi <bala@ats.com>
To: linux-sound@vger.kernel.org
Subject: Re: SoundBlasterPCI128
Date: Fri, 15 Jan 1999 19:11:42 +0000	[thread overview]
Message-ID: <marc-linux-sound-91641748726022@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91584820831233@msgid-missing>

Thanks. I guess I had the wrong patch (2.0.36*patch*) applied.
That's why the ES1371 driver did not show up.
THe 2.0.34*patch* has the ES1371 driver.

I have one more problem.
I have slackware dirstribution of LINUX which has gcc2.8
I guess to compile the 2.0.36 kernel with the patch applied
we need gcc2.7. I could not compile the kernel with my version
of gcc2.8. 
Is it possible or valid to apply the patch to a newer version of the kernel
source say 2.1.99 ? Will this compile with gcc2.8

Thanks,
-)Bala.




At 02:23 PM 1/15/99 +0100, you wrote:
>>         The problem I have is that I cannot see the ES1371 driver in the
>> kernel configuration options. So I did not even make the kernel.
>
>You need to enable CONFIG_EXPERIMENTAL
>
>Tom
>
>

  parent reply	other threads:[~1999-01-15 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-07 22:46 SoundBlasterPCI128 Balaguru Nallathambi
1999-01-09 14:11 ` SoundBlasterPCI128 Thomas Sailer
1999-01-11 22:53 ` SoundBlasterPCI128 Georg Wendt
1999-01-12  7:48 ` SoundBlasterPCI128 Thomas Sailer
1999-01-13 18:49 ` SoundBlasterPCI128 Balaguru Nallathambi
1999-01-13 20:00 ` SoundBlasterPCI128 Georg Wendt
1999-01-13 23:45 ` SoundBlasterPCI128 Balaguru Nallathambi
1999-01-15 13:23 ` SoundBlasterPCI128 Thomas Sailer
1999-01-15 19:11 ` Balaguru Nallathambi [this message]
1999-01-15 21:50 ` SoundBlasterPCI128 Georg Wendt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-91641748726022@msgid-missing \
    --to=bala@ats.com \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox