* Modular Sound 2.0.36
@ 1998-12-14 12:28 Andries, Bert
1998-12-14 18:06 ` Bill Nottingham
1998-12-15 9:50 ` Andries, Bert
0 siblings, 2 replies; 3+ messages in thread
From: Andries, Bert @ 1998-12-14 12:28 UTC (permalink / raw)
To: linux-sound
Hello,
Via ftp.redhat.com ( and ftpsearch.lycos.com ) I found in
sound/patches-current/modular-sound-2.0.36-2.diff.gz
When applied to the kernel 2.0.36 source tree ( the real thing, not the
RH5.2 pre-2.0.36 ) it gives rejects on Config.in ( /drivers/sound/Config.in
)
Anyone here has experience on this subject ? Am I following the right
procedure to get modular sound on 2.0.36 ?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Modular Sound 2.0.36
1998-12-14 12:28 Modular Sound 2.0.36 Andries, Bert
@ 1998-12-14 18:06 ` Bill Nottingham
1998-12-15 9:50 ` Andries, Bert
1 sibling, 0 replies; 3+ messages in thread
From: Bill Nottingham @ 1998-12-14 18:06 UTC (permalink / raw)
To: linux-sound
Andries, Bert (Bert.Andries@uza.uia.ac.be) said:
> Via ftp.redhat.com ( and ftpsearch.lycos.com ) I found in
> sound/patches-current/modular-sound-2.0.36-2.diff.gz
> When applied to the kernel 2.0.36 source tree ( the real thing, not the
> RH5.2 pre-2.0.36 ) it gives rejects on Config.in ( /drivers/sound/Config.in
> )
>
> Anyone here has experience on this subject ? Am I following the right
> procedure to get modular sound on 2.0.36 ?
It seems to work OK here on a plain 2.0.36 - there's a couple of
patches with offsets (I'll throw a newer version on the FTP site
that doesn't do this), but it goes through clean. What version
of patch are you using?
Bill
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Modular Sound 2.0.36
1998-12-14 12:28 Modular Sound 2.0.36 Andries, Bert
1998-12-14 18:06 ` Bill Nottingham
@ 1998-12-15 9:50 ` Andries, Bert
1 sibling, 0 replies; 3+ messages in thread
From: Andries, Bert @ 1998-12-15 9:50 UTC (permalink / raw)
To: linux-sound
>Andries, Bert (Bert.Andries@uza.uia.ac.be) said:
> > Via ftp.redhat.com ( and ftpsearch.lycos.com ) I found in
> > sound/patches-current/modular-sound-2.0.36-2.diff.gz
> > When applied to the kernel 2.0.36 source tree ( the real thing, not the
> > RH5.2 pre-2.0.36 ) it gives rejects on Config.in (
> /drivers/sound/Config.in
> > )
> >
> > Anyone here has experience on this subject ? Am I following the right
> > procedure to get modular sound on 2.0.36 ?
>
< It seems to work OK here on a plain 2.0.36 - there's a couple of
< patches with offsets (I'll throw a newer version on the FTP site
< that doesn't do this), but it goes through clean. What version
< of patch are you using?
< Bill
It isn't clear to me against what the
sound/patches-current/modular-sound-2.0.36-2.diff.gz
should be patched.
What I failed to reveal in my posting is that I'm trying to get beta
modular sound drivers from
the 2.1.xxx kernel onto 2.0.36. In particular the Turtle Beach Pinnacle /
Fiji driver.
( Andrew Veliath http://www.rpi.edu/~veliaa/pinlinux.html )
The mentioned patch file puts the 'extra' 2.1.xxx drivers in the
drivers/sound directory ( looks
good at first glance ). Only patching the Config.in fails. I tried to put
the chunk of code for the
Turtle Beach Pinnacle / Fiji into it ... manually. Which works except that
tkparse doesn't
accept the 'string' keyword. ( make mrproper ; make xconfig ).
I'll check the version of patch ... it should be the one that came with the
rh5.1.
Bert
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1998-12-15 9:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1998-12-14 12:28 Modular Sound 2.0.36 Andries, Bert
1998-12-14 18:06 ` Bill Nottingham
1998-12-15 9:50 ` Andries, Bert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox