On Sat, 24 Apr 1999, Chris Csanady wrote:
> Ugh. This also has the same effect on captured audio using fxtv. It seems
> that everything audio related is messed up now. (Or perhaps real time?)
>
> I will try to find the exact day where things broke I guses. I don't have
> much time right now th
>> >mp3s aren't playing quite right with x11amp though, little
>> >skips here and there, they work fine with the old kernel.
>> >mpg123 seems fine, as does the sound in FXTV.
>> >I'll try making the world again.
>>
>> Was there ever any resolution/further inspection of this?
>
>Not as far I know;
> >mp3s aren't playing quite right with x11amp though, little
> >skips here and there, they work fine with the old kernel.
> >mpg123 seems fine, as does the sound in FXTV.
> >I'll try making the world again.
>
> Was there ever any resolution/further inspection of this?
Not as far I know; its stil
>> Hmm, you might like to try this patch and see what happens, there is
>> a missing old driver wrapper for the pcm stuff. As a result, it's not
>> getting run from the isa probe. Regarding the other driver, I'm not
>> sure what's going on there as the hooks appear to be present.
>
>Right on, th
On Sun, 18 Apr 1999, Daniel C. Sobral wrote:
> Brian Feldman wrote:
> >
> > > IPFW works for me...but I'm loading the KLD.
> >
> > I like having my ipfw rules there BEFORE anything happens, hence before
> > rc(5).
>
> klds can be loaded by the loader. Hence, before /kernel.
Thanks for ruining
Brian Feldman wrote:
>
> > IPFW works for me...but I'm loading the KLD.
>
> I like having my ipfw rules there BEFORE anything happens, hence before
> rc(5).
klds can be loaded by the loader. Hence, before /kernel.
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.
On Sat, 17 Apr 1999, Jake Burkholder wrote:
> > Hmm, you might like to try this patch and see what happens, there is
> > a missing old driver wrapper for the pcm stuff. As a result, it's not
> > getting run from the isa probe. Regarding the other driver, I'm not
> > sure what's going on there as
Oh, btw, you did break sbxvi. Look carefully at the #if which surrounds it ;)
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \__ \ |) |
http://www.freebsd.org _
> Hmm, you might like to try this patch and see what happens, there is
> a missing old driver wrapper for the pcm stuff. As a result, it's not
> getting run from the isa probe. Regarding the other driver, I'm not
> sure what's going on there as the hooks appear to be present.
Right on, that patc
On Sun, 18 Apr 1999, Peter Wemm wrote:
> Brian Feldman wrote:
> > On Sat, 17 Apr 1999, Peter Wemm wrote:
> > > Chris Piazza wrote:
> > > > On 17-Apr-99 Brian Feldman wrote:
> > > > > Both sound drivers are broken with the new-bus code. My SB16, in the
> > > > > ol
> d
> > > > > driver, now ge
On Sat, 17 Apr 1999, Peter Wemm wrote:
> For what it's worth, PnP has for the most part not been changed under
> new-bus and is using the old mechanisms. The only significant risk is that
> the attach code doesn't like what I've done with the emulation of
> isa_device->id_id for "unit numbers".
Brian Feldman wrote:
> On Sat, 17 Apr 1999, Peter Wemm wrote:
> > Chris Piazza wrote:
> > > On 17-Apr-99 Brian Feldman wrote:
> > > > Both sound drivers are broken with the new-bus code. My SB16, in the ol
d
> > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the ne
w
>
On Sat, 17 Apr 1999, Brian Feldman wrote:
> On Sat, 17 Apr 1999, Peter Wemm wrote:
>
> > Chris Piazza wrote:
> > > On 17-Apr-99 Brian Feldman wrote:
> > > > Both sound drivers are broken with the new-bus code. My SB16, in the old
> > > > driver, now gets recognized but sbxvi is never looked for.
On Sat, 17 Apr 1999, Peter Wemm wrote:
> Chris Piazza wrote:
> > On 17-Apr-99 Brian Feldman wrote:
> > > Both sound drivers are broken with the new-bus code. My SB16, in the old
> > > driver, now gets recognized but sbxvi is never looked for. pcm0, the new
> > > driver, never initializes with the
>Chris Piazza wrote:
>> On 17-Apr-99 Brian Feldman wrote:
>> > Both sound drivers are broken with the new-bus code. My SB16, in the old
>> > driver, now gets recognized but sbxvi is never looked for. pcm0, the new
>> > driver, never initializes with the new code :(
>> >
>> > device pcm0 at isa? p
Chris Piazza wrote:
> On 17-Apr-99 Brian Feldman wrote:
> > Both sound drivers are broken with the new-bus code. My SB16, in the old
> > driver, now gets recognized but sbxvi is never looked for. pcm0, the new
> > driver, never initializes with the new code :(
> >
> > device pcm0 at isa? port? tty
On 17-Apr-99 Brian Feldman wrote:
> Both sound drivers are broken with the new-bus code. My SB16, in the old
> driver, now gets recognized but sbxvi is never looked for. pcm0, the new
> driver, never initializes with the new code :(
>
> device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
>
The
Both sound drivers are broken with the new-bus code. My SB16, in the old
driver, now gets recognized but sbxvi is never looked for. pcm0, the new
driver, never initializes with the new code :(
device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
#controller snd0
#device sb0 at isa? port
18 matches
Mail list logo