Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Neale Banks <neale@lowendale.com.au>
To: linux-sound@vger.kernel.org
Subject: Status of ALi5451(trident)?
Date: Wed, 10 Jul 2002 08:49:37 +0000	[thread overview]
Message-ID: <marc-linux-sound-102629084116513@msgid-missing> (raw)

Greetings,

What is the status (e.g. supposedly working, supported and maintained?)
of the Trident driver with the Ali5451 chipset (both regular audio and
MIDI synth)?

Issues I have on the Toshiba Satellite 1800[1] include:

1) not working[2] with 2.2.21
2) MIDI not working with 2.2.21 or 2.4.18
3) MIDI code appears to be removed in 2.4.17 source (is this a sign?)
4) Lack of findable documentation on what's supposed to work and how (yes,
I'm prepared to collate something for linux/Documentation/sound/)

Thanks,
Neale.

[1] The Toshi 1800's lspci -v output includes:

00:06.0 Multimedia audio controller: Acer Laboratories Inc. [ALi] M5451 PCI South Bridge Audio (rev 01)
        Subsystem: Toshiba America Info Systems: Unknown device 0001
        Flags: bus master, medium devsel, latency 64, IRQ 11
        I/O ports at ed00
        Memory at f7efe000 (32-bit, non-prefetchable)
        Capabilities: [dc] Power Management version 2

[2] OK, "not working" isn't really a proper report.  I get this logged
when something tries to open the audio:

kernel: trident: drain_dac, dma timeout?

What else should I be reporting about this?


             reply	other threads:[~2002-07-10  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  8:49 Neale Banks [this message]
2002-07-10  9:07 ` Status of ALi5451(trident)? Joern Nettingsmeier
2002-07-12  6:29 ` Neale Banks
2002-07-12  8:20 ` Joern Nettingsmeier
2002-07-12 14:34 ` Neale Banks
2002-07-12 18:03 ` Joern Nettingsmeier
2002-07-17  5:36 ` Neale Banks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-102629084116513@msgid-missing \
    --to=neale@lowendale.com.au \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox