From: Mike Frisch <mfrisch@saturn.tlug.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Status of ALi MAGiK 1 support in 2.4.?
Date: Mon, 28 May 2001 12:28:18 -0400 [thread overview]
Message-ID: <20010528122818.B32232@saturn.tlug.org> (raw)
In-Reply-To: <20010528175712.B18955@pua.nirvana> <E154Pha-0003Gr-00@the-village.bc.nu>
In-Reply-To: <E154Pha-0003Gr-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, May 28, 2001 at 05:17:06PM +0100
On Mon, May 28, 2001 at 05:17:06PM +0100, Alan Cox wrote:
> > So it seems that only AMD and ALi are left with Socket A chipsets (SiS 735 is
> > yet to come). And the ALi MAGiK 1 has a good feature/cost ratio and is being
> > reported as very stable (although perhaps not very fast).
> >
> > So having been burned in the recent past with VIAs KT133A/686B and Linux, I
> > hope that I can get an ALi MAGiK 1 board and rest in peace ...
>
> It would be interesting to know how well the ALi stuff behaves. They've
> certainly been helpful in the Linux world, indeed they did the ALi parts
> of the trident sound driver themselves, including full 5.1 audio out and also
> chunks of the alim15x3 (IDE) driver
If there is anything in particular (benchmarks or stress tests) I can
help with in this regard, please let me know. I am not a kernel hacker,
but a competent Linux user and programmer. I am not afraid to get my
hands dirty.
next prev parent reply other threads:[~2001-05-28 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 15:57 Status of ALi MAGiK 1 support in 2.4.? Axel Thimm
2001-05-28 16:09 ` Mike Frisch
2001-05-28 16:17 ` Alan Cox
2001-05-28 16:28 ` Mike Frisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-28 23:18 Bobby D. Bryant
2001-05-29 12:35 ` Alan Cox
2001-05-29 9:04 ` Bobby D. Bryant
2001-05-30 21:48 ` Stefan Jaschke
2001-05-29 14:07 ` Mike Frisch
2001-05-29 9:11 ` Bobby D. Bryant
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=20010528122818.B32232@saturn.tlug.org \
--to=mfrisch@saturn.tlug.org \
--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.