Re: aplay: test_wavefile:807: can't play WAVE-file format 0x0055 !??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Checking some backlog, saw I hadn't responded to this.  You have other
responses and seem to have moved on, but I'll just put in my 2 cents.
:-)

On Fri, 04 Sep 2009 22:15:21 -0400
William Case <billlinux@xxxxxxxxxx> wrote:

> Hi Stan and others;

> > http://ftp.kernel.org/pub/linux/kernel/people/tiwai/docs/HD-Audio.html
> 
> Stan, I have taken your advice and I am pursuing it diligently.  My
> fist quick questionis;
> 
> /docs/HD-Audio.pdf says:
> 
> "The HD-audio component consists of two parts: 
> 1) the controller chip, and, 
> 2) the codec chips on the HD-audio bus. "
> 
> Checking with lshw:
> On my machine they are:
> 1) [82801G (ICH7 Family) High Definition Audio Controller]
> 2) And nothing obvious to me for the codec chip.  Would this be the
> hardware I am looking for:
>         *-pci:2
>              description: PCI bridge
>              product: 82801G (ICH7 Family) PCI Express Port 2
>              vendor: Intel Corporation
>              physical id: 1c.1
>              bus info: pci@0000:00:1c.1
>              version: 01
>              width: 32 bits
>              clock: 33MHz
>              capabilities: pci normal_decode bus_master cap_list
>              configuration: driver=pcieport-driver
>              resources: irq:26 ioport:d000(size=4096)
> memory:e4000000-e4ffffff ioport:e5200000(size=1048576)
> 
> and, would the pcieport-driver be a digital-to-analog /
> analog-to-digital driver.  /docs/HD-Audio.pdf says there should be a
> specific driver.
> 
> If not, what should I be looking for?  
> Is the codec chip just considered part of the 82801G (ICH7 Family) and
> snd-hda-intel the sole driver?

Bill, if I could answer questions like that I would be developing alsa
drivers. :-)  Snd-hda-intel is the driver for the architecture.
Because it is a standard architecture, no matter who provides the chips
that build it, the same driver should *theoretically* work for any
device that conforms to the standard.  Yeah, right!  Like that will
happen.  So yes, all hda-intel devices use the snd-hda-intel driver.

> 
> Actually most of that document is not too hard to follow, but this
> codec chip question doesn't seem to be answered, and, googling
> doesn't give me anything useful about my particular
> machine/motherboard that I can see.

The parts of the document I thought were particularly relevant for
people with hda-intel devices that weren't working were the slots
information at the start, and how to overcome broken bioses that
mis-reported the device (proprietary drivers can ignore the bios
reports because they *know* the setup of the hardware), and the
hda-verb section that allowed the user to change pin configuration on
the device until it was working. i.e.  I wasn't viewing it as a
theoretical overview, though it is partly that, but as a practical way
of getting an hda-intel device to work on your hardware.  Someday, when
I upgrade my hardware, I'll probably have the opportunity to test that
view myself seeing as all new hardware seems to be moving to hda-intel
as the on board device. Or, maybe I'll buy an add-on device that doesn't
use hda-intel and avoid the whole potential problem.  ;-)   External
devices avoid the whole electronically noisy environment inside a pc,
so they have other benefits as well.

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux