From: Marc Wilson <msw@cox.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Via-Rhine dirve in 2.4.21-pre7
Date: Thu, 17 Apr 2003 19:47:09 -0700 [thread overview]
Message-ID: <20030418024709.GD14527@moonkingdom.net> (raw)
In-Reply-To: <20030417175924.GE25696@gtf.org>
On Thu, Apr 17, 2003 at 01:59:24PM -0400, Jeff Garzik wrote:
> Until further notice, please do not attempt to use Via IOAPIC support.
> This has nothing to do with via-rhine, and remains an open issue.
I thought I'd read everything about the Rhine and Via in my lurking on
lkml, but I must have missed something. This box here is an Abit KD7-RAID
(Via KT400 + Rhine II) and I have IOAPIC enabled and am using Roger's latest
driver with 2.4.21-pre6 with great success.
rei $ uname -a
Linux rei 2.4.21-pre6-preempt #1 Mon Mar 31 17:05:40 PST 2003 i686 unknown unknown GNU/Linux
rei $ cat /var/log/dmesg | egrep -i "via|rhine"
PCI: Using IRQ router VIA [1106/3177] at 00:11.0
PCI: Via IRQ fixup for 00:10.0, from 10 to 5
PCI: Via IRQ fixup for 00:10.2, from 11 to 5
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
agpgart: Detected Via Apollo Pro KT400 chipset
via-rhine.c:v1.10-LK1.1.17 March-1-2003 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT6102 Rhine-II at 0xd800, 00:50:8d:45:af:b7, IRQ 23.
rei $ grep APIC /usr/src/linux/.config
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
What am I missing here? It sounds like it's dangerous to use, but it
doesn't look like it's broken.
--
Marc Wilson | One big pile is better than two little piles. --
msw@cox.net | Arlo Guthrie
next prev parent reply other threads:[~2003-04-18 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 9:10 Via-Rhine dirve in 2.4.21-pre7 Mark Syms
2003-04-07 11:26 ` Roger Luethi
2003-04-17 17:53 ` Mark Syms
2003-04-17 17:59 ` Jeff Garzik
2003-04-18 2:47 ` Marc Wilson [this message]
2003-04-18 3:21 ` Jeff Garzik
2003-04-17 19:34 ` Roger Luethi
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=20030418024709.GD14527@moonkingdom.net \
--to=msw@cox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox