From: Hans de Goede <hdegoede@redhat.com>
To: Oliver Neukum <oneukum@suse.com>, Julian Sikorski <belegdol@gmail.com>
Cc: Nathan Stratton Treadway <vgerlists@nathanst.com>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Mon, 13 Sep 2021 13:50:26 +0200 [thread overview]
Message-ID: <2167ea48-e273-a336-a4e0-10a4e883e75e@redhat.com> (raw)
In-Reply-To: <1f6c3026-143a-2004-24da-1da56e6305be@suse.com>
Hi,
On 9/13/21 1:06 PM, Oliver Neukum wrote:
>
> On 13.09.21 09:38, Hans de Goede wrote:
>>> Hi,
>>>
>>> I have just updated my backups with f+k quirks enabled and everything worked without errors. Given that nobody appears to be aware of a sure test case for checking whether f alone is sufficient, should I just generate a patch enabling fk instead of u?
>> Yes I believe that switching from fk to u, like done on the other Lacie entries is best.
>
> Hi,
>
> just to be sure that we are really on the same page.
>
> Do you really want to go to u - US_FL_IGNORE_UAS? The other one
> has fk - US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME
We currently have u - US_FL_IGNORE_UAS, because Julian's initial patch
did that and that was merged.
What we are talking about now, is moving from the big-hammer 'u'
to fk - US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME, since testing
has show that just 'fk' is enough, allowing us to keep using uas.
> I may be a bit confused and I think we need to make sure first, that we are
> talking about the same things.
I hope that my reply above helps to clear things up.
Regards,
Hans
prev parent reply other threads:[~2021-09-13 11:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 13:31 Lacie Rugged USB3-FW does not work with UAS Julian Sikorski
2019-08-23 13:39 ` Oliver Neukum
2019-08-23 13:43 ` Julian Sikorski
2019-08-23 14:21 ` Julian Sikorski
2019-08-23 21:23 ` Oliver Neukum
2019-08-24 7:08 ` Julian Sikorski
2019-08-29 18:33 ` Julian Sikorski
2019-09-02 11:42 ` Oliver Neukum
2019-09-02 20:10 ` Julian Sikorski
2019-09-04 15:58 ` Nathan Stratton Treadway
2019-09-04 17:10 ` Julian Sikorski
2019-09-09 12:45 ` Oliver Neukum
2019-09-09 16:18 ` Julian Sikorski
2021-07-17 8:28 ` Julian Sikorski
2021-07-19 12:47 ` Oliver Neukum
2021-07-19 16:10 ` Julian Sikorski
2021-07-20 7:43 ` Greg KH
2021-07-20 9:35 ` Oliver Neukum
2021-07-27 21:19 ` Hans de Goede
[not found] ` <CA+xVL_QEgzb1tu-tzqYPxJF-G_a8czCp=uyZ1JJ9+5xmCcNp2Q@mail.gmail.com>
[not found] ` <CA+xVL_QrJ9f8-BwVRq1oG_yo2Cd=yQH9=TCm5g=MUO9MmdvRVA@mail.gmail.com>
2021-07-29 8:43 ` Oliver Neukum
2021-07-29 9:08 ` Hans de Goede
2021-08-01 7:36 ` Julian Sikorski
2021-08-01 8:46 ` Hans de Goede
[not found] ` <a645c513-794f-5171-d383-7b40fbb1ba18@gmail.com>
2021-08-01 7:47 ` Julian Sikorski
2021-09-12 20:13 ` Julian Sikorski
2021-09-13 7:38 ` Hans de Goede
[not found] ` <1f6c3026-143a-2004-24da-1da56e6305be@suse.com>
2021-09-13 11:50 ` Hans de Goede [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=2167ea48-e273-a336-a4e0-10a4e883e75e@redhat.com \
--to=hdegoede@redhat.com \
--cc=belegdol@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=vgerlists@nathanst.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).