Re: [systemd-devel] [PATCH] usb-storage: Add quirk to defeat Kindle's automatic unload

From: Alan Stern <stern@rowland.harvard.edu>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: Greg KH <greg@kroah.com>,
	systemd-devel@lists.freedesktop.org,
	usb-storage@lists.one-eyed-alien.net, linux-usb@vger.kernel.org,
	Matthias Schwarzott <zzam@gentoo.org>,
	hirofumi@mail.parknet.co.jp, Mike Tsai <miketsai@amazon.com>
Subject: Re: [systemd-devel] [PATCH] usb-storage: Add quirk to defeat Kindle's automatic unload
Date: Thu, 18 Mar 2021 11:07:23 -0400	[thread overview]
Message-ID: <20210318150723.GC527768@rowland.harvard.edu> (raw)
In-Reply-To: <YFNalS7Sl/l+zywM@mother.pipebreaker.pl>

On Thu, Mar 18, 2021 at 02:50:13PM +0100, Tomasz Torcz wrote:
> Dnia Wed, Mar 17, 2021 at 03:06:54PM -0400, Alan Stern napisał(a):
> > Matthias reports that the Amazon Kindle automatically removes its
> > emulated media if it doesn't receive another SCSI command within about
> > one second after a SYNCHRONIZE CACHE.  It does so even when the host
> > has sent a PREVENT MEDIUM REMOVAL command.  The reason for this
> > behavior isn't clear, although it's not hard to make some guesses.
> 
>   Could Kindle be fixed not to required such workaround? Is there a way
> to open a bug with Amazon?

You really should be asking people who work for Amazon.  I suspect that 
nobody who regularly reads this mailing list knows the answer.

(If you look through the MAINTAINERS file, you'll find there are a few 
kernel developers who do work for Amazon, or at least, have @amazon.com 
email addresses.  Try asking some of them.)

But even if the Kindle firmware gets changed (which I doubt will 
happen), we would still want to support all the old devices that aren't 
running the updated firmware.

Alan Stern