All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Julian Sikorski <belegdol@gmail.com>, linux-usb@vger.kernel.org
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Fri, 23 Aug 2019 23:23:13 +0200	[thread overview]
Message-ID: <1566595393.8347.56.camel@suse.com> (raw)
In-Reply-To: <0eaecb64-4c67-110d-8493-31dd7fd58759@gmail.com>

Am Freitag, den 23.08.2019, 16:21 +0200 schrieb Julian Sikorski:
> 
> I did some further digging regarding whether this is a regression: the
> quirk file on the laptop is from 15 July 2014. The machine is from ca.
> May 2011. Looking through my earlier posts to linux-usb it appears that
> the addition of the quirk is related to this thread:
> 
> https://marc.info/?l=linux-usb&m=140537519907935&w=2
> 
> At the same time, back in 2011, I reported that the drive was working
> after some fixes:
> 
> https://marc.info/?l=linux-usb&m=132276407611433&w=2

Hi,

this is alarming. Was this physically the same drive? I am asking
because we have seen cases where two different devices were sold
under the same name.

	Regards
		Oliver


  reply	other threads:[~2019-08-23 21:23 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 [this message]
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

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=1566595393.8347.56.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=belegdol@gmail.com \
    --cc=linux-usb@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.