On Fri, 3 Sep 1999, Nick Hibma wrote:
>
> What about documenting what you do here? It's not quite obvious to me
> why the dev is not the parent of the child in some cases.
It may be a great-grandchild. For instance in this case, the child is
isab0, the grandchild is isa0 and the great-grandchil
What about documenting what you do here? It's not quite obvious to me
why the dev is not the parent of the child in some cases.
Cheers,
Nick
> pcicfgregs *cfg = &dinfo->cfg;
> +int passthrough = (device_get_parent(child) != dev);
> int map = 0;
--
ISIS/STA, T.P.270, Joint Re
On Thu, 2 Sep 1999, Ollivier Robert wrote:
> According to Doug Rabson:
> > changing over to the pcm driver. Since your card is a PnP one, you should
> > be able to put just "device pcm0" in your kernel config.
>
> Even for ISA ones ? I though only PCI sound cards let you use the shorter
> form..
On Thu, 2 Sep 1999, Luoqi Chen wrote:
> > That's exactly what I have. This is just so weird. I am now reading the
> > debug register chapter of intel's manual, it is virtually impossible to
> > pinpoint the location by single-stepping through the code...
> >
> The debug register trick worked, an
> That's exactly what I have. This is just so weird. I am now reading the
> debug register chapter of intel's manual, it is virtually impossible to
> pinpoint the location by single-stepping through the code...
>
The debug register trick worked, and the discovery was quite unexpected:
because the
According to Doug Rabson:
> changing over to the pcm driver. Since your card is a PnP one, you should
> be able to put just "device pcm0" in your kernel config.
Even for ISA ones ? I though only PCI sound cards let you use the shorter
form...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -
> > I too have problems with my on board CS4236 sound chip and it is of a very
> > strange nature: in the new isa pnp code, function isa_assign_resources()
> > mysteriously overwrites the isa_device structure and sets logical_id to 0,
> > and as a result subsequent probe would not recognize it any
On Thu, 2 Sep 1999, Luoqi Chen wrote:
> > Could you send the output of dmesg. It could be that your BIOS has
> > rearranged the irq settings and has put another card on that IRQ. Is the
> > sound card PNP? If not, could you check that the card's IRQ is marked as
> > legacy in the BIOS?
> >
> > N
On Thu, 2 Sep 1999, Arthur H. Johnson II wrote:
> here it is:
> sb0 at port 0x220 irq 5 drq 1 on isa0
> snd0:
> sbxvi0 at port 0x drq 5 on isa0
> isa_compat: didn't get ports for sbxvi
> snd0:
> WARNING: "snd" is usurping "snd"'s cdevsw[]
> unknown0: on isa0
> unknown1: at port 0x
> Could you send the output of dmesg. It could be that your BIOS has
> rearranged the irq settings and has put another card on that IRQ. Is the
> sound card PNP? If not, could you check that the card's IRQ is marked as
> legacy in the BIOS?
>
> Nick
>
> > My sound card used to work, and with a
here it is:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #4: Thu Sep 2 10:45:54 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/ARTHUR
Timecounter "i8254"
Could you send the output of dmesg. It could be that your BIOS has
rearranged the irq settings and has put another card on that IRQ. Is the
sound card PNP? If not, could you check that the card's IRQ is marked as
legacy in the BIOS?
Nick
> My sound card used to work, and with a backup kernel i
My sound card used to work, and with a backup kernel it still did ( I lost
it ) but after doing a make update world yesturday I came to the
realization that it no longer works. Did someone break the sb drivers? I
get a drq / irq conflict error, but they are set to the sound card's
settings.
Art
13 matches
Mail list logo
