Hello,
I have been tasked with getting sound to work on a couple
different embedded x86 boards that contain the ESS1869
audio chipset. (in QNX6.2)
I was prepared to write the driver from scratch using the
Audio DDK but there is no sense doing more work than
necessary.
The chipset is “Sound Blaster Pro” compatible, but it
seems with some caveats. Most spefically the QNX 6.2
docs for deva-ctrl-sb.so states:
“Some sound cards listed as being Sound Blaster compatible
default to another mode (eg ESS18xx series, …). These
cards will not work with this driver.”
Could someone explain to me what “another mode” means?
The tone of this comment would lead me to believe that
someone close to this driver has direct knowledge of what
is missing to support the 18xx series. It would save me
a fair amount of work if someone could point me in the
right direction.
I have been told that I should be able to obtain the
deva-ctrl-sb.so source through other (more appropriate)
channels if it would be a useful starting point.
So I basically want to know:
- What makes ESS1869 not work with the current driver?
- Would dev-ctrl-sb.so be an appropriate starting point
to writing a ESS1869 driver?
Thanks
–
Sean Gustafson Astra Network
sean@astra.mb.ca QNX Consulting and Custom Programming
Hello, Sean!
SG> So I basically want to know:
SG> 1) What makes ESS1869 not work with the current driver?
Try to use isapnp utility to assign resources: DMA, IRQ, PORT. Then try to
run SB driver.
SG> 2) Would dev-ctrl-sb.so be an appropriate starting point
SG> to writing a ESS1869 driver?
The cost of development ESS1869 ISA driver is much bigger then the just a
buy a good PCI adapter 
With best regards, Mike Gorchak.
Mike Gorchak wrote:
SG> So I basically want to know:
SG> 1) What makes ESS1869 not work with the current driver?
Try to use isapnp utility to assign resources: DMA, IRQ, PORT. Then try to
run SB driver.
Isn’t isapnp a QNX4 thing? I’m doing this in 6.2. By the way,
I would have tried setting these resources if the docs did not
explicitly say my chipset would not work.
SG> 2) Would dev-ctrl-sb.so be an appropriate starting point
SG> to writing a ESS1869 driver?
The cost of development ESS1869 ISA driver is much bigger then the just a
buy a good PCI adapter >
Agreed, but this is a embedded system with the chip on board.
It is not an option at this time to use something different.
Thanks for your comments,
Sean
–
Sean Gustafson Astra Network
sean@astra.mb.ca QNX Consulting and Custom Programming
Sean Gustafson <sean@astra.mb.ca> writes:
Mike Gorchak wrote:
SG> So I basically want to know:
SG> 1) What makes ESS1869 not work with the current driver?
Try to use isapnp utility to assign resources: DMA, IRQ, PORT. Then try to
run SB driver.
Isn’t isapnp a QNX4 thing? I’m doing this in 6.2. By the way,
I would have tried setting these resources if the docs did not
explicitly say my chipset would not work.
Not necessarily. But I think you don’t need this, as we are using the
1869 on our board and it works. Did you try the enum-pnpisa? If you
start the driver with the outputs of the enum-*, it worked for me.
SG> 2) Would dev-ctrl-sb.so be an appropriate starting point
SG> to writing a ESS1869 driver?
The cost of development ESS1869 ISA driver is much bigger then the just a
buy a good PCI adapter >
I don’t think this is necessary, since the 1869 works perfectly with
6.2 over here.
Sven
–
Sven Fischer – DEUTA-Werke GmbH, Abteilung EIT
Dipl.-Phys. Paffrather Str. 140, 51465 Bergisch Gladbach, Germany
Tel.: +49-(0)2202-958-216 Fax.: +49-(0)2202-958-145
Please note the disclaimer: http://www.deutaeit.de/disclaimer.html
Sven Fischer wrote:
I don’t think this is necessary, since the 1869 works perfectly with
6.2 over here.
Interesting, thanks for the info. I don’t actually have the
hardware in hand yet but I will certainly look closely at
configuring the existing driver when I get it.
Thanks again.
–
Sean Gustafson Astra Network
sean@astra.mb.ca QNX Consulting and Custom Programming