From: Vojtech Pavlik <vojtech@suse.cz>
To: Piotrek Kaczmarek <kaczorek@msg.beta.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA VT82C416MV support
Date: Wed, 29 Aug 2001 22:26:06 +0200 [thread overview]
Message-ID: <20010829222606.A14042@suse.cz> (raw)
In-Reply-To: <20010828210426.A278@msg.beta.pl>
In-Reply-To: <20010828210426.A278@msg.beta.pl>; from kaczorek@msg.beta.pl on Tue, Aug 28, 2001 at 09:04:26PM +0200
On Tue, Aug 28, 2001 at 09:04:26PM +0200, Piotrek Kaczmarek wrote:
> Hi,
> I use 2.4.10-pre1-xfs series kernel (cvs checkout 2001-08-28)
> on a P133 based on a motherboard (don't remeber the manufacturer)
> with some VIA IDE controller, which seems to be
> PCI_IDE: unknown IDE controller on PCI bus 00 device 08, VID=1106, DID=1571
> for IDE driver....
> VIA_82CXXX suport is compiled in kernel
>
> Unfortunately i was unable to use UDMA33 mode with my
> FUJITSU MPF3204AT, ATA DISK drive (20496MB w/512KiB Cache)
> Aug 22 22:32:49 vigo kernel: ide0: unexpected interrupt, status=0x58, count=2
> Aug 22 22:33:03 vigo kernel: ide0: unexpected interrupt, status=0x58, count=3
> Aug 22 22:33:12 vigo kernel: ide0: unexpected interrupt, status=0x58, count=4
> Aug 22 22:33:22 vigo kernel: ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
> Aug 22 22:33:22 vigo kernel: hda: lost interrupt
> Aug 22 22:33:22 vigo kernel: hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
> Aug 22 22:33:22 vigo kernel: hda: status timeout: status=0xd0 { Busy }
> Aug 22 22:33:22 vigo kernel: hda: DMA disabled
> Aug 22 22:33:22 vigo kernel: ide0: unexpected interrupt, status=0xd0, count=5
> Aug 22 22:33:22 vigo kernel: hda: drive not ready for command
> Aug 22 22:33:22 vigo kernel: ide0: reset: success
>
> Here's my lspci -vvv output
> 00:01.0 IDE interface: VIA Technologies, Inc. VT82C416MV (rev 04) (prog-if 8a [Master SecP PriP])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32
> Region 4: I/O ports at 6000 [size=16]
> Is that controller supported in 2.4 kernels ? or maybe i am missing something?
>
> I'd be appreciated for any response
Wow, this must be a very ancient hardware! If you send me lspci -vvxxx,
I'll take a look and perhaps we could make it work.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-08-29 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 19:04 VIA VT82C416MV support Piotrek Kaczmarek
2001-08-29 20:26 ` Vojtech Pavlik [this message]
[not found] ` <20010829231544.A4305@msg.beta.pl>
2001-08-31 20:44 ` Vojtech Pavlik
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=20010829222606.A14042@suse.cz \
--to=vojtech@suse.cz \
--cc=kaczorek@msg.beta.pl \
--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