From: Niklas Cassel <cassel@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Cryptearth <cryptearth@googlemail.com>,
temnota.am@gmail.com, linux-ide@vger.kernel.org,
conikost@gentoo.org, Ioannis Barkas <jnyb.de@gmail.com>
Subject: Re: Fwd: Re[2]: ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers
Date: Mon, 18 Mar 2024 12:31:10 +0100 [thread overview]
Message-ID: <Zfgl_n1hra6xSYIK@ryzen> (raw)
In-Reply-To: <65cd50b1-4f54-4f47-89d8-65b4ef2c0549@redhat.com>
Hello Hans,
On Mon, Mar 18, 2024 at 12:07:37PM +0100, Hans de Goede wrote:
> >
> > So I have honestly no idea how this works...
> >
> > Perhaps the ASMedia firmware takes the command to port0-port3,
> > and instead of sending it to the PMP, it sends back some faked
> > reply instead?
>
> Yes I believe that this is what is happening, the physical-ports 0-3
> are obviously connected to the JMB575 Port Multipliers, but I believe
> the "emulated" ports seen by the OS are mapped like this:
>
> 0-3 Only show as connected to the OS is connected directly to a disk
> without a PMP
> 4-19 Only show as connected to the OS when PMPs are used and the mapped
> port on the PMP has a disk connected
>
I'm not sure, see:
https://lore.kernel.org/linux-ide/CADUzMVaFcD26QiBK_eKCbtC5Ot-+hAruNbUx+2pQNTKtMhDGRA@mail.gmail.com/
Ioannis has an external PMP, and on v6.6,
he sees two disks.
But on v6.8 he only sees one disk.
It is a bit unfortunate that he did not provide a full boot log,
but he claims that both disks are connected to the same PMP.
Kind regards,
Niklas
next prev parent reply other threads:[~2024-03-18 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFDm6W19R3KHDO09c94Uwry9mdG+whAVy=u4Sdpt30A2MK1KPA@mail.gmail.com>
2024-03-13 6:36 ` ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers Andrey Melnikov
2024-03-13 17:37 ` Cryptearth
2024-03-13 21:21 ` Hans de Goede
2024-03-13 21:52 ` Re[2]: " Conrad Kostecki
2024-03-13 22:20 ` Hans de Goede
2024-03-16 14:01 ` Andrey Jr. Melnikov
2024-03-17 1:34 ` Cryptearth
2024-03-14 15:58 ` Niklas Cassel
2024-03-15 15:01 ` Hans de Goede
2024-03-16 11:33 ` Cryptearth
2024-03-16 11:45 ` Re[2]: " Conrad Kostecki
[not found] ` <CAFDm6W2nCj+qw=-7Sb9xcJTYZ8sitwUriR+Qdh9fo9+ET1Oo=g@mail.gmail.com>
2024-03-17 22:58 ` Fwd: " Cryptearth
2024-03-17 23:04 ` Christoph Hellwig
[not found] ` <CAFDm6W2X_2Nhn4ZeDd-=6Sra-evDW8Dx_CE0m5yggXpOXNTQ9g@mail.gmail.com>
2024-03-17 23:25 ` Christoph Hellwig
[not found] ` <CAFDm6W3pe+nv5CTcEq2FwGbKS4Cdu+7xdLa1Zy6iODampfwxsw@mail.gmail.com>
2024-03-17 23:48 ` Christoph Hellwig
2024-03-18 10:56 ` Niklas Cassel
2024-03-18 11:07 ` Hans de Goede
2024-03-18 11:31 ` Niklas Cassel [this message]
2024-03-18 11:53 ` Damien Le Moal
2024-03-18 14:21 ` Hans de Goede
2024-03-18 23:59 ` Damien Le Moal
2024-03-17 9:36 ` Niklas Cassel
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=Zfgl_n1hra6xSYIK@ryzen \
--to=cassel@kernel.org \
--cc=conikost@gentoo.org \
--cc=cryptearth@googlemail.com \
--cc=hdegoede@redhat.com \
--cc=jnyb.de@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=temnota.am@gmail.com \
/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.