[systemd-devel] Antw: [EXT] Re: [usb-storage] Re: Amazon Kindle disconnect after Synchronize Cache

Alan Stern stern at rowland.harvard.edu
Thu Mar 18 14:59:15 UTC 2021


On Thu, Mar 18, 2021 at 08:03:07AM +0100, Ulrich Windl wrote:
> >>> Lennart Poettering <lennart at poettering.net> schrieb am 17.03.2021 um 17:47
> in
> Nachricht <YFIyidaZZmDoTevB at gardel-login>:
> > I'd say quirks that are necessary to avoid data corruption should
> > better be done in the kernel and udev's hwdb stuff is only for stuff
> > that "fills in gaps", i.e. adds additional tweaks that make things
> > prettier, cleaner, nicer, more efficient but not things that make the
> > basic things work, and data integrity sounds pretty basic to me.
> 
> But seeing the list of bad, broken or ill-designed hardware grow year by year,
> I wonder whether we really want all that bloat in the kernel.
> 
> > 
> > Or to give a counter example: the device advertises it can do media
> > change, but actually cannot, right, it's not a floppy drive or cdrom
> > driver after all? maybe hwdb would thus actually be the place for the
> > opposite of the suggested fix: turn off the media change polling to
> > reduce needless wakeups.
> 
> I actually think it would be best if those work-arounds could be loadable as
> module, and the vendors of broken hardware can provide the modules that
> document their broken design as well.

If you can come up with a way to do this (preferably in the form of a 
patch), that would be great.  I can't think of any way to remove this 
information from the kernel.

Alan Stern


More information about the systemd-devel mailing list