mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Aryix <aryix@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: via82cxxx probable incorrect detection (urgency=low)........
Date: Sat, 14 Dec 2002 11:28:42 +0100	[thread overview]
Message-ID: <20021214112842.A8790@ucw.cz> (raw)
In-Reply-To: <courier.3DF9A5CE.00001047@softhome.net>; from aryix@softhome.net on Thu, Dec 12, 2002 at 08:14:53AM -0300

On Thu, Dec 12, 2002 at 08:14:53AM -0300, Aryix wrote:
> I am Argentino <- i don't speak english, please be patient
> 
> Kernel-2.4.20-final
> 
> lspci -vvv
> 
> 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) (prog-if 8
> a [Master SecP PriP])
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
> ping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
> - <MAbort- >SERR- <PERR-
>         Latency: 32
>         Region 4: I/O ports at d000 [size=16]
>         Capabilities: [c0] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot
> -,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 
> 
> cat /proc/pci
>  Bus  0, device   7, function  0:
>     ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 33).
>   Bus  0, device   7, function  1:
>     IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 16).
>       Master Capable.  Latency=32.  
>       I/O at 0xd000 [0xd00f].
> 
> dmesg 
> 
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: IDE controller on PCI bus 00 dev 39
> VP_IDE: chipset revision 16
> VP_IDE: not 100% native mode: will probe irqs later
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <- is my error?
> VP_IDE: VIA vt82c686a (rev 21) IDE UDMA66 controller on pci00:07.1
>     ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: QUANTUM FIREBALLlct20 30, ATA DISK drive
> hdc: ST36421A, ATA DISK drive
> hdd: ATAPI 44X CDROM, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> blk: queue c030a5c4, I/O limit 4095Mb (mask 0xffffffff)
> hda: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=3649/255/63, (U)DMA <- ??????????

The drive doesn't say to the OS which DMA mode is enabled on it.

> blk: queue c030a928, I/O limit 4095Mb (mask 0xffffffff)
> hdc: 12596850 sectors (6450 MB) w/256KiB Cache, CHS=13330/15/63, UDMA(66) <- this is ok
> hdd: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33) <- ok!
> 
> i have a chip via82c686a (Epox 7-kxa)
> at boot time is been detected via82c686a
> proc says via82c586b
> lspci -vvv no says 

Because all VIA IDE chips say they're 586b.

> the udma capabilities is not work propetly i set manually with "hdparm -m 8 -W 1 -X udma5 /dev/hda"

The chip doesn't support UDMA5. The highest speed it supports
is UDMA3 (UDMA66).

> whats happening here?

Nothing unusual.

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2002-12-14 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 11:14 Aryix
2002-12-14 10:28 ` Vojtech Pavlik [this message]

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=20021214112842.A8790@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=aryix@softhome.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

Powered by JetHome