drivers/usb/storage/unusual_devs.h
> @@ -2259,6 +2259,24 @@ UNUSUAL_DEV( 0x1e74, 0x4621, 0x, 0x,
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_BULK_IGNORE_TAG | US_FL_MAX_SECTORS_64 ),
>
> +/*
> + * Using an Android phone as USB storage back-end for Chrome OS recovery. See
> + * usb/storage/cros-aoa.c for details.
> + */
> +#if defined(CONFIG_USB_STORAGE_CROS_AOA) || \
> + defined(CONFIG_USB_STORAGE_CROS_AOA_MODULE)
> +UNUSUAL_DEV( 0x18d1, 0x2d00, 0x, 0x,
> + "Google",
> + "Chrome OS Recovery via AOA",
> + USB_SC_SCSI, USB_PR_BULK, usb_stor_cros_aoa_validate,
> + US_FL_SINGLE_LUN | US_FL_CAPACITY_OK),
> +UNUSUAL_DEV( 0x18d1, 0x2d01, 0x, 0x,
> + "Google",
> + "Chrome OS Recovery via AOA (with ADB)",
> + USB_SC_SCSI, USB_PR_BULK, usb_stor_cros_aoa_validate,
> + US_FL_SINGLE_LUN | US_FL_CAPACITY_OK),
> +#endif /* defined(CONFIG_USB_STORAGE_CROS_AOA) || ... */
> +
> /* Supplied with some Castlewood ORB removable drives */
> UNUSUAL_DEV( 0x2027, 0xa001, 0x, 0x,
> "Double-H Technology",
> --
> 2.20.1
>
--
Matthew Dharm
Former Maintainer, USB Mass Storage driver for Linux
unaffected. It did
> result in me purchasing a few replacement USB cables in an attempt to
> remove the warning.
>
> Anything I can do to "fix" this? I have verified the USB reader
> (FCR-HS3) is running the latest
> firmware from Kingston.
>
> I am running Linux
rom this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Dharm
Former Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from
>
> Find attached the pcap file for both cases and part of the kernel dmesg.
> This is the kernel with the problem: Linux arbo 4.9.0-4-amd64 #1 SMP
> Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux
>
> Eduardo.
>
--
Matthew Dharm
Former Maintainer, USB Mass Storage
Stern
>> Cc: Oliver Neukum
>> Signed-off-by: Greg Kroah-Hartman
>> ---
>
> Acked-by: Alan Stern
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@vger.kernel.org
> More majordomo i
1 08 01 00 00 00
> eb 87 41 ff c9 75 04 f3 c3 f3 90 <8b> 07 84 c0 75 f8 66 c7 07 01 00 c3 f3 90
> 4c 8b 09 4d 85 c9 74
>
> I'm happy to supply extra configuration information and run tests.
>
> If it is worthwhile doing a git-bisect on usb-storage I could do that also.
>
> Arthur.
--
Matthew Dharm
Former Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Aug 30, 2016 at 10:19 AM, Greg KH wrote:
> On Thu, Aug 25, 2016 at 08:52:38AM -0700, Matthew Dharm wrote:
>> On Thu, Aug 25, 2016 at 8:30 AM, Alan Stern
>> wrote:
>> > At Matt Dharm's request, I am taking over maintainership of the
>> > usb-stora
s finally got me off-the-bubble.
> Signed-off-by: Alan Stern
Acked-by: Matthew Dharm
>
> ---
>
>
> [as1811]
>
>
> MAINTAINERS |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: usb-4.x/MAINTAINERS
> ==
> drivers/usb/storage/usb.c
>
>
>
> Best Regards,
>
> Pengcheng Li
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More
bps)
> bU1DevExitLat 10 micro seconds
> bU2DevExitLat 32 micro seconds
> Device Status: 0x000d
> Self Powered
> U1 Enabled
> U2 Enabled
>
> The issue is Linux specific, because the same machine when booted in Windows
> 7
> det
ees a "newer" device, which should
hopefully behave better.
Matt
On Thu, Oct 29, 2015 at 1:56 PM, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
>> On Thu, 29 Oct 2015, Matthew Dharm wrote:
>>
>>> Uhh... I think this is a bad idea. The 120K limit was
>
> /* merge commands... this seems to help performance, but
> * periodically someone should test to see which setting is more
> --
> 2.6.2
>
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
e it yanked-out from underneath us by this
unprompted mode switch that the device does.
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
gt; not spun up yet, and in both cases the uas and usb-storage modules are loaded
> beforehand (albeit with a larger delay in the second case). That is: what is
> the difference from the drive's perspective?
>
> (Also, why does Windows, without any manually installed drivers, work,
t; /*
>>* Some devices don't like GetMaxLUN. They may STALL the control
>
> Apart from that minor issue,
>
> Acked-by: Alan Stern
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@v
> http://www.mediafire.com/download/uw4d4dmcq8qfbwg/Iomega_SCSI-USB_problem.tar.gz
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-in
On Sat, Aug 30, 2014 at 2:15 PM, Alan Stern wrote:
> On Fri, 29 Aug 2014, Matthew Dharm wrote:
>
>> Is there an 'easy' way to override the detected size of a storage
>> device from userspace? If we had that, someone could write a helper
>> application which lo
the Windows workaround is icky, but it allows any use
> but repartitioning to be one on the attached disk.
>
> Dale
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info
I'm okay with these patches. No need to resend to the USB Storage
list, tho I would appreciate such in the future.
Acked-By: Matthew Dharm
Matt
On Wed, Dec 4, 2013 at 3:58 PM, Sarah Sharp
wrote:
> On Mon, Nov 18, 2013 at 03:39:05PM +0100, Hans de Goede wrote:
>> Hi Sarah et a
I'm happy with it, modulo Sergi's grammer comment.
ACKed-by: Matthew Dharm mdharm-...@one-eyed-alien.net
Matt
On Mon, Mar 4, 2013 at 1:57 PM, Bjørn Mork wrote:
> Signed-off-by: Bjørn Mork
> ---
> So, is something like this good enough?
>
>
> Bjørn
>
>
bout the issue years ago. Putting a comment in
> the code to remind the current maintainers about their own statements
> could be considered out of line? Or is this appropriate here?
>
>
> Bjørn
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubs
in
transport.c
Care to submit a patch to Greg?
Matt
On Wed, Feb 27, 2013 at 4:33 AM, Dan Carpenter wrote:
> Hello Matthew Dharm,
>
> This is an old warning but it looks like it might be valid.
>
> The patch 34008dbfe8c0: "[PATCH] USB Storage: add support for Maxtor
> One-Touch
hcd
>> Jan 28 21:32:56 localhost kernel: usb 7-1.2: new SuperSpeed USB device
>> number 4 using xhci_hcd
>> Jan 28 21:32:56 localhost kernel: usb 7-1.3: new SuperSpeed USB device
>> number 5 using xhci_hcd
>> Jan 28 21:32:56 localhost kernel: usb 7-1.4: new SuperSpeed
th verbose USB logging while connecting
> the E-reader. This is with today's kernel git + nouveau git of today
> (v3.8-rc7+). It's pretty big btw...
>
> I also enabled verbose SCSI logging, but didn't see some of that come
> back in the logs.
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
r patches. Outlook commonly mangles patches, unfortunately.
It is not a very good e-mail client.
I suggest one of two options:
1) Setup an alternative mail client. There are many to choose from
which will not damage your patches. I personally like 'mutt' (which
you should be able to ins
Let me try this again...
It looks fine to me.
Acked-by: Matthew Dharm
Matt
On Sat, Jan 19, 2013 at 10:47 AM, Alan Stern wrote:
> On Sat, 19 Jan 2013, Ming Lei wrote:
>
>> This patch sets scsi_host->max_id as 1 if the device's quirk
>> flag of US_FL_SCM_MULT_TARG is
On Sun, 23 Dec 2012 11:45:31 -0800
> Matthew Dharm
> wrote:
>
>> The breakpoint between SDSC and SDHC is, in fact, 4GB for 512-byte
>> sectors. So, your data supports my theory that your cardreader is
>> non-SDHC compatible.
>
> I tried the 4GB microSD and the sympt
The breakpoint between SDSC and SDHC is, in fact, 4GB for 512-byte
sectors. So, your data supports my theory that your cardreader is
non-SDHC compatible.
Matt
On Sun, Dec 23, 2012 at 11:19 AM, rh wrote:
> On Sun, 23 Dec 2012 11:01:28 -0800
> Matthew Dharm
> wrote:
>
>> If
8.489866] hub 3-0:1.0: unable to enumerate USB device on port 1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Dharm
Maintainer, USB Mass Storage driver for Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
. BUT, your code includes
many more PIDs than the table did. Again, how was this tested for the
new PIDs covered? At a minimum, some comment in dongles_pid is
required to highlight this area of code for possible future expansion
as new devices are released.
Matt
--
Matthew Dharm
Maintainer, USB
ou don't use raid, use raid=noautodetect
> md: Autodetecting RAID arrays.
> md: Scanned 0 and added 0 devices.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Mounted root (iso9660 filesystem) readonly on device 11:0.
> devtmpfs: mounted
> Freeing unused kernel memory: 656k freed
>
>
tocol?
It's a limitation of the particular USB/ATA bridge device you're using.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
It was a new hope.
-- Dust Puppy
User Friendly, 12/25/1998
pgp7cxaAuQAtw.pgp
Description: PGP signature
ol?
The protocol will carry the commands just fine. The problem is that most
USB/ATA converter chips won't translate the command properly.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
It was a new ho
On Tue, Feb 12, 2008 at 03:51:22PM -0500, Alan Stern wrote:
> On Sat, 2 Feb 2008, Matthew Dharm wrote:
>
> > On Sat, Feb 02, 2008 at 05:12:29PM -0500, Alan Stern wrote:
> > > IMO this indicates we shouldn't issue any clear-halts at all unless the
> > > device
of how that flow is controlled, but not the data itself.
usb-storage never actually dumps out the data blocks being exchanged, only
the transport framing and packing of those exchanges.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage
seem to have a bad cable
> Registration Error: There are problems with registering the
> device. It may have a bad XYZ command processing
There are some messages like that for errors that generally only happen
with bad cables. This is not one of those.
Matt
--
Matthew Dharm
trace of htat would shed some light on this
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
What the hell are you?
-- Pitr to Dust Puppy
User Friendly, 12/3/1997
pgpOgZjGjVXDL.pgp
Description: PGP signature
>
> Shouldn't it be /dev/ube1 instead of ude1 ??
>
> In any case, a full dmesg output with CONFIG_USB_STORAGE_DEBUG enabled
> would be great.
That probably wouldn't help; it looks like he's using the ub driver, not
usb-storage.
Matt
--
Matthew Dharm
On Wed, Feb 06, 2008 at 03:23:39PM -0500, Alan Stern wrote:
> On Tue, 5 Feb 2008, Matthew Dharm wrote:
>
> > Six of one and a half-dozen of the other. All we're arguing over is the
> > definition of "correct behavior" here. You want to change the API so t
On Mon, Feb 04, 2008 at 03:05:58PM -0500, Alan Stern wrote:
> On Sun, 3 Feb 2008, Matthew Dharm wrote:
>
> I think the correct approach is to modify those routines so that they
> will never overrun the s-g buffer (like Boaz has done), and _document_
> this behavior. Then the c
ecture - just lets call
> > them mashineA, mashineB and mashineC.
>
> Is the kernel the same on all of these machines?
I'm not sure it matters...
usb-storage has no knowledge of CHS geometery. It deals entirely in LBA.
Does anyone know where the kernel gets the CHS g
s much as possible.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
Type "format c:" That should fix everything.
-- Greg
User Friendly, 12/18/1997
pgpg0qLfBYeeo.pgp
Description: PGP signature
) to not attempt to use more
SCSI buffer than exists.
My opinion is this: Let's make the protocol.c mods (modulo my comments
about setting useless status bits) now. Then, let's decide if we're going
to patch all the other users of the usb_stor_*_xfer_buf() functions as a
separate d
On Sat, Feb 02, 2008 at 10:30:51PM -0500, Alan Stern wrote:
> On Sat, 2 Feb 2008, Matthew Dharm wrote:
>
> > On Sat, Feb 02, 2008 at 05:12:29PM -0500, Alan Stern wrote:
> > > IMO this indicates we shouldn't issue any clear-halts at all unless the
> > > device
be on the
lookout for reports of very old ZIP-100 drives breaking.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
Somebody call an exorcist!
-- Dust Puppy
User Friendly, 5/16/1998
pgps8Umt5SEwf.pgp
Description: PGP signature
s.
> >>>Maybe then the device will work...
> >>>
> >>>
> >>>
> >>IT WORKS.
> >>
> >
> >And just out of curiousity, what happens if you remove the
> >usb_stor_clear_halt() entirely?
> >
> >
&g
clearing halts on all endpoints before we talk
> additional quirks.
This is my position exactly. I speculate that the windows-issued
clear-halt on ep0 is required by the device.
There's no way to know until Robert tests with no clear-halt at all.
Matt
--
Matthew Dharm
On Fri, Feb 01, 2008 at 11:59:56AM -0500, Alan Stern wrote:
> On Fri, 1 Feb 2008, Matthew Dharm wrote:
>
> > On Fri, Feb 01, 2008 at 10:17:24AM -0500, Alan Stern wrote:
> > > On Thu, 31 Jan 2008, David Brownell wrote:
> > >
> > > > On Thursday 31 Jan
ys to do so but because one ancient device (a ZIP-100) requires it.
> Now it looks as though we've found a device which can't handle it.
> Time for another quirk?
Do we really need another quirk? If the 'popular' OS does it, it's likely
safe to do for all deveice
On Thu, Jan 31, 2008 at 10:05:19PM +0200, Boaz Harrosh wrote:
> On Thu, Jan 31 2008 at 21:49 +0200, Matthew Dharm <[EMAIL PROTECTED]> wrote:
> > No. No no no.
>
> Please re-inspect the code again.
> There is no device involved here. The code completely emulates this comma
> - usb_stor_access_xfer_buf(buffer, buflen, srb, &sg, &offset,
> + count = usb_stor_access_xfer_buf(buffer, buflen, srb, &sg, &offset,
> TO_XFER_BUF);
> - if (buflen < srb->request_bufflen)
> - srb->resid = srb->
On Tue, Jan 29, 2008 at 08:15:04PM +0100, Jens Axboe wrote:
> On Tue, Jan 29 2008, Matthew Dharm wrote:
> > On Tue, Jan 29, 2008 at 07:39:11PM +0100, Jens Axboe wrote:
> > > On Tue, Jan 29 2008, Jens Axboe wrote:
> > > > On Tue, Jan 29 2008, Oliver Neukum wrote:
>
fer_sglist: xfer 18 bytes, 1 entries
> usb-storage: usb_sg_init returned -22
> usb-storage: Bulk data transfer result 0x4
> usb-storage: -- auto-sense failure
> usb-storage: storage_pre_reset
> ehci_hcd :00:1d.7: port 1 high speed
> ehci_hcd :00:1d.7: GetStatus por
27;t added any USB patches to the -git tree
> > yet after 2.6.24 :)
> >
> > Could this be caused by some scsi changes perhaps?
> >
> > thanks,
> >
> > greg k-h
> > -
> Yes it is ;)
>
> Jens could you test the patch below? if it works I&#x
ACKed-by: Matthew Dharm <[EMAIL PROTECTED]>
Matt
On Fri, Jan 25, 2008 at 11:12:21AM -0600, James Bottomley wrote:
> On Thu, 2008-01-24 at 09:21 -0800, Greg KH wrote:
> > On Thu, Jan 24, 2008 at 06:07:00PM +0100, Stefan Richter wrote:
> > > Greg KH wrote:
> > >
ss
defines the protocol (i.e. language) the device uses; the "Protocol"
defines the transport (i.e. how messages are packed for exchange).
There is no USB-spec field named 'Transport'.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux
On Mon, Jan 14, 2008 at 10:33:08AM -0600, James Bottomley wrote:
>
> On Mon, 2008-01-14 at 08:03 -0800, Matthew Dharm wrote:
> > We may be able to convince the SCSI people to enable it for all devices,
> > regardless of HCD.
>
> No ... I'm not particularly keen to
ince the SCSI people to enable it for all devices,
regardless of HCD.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
What the hell are you?
-- Pitr to Dust Puppy
User Friendly, 12/3/1997
pgpRWo6penKzA.pgp
Description: PGP signature
g a multi-interface
device based on the interface class code, but I don't see a better solution
that isn't a major coding project.
This approach looks pretty reasonable to me.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Stora
a flag to indicate that it should be used, if really desired.
But, it seems to me to be a much easier change to make where the command
originated rather than in mid-flight.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
P: Nine
o with USB.
I agree. The usb-storage driver isn't even getting bound to the device,
which is a different problem than was being reported in the URL Sean
provided. That URL showed a device enumerating at least somewhat
successfully and then failing during a SCSI reset.
allocation calls in the URB submission paths. I would expect those calls
to fail when under memory pressure.
Matt
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
Oh BAY-bee.
-- Dust Pu
but no solutions.
>
> Any linux diagnostics that would be useful?
Looking at that link, it seems likely that you cut too much from your logs.
Can you show us more? Specifically, the link shows some SCSI messages that
you do not...
Matt
--
Matthew Dharm
mputer's USB controller isn't working.
> >
> >You can try attaching the drive to a different computer or attaching
> >different high-speed USB devices to your computer. That should
> >indicate which component is at fault.
> >
> >Alan
the first partition. And then of course you'll have to
> recreate the VFAT filesystem on it.
That will work, but I don't think it's optimal.
Looking at the logs provided, I think this might be one of those devices
that doesn't like reading the last sector if it's par
on what
> to do would be greatly appreciated.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Dharm
sd_mod be loading automatically? Or should I add it
> to /etc/modules? Currently I'm only autoloading ohci-hcd and everything
> else USB needs seems to be pulled in as needed.
>
> Thanks!
>
> Steve
>
> On Sat, 2007-12-22 at 00:05 -0800, Matthew Dharm wrote:
> > I
anks!
>
> Steve
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Dha
68 matches
Mail list logo
