From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Marco Colombo <marco@esi.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA chipset
Date: Wed, 12 Sep 2001 22:55:19 +0200 [thread overview]
Message-ID: <3B9FCBB7.9020806@fugmann.dhs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109122209470.8745-100000@Megathlon.ESI>
I've got a A7M266 (1.33 Ghz, 133 Mhz fb), and all works perfectly:
ATA100 + DMA + K7/3DNOW optimization.
No craches yet (run for about 2 month).
I'm very satisfied with this mobo - IMHO it's a good buy.
Regards
Anders Fugmann
Marco Colombo wrote:
> On Wed, 12 Sep 2001, Jussi Laako wrote:
>
>
>>Marco Colombo wrote:
>>
>>>Sorry to bother you again with this issue, Alan... by 'AMD chipsets'
>>>you mean BOTH north and south bridges (eg. 761 + 766) or does it include
>>>also AMD NB + VIA SB combo?
>>>AMD 761 + VIA 686B based MBs are quite common this days: are they "safe"
>>>(do you have failure reports)?
>>>
>>At least my ASUS A7M266 works very well. It has AMD 761 nb and VIA 686B sb
>>and the 686B is used only for IDE and IO interfaces. PCI bus comes from the
>>761, AFAIK.
>>
>> - Jussi Laako
>>
>>
>
> Thanks for your answer! Can you please confirm me that both the ATA/100
> controller (at ATA/66 or ATA/100 speed) and Athlon optimized kernels work?
>
> .TM.
>
next prev parent reply other threads:[~2001-09-12 20:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13 ` Marco Colombo
2001-09-12 20:55 ` Anders Peter Fugmann [this message]
2001-09-14 17:29 ` Jussi Laako
-- strict thread matches above, loose matches on Subject: below --
2001-10-17 11:45 grouch
[not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
[not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
[not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
2001-10-15 11:09 grouch
2001-10-05 10:20 amit yajurvedi
2001-08-15 16:46 Via chipset Ryan C. Bonham
[not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
2001-08-07 23:10 Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox
2001-08-07 23:47 ` Larry McVoy
2001-08-08 9:16 ` Janne Pänkälä
2001-08-08 16:09 ` Marco Colombo
2001-08-15 3:25 ` Maxwell Spangler
2001-08-15 11:48 ` Alan Cox
2001-08-15 12:28 ` Bobby D. Bryant
2001-08-15 19:59 ` Dan Hollis
2001-08-15 20:16 ` Alan Cox
2001-08-15 20:27 ` Dan Hollis
2001-08-15 20:32 ` Alan Cox
2001-08-15 21:50 ` Bryan O'Sullivan
2001-08-16 15:35 ` Bob Martin
2001-08-16 21:09 ` Dan Hollis
2001-08-17 3:04 ` Adrian V. Bono
2001-08-20 22:52 ` Bob Martin
2001-08-08 1:54 ` Ignacio Vazquez-Abrams
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=3B9FCBB7.9020806@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@esi.it \
/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.