All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balaguru Nallathambi <bala@ats.com>
To: linux-sound@vger.kernel.org
Subject: Re: SoundBlasterPCI128
Date: Wed, 13 Jan 1999 23:45:50 +0000	[thread overview]
Message-ID: <marc-linux-sound-91626166717503@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91584820831233@msgid-missing>

At 09:00 PM 1/13/99 +0100, you wrote:

To apply the patch all you have to do is

	zcat 2.0*patch*gz | patch -p0

	on the linux source tree.
	The source tree will have the patch applied now.
	Then you need to do a make clean, make config, make dep, make zImage
and use the boot image to load a new kernel.

	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.

I guess we need help from some one who has successfully done this before.
If you get everything done right, let me know.

-)Bala.

>Hi,
> 
>> I downloaded the modular sound patch from Alan Cox's web site.
>> and applied it to kernel 2.0.36
>
>I'm trying the same at the moment.
>How did you apply the patch (and which, I read the
>2.0.34-modular-3.patch.gz should me the safest...)?
>
>Whenever I get the patch installed, I'm a step further!
>Thanks + bye
>	Georg
>
>

  parent reply	other threads:[~1999-01-13 23:45 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 ` Balaguru Nallathambi [this message]
1999-01-15 13:23 ` SoundBlasterPCI128 Thomas Sailer
1999-01-15 19:11 ` SoundBlasterPCI128 Balaguru Nallathambi
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-91626166717503@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.