All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jo Lodewyckx <jo.lodewyckx@edpnet.be>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 3/3] sata_inic162x: finally, driver for initio 162x SATA controllers
Date: Sun, 28 Oct 2007 11:23:07 +0100	[thread overview]
Message-ID: <4724630B.9090405@edpnet.be> (raw)
In-Reply-To: <47225535.2040404@gmail.com>

Tejun Heo,

Here's the output of lspci -nnvvv:

03:00.0 SATA controller [0106]: Initio Corporation Unknown device 
[1101:1622] (rev 02) (prog-if 00 [Vendor specific])
        Subsystem: Initio Corporation Unknown device [1101:1626]
        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-
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at 4000 [size=256]
        Region 1: Memory at 40000000 (32-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at 30000000 [disabled] [size=128K]
        Capabilities: [dc] 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-

yours sincerely,

Jo Lodewyckx

Tejun Heo schreef:
> Hello,
>
> jo.lodewyckx@edpnet.be wrote:
>> When probing the module I did get an error and after some google fun, 
>> I stumbled upon you as being the
>> driving force behind this driver. This is the error I'm getting:
>> sata_inic162x 0000:03:00.0: version 0.2
>> PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
>> ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [C0C3] -> GSI 10 (level, 
>> low) -> IRQ 10
>> ACPI: PCI interrupt for device 0000:03:00.0 disabled
>> sata_inic162x: probe of 0000:03:00.0 failed with error -22
>>
>> Some more sysinfo:
>> Linux sip 2.6.22-gentoo-r8 #8 SMP PREEMPT Mon Oct 22 19:49:47 CEST 
>> 2007 i686 Intel(R) Pentium(R) M processor 1500MHz GenuineIntel GNU/Linux
>>
>> hopefully you can help me out on this one. I would be glad to act as 
>> "alpha/beta tester" for your driver :)
>
> 1. Please cc linux-ide@vger.kernel.org and 
> linux-pci@atrey.karlin.mff.cuni.cz
>
> 2. Post the result of "lspci -nnvvv".
>
> 3. Please note that sata_inic162x driver is only in half-working state 
> and virtually useless because it doesn't support LBA48 (drives bigger 
> than 128G).  I need more info to fix this problem but the vendor isn't 
> willing and I don't have time to find it out by trial-and-error.
>
> Thanks.
>


       reply	other threads:[~2007-10-28 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6403454.272891193414331004.JavaMail.nabble@isper.nabble.com>
     [not found] ` <47225535.2040404@gmail.com>
2007-10-28 10:23   ` Jo Lodewyckx [this message]
2007-10-29  3:24     ` [PATCH 3/3] sata_inic162x: finally, driver for initio 162x SATA controllers Tejun Heo
2006-12-16 10:48 [PATCH 1/3] libata: kill qc->nsect and cursect Tejun Heo
2006-12-16 10:48 ` [PATCH 2/3] libata: implement max_segment_size Tejun Heo
2006-12-16 10:49   ` [PATCH 3/3] sata_inic162x: finally, driver for initio 162x SATA controllers Tejun Heo

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=4724630B.9090405@edpnet.be \
    --to=jo.lodewyckx@edpnet.be \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.