From: Andi Kleen <ak@suse.de>
To: Dan Hollis <goemon@anime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ECS k7s5a audio sound SiS 735 - 7012
Date: 03 Nov 2001 20:45:20 +0100 [thread overview]
Message-ID: <p73zo63prjj.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <86ady56u3h.fsf@cam.ac.uk.suse.lists.linux.kernel> <Pine.LNX.4.30.0111021316150.4828-100000@anime.net.suse.lists.linux.kernel>
In-Reply-To: Dan Hollis's message of "2 Nov 2001 22:23:47 +0100"
Dan Hollis <goemon@anime.net> writes:
> On 2 Nov 2001, John Fremlin wrote:
> > Who to talk to at SiS? They have a dubious web interface for sales and
> > marketing requests that I used, but I'd prefer to email someone who
> > knows what a datasheet actually is ;-)
> > Alsa doesn't advertise any contact with SiS at all :-(
>
> I've already talked with SiS. They are insisting that they will write the
> drivers themselves, they dont want to release datasheets to anyone. The
> reply I got (Thu, 25 Oct 2001) they said they are working on OSS drivers
> in-house, and ALSA drivers are next.
ALSA drivers seem to work. A standard SuSE 7.2 install with yast2 alsa installer
had no problems with producing sound on a k7s5a.
The sound quality is somewhat poor however; but even with another sound card
this board is cheaper than the alternativesa and works very fast.
-Andi (happy user of a k7s5a with a sblive)
next parent reply other threads:[~2001-11-03 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86ady56u3h.fsf@cam.ac.uk.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.30.0111021316150.4828-100000@anime.net.suse.lists.linux.kernel>
2001-11-03 19:45 ` Andi Kleen [this message]
2001-11-04 1:02 ` ECS k7s5a audio sound SiS 735 - 7012 Alan Cox
[not found] <20011103055053.J761-100000@gerard>
2001-11-03 12:59 ` Alan Cox
2001-10-31 8:30 ECS k7s5a motherboard doesnt work Zephaniah E. Hull
2001-10-31 10:52 ` Alan Cox
2001-11-02 15:48 ` ECS k7s5a audio sound SiS 735 - 7012 John Fremlin
2001-11-02 16:16 ` Alan Cox
2001-11-02 16:00 ` John Fremlin
2001-11-02 21:20 ` Dan Hollis
2001-11-02 23:42 ` Alan Cox
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=p73zo63prjj.fsf@amdsim2.suse.de \
--to=ak@suse.de \
--cc=goemon@anime.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.