public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Misha Nasledov <misha@nasledov.com>
To: Daniela Engert <dani@ngrt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA Serial ATA chipset
Date: Sun, 10 Aug 2003 23:06:34 -0700	[thread overview]
Message-ID: <20030811060634.GA10852@nasledov.com> (raw)
In-Reply-To: <20030811055522.31F6427A21@mail.medav.de>

On Mon, Aug 11, 2003 at 07:55:49AM +0200, Daniela Engert wrote:
> It's looking very similar to the standard ATA host register model, so
> it's probably nearly identical to existing VIA PATA controllers. To
> check this we need to know the actual PCI config space. What does lspci
> -s 0:f.0 -vvxx show?

Here is the output:
00:0f.0 RAID bus controller: VIA Technologies, Inc.: Unknown device
3149 (rev 80)
        Subsystem: VIA Technologies, Inc.: Unknown device 3149
        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
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 8800 [size=8]
        Region 1: I/O ports at 8400 [size=4]
        Region 2: I/O ports at 8000 [size=8]
        Region 3: I/O ports at 7800 [size=4]
        Region 4: I/O ports at 7400 [size=16]
        Region 5: I/O ports at 7000 [size=256]
        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-
00: 06 11 49 31 07 00 90 02 80 00 04 01 00 20 80 00
10: 01 88 00 00 01 84 00 00 01 80 00 00 01 78 00 00
20: 01 74 00 00 01 70 00 00 00 00 00 00 06 11 49 31
30: 00 00 00 00 c0 00 00 00 00 00 00 00 0b 01 00 00

Also, if SATA were to work, would there be any problem with accessing
the hard disk? Currently, I have two onboard IDE channels, a PCI IDE
card, and this SATA chip. I notice that the IDE hard disk devices only
go up to hdh in /dev. Would I be able to use all 6 of my IDE channels?
-- 
Misha Nasledov
misha@nasledov.com
http://nasledov.com/misha/

  parent reply	other threads:[~2003-08-11  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11  2:17 VIA Serial ATA chipset Misha Nasledov
     [not found] ` <20030811055522.31F6427A21@mail.medav.de>
2003-08-11  6:06   ` Misha Nasledov [this message]
     [not found]     ` <20030811062839.76F9216F24@mail.medav.de>
2003-08-11  6:34       ` Misha Nasledov
     [not found]         ` <20030811064757.7B1CF1C92C@mail.medav.de>
2003-08-11 22:34           ` Misha Nasledov
     [not found]             ` <20030812111332.351001ACFB@mail.medav.de>
2003-08-13  6:49               ` Misha Nasledov
2003-08-13  7:46                 ` Daniela Engert
2003-08-29 14:51                   ` libata update posted (was Re: VIA Serial ATA chipset) Jeff Garzik
2003-08-29 17:21                     ` Samuel Flory
2003-08-29 17:59                       ` Jeff Garzik
2003-08-29 18:09                         ` Samuel Flory

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=20030811060634.GA10852@nasledov.com \
    --to=misha@nasledov.com \
    --cc=dani@ngrt.de \
    --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