All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ioannis Barkas <jnyb.de@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: The SATA_ini162x.
Date: Wed, 22 Feb 2023 23:28:54 +0200	[thread overview]
Message-ID: <CADUzMVb+JbwxiKxrxjAep8Gbom_ynM7Os67_gTEHC-dJFAVL0g@mail.gmail.com> (raw)

Hello Magnus,

I will give you more details about it since I reported the issue with
this controller many years ago.

Yes you can activate the driver but you will need to enable this
driver and build your own kernel. That is needed since the driver is
disabled by default. There is at least one underlying issue that has
got unnoticed and has not been solved yet thus the driver is
considered experimental. My PCI card has an eSATA connector routed to
port 0 and a SATA connector routed to port 1. Back then, I had tested
the SATA port and believed that the driver could only handle port 0.

Damien if you are willing to investigate this and help me fix it, I am
at your disposal. I still have the card with this controller, the
datasheet of the IC manufacturer, an AMD based PC with a PCI slot and
lots of disks for testing. What is more, I had done some tests back in
December and the issue remains. Here is what 6.1 prints:
[    1.947670] sata_inic162x 0000:05:06.0: version 0.4
[    1.947716] sata_inic162x 0000:05:06.0: inic162x support is broken
with common data corruption issues and will be disabled by default,
contact linux-ide@vger.kernel.org if in production use

Here is the problem:
[    3.285163] ata8.00: native sectors (1) is smaller than sectors (976773168)

I tested the eSATA port and it behaves exactly the same as the SATA
port. I have also performed some modifications but those were in the
wrong direction as I completely broke the driver thus it could not
detect attached devices. That brought a libata bug to the surface and
I need to send a patch about it. Back to sata_inic, I have not figured
out how it works with both channels.

Hope to get better Magnus really soon!

Best regards.

             reply	other threads:[~2023-02-22 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 21:28 Ioannis Barkas [this message]
2023-02-22 23:43 ` The SATA_ini162x Damien Le Moal
2023-04-04 19:59   ` Ioannis Barkas
  -- strict thread matches above, loose matches on Subject: below --
2023-02-12 14:53 Magnus Elfvendahl
2023-02-13  1:55 ` Damien Le Moal

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=CADUzMVb+JbwxiKxrxjAep8Gbom_ynM7Os67_gTEHC-dJFAVL0g@mail.gmail.com \
    --to=jnyb.de@gmail.com \
    --cc=linux-ide@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 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.