On Tue, Jun 07, 2005 at 01:37:21PM -0400, Alan Stern wrote:
> On Tue, 7 Jun 2005, Greg KH wrote:
>
> > On Tue, Jun 07, 2005 at 11:44:48AM -0400, Alan Stern wrote:
> > > There are other, more general sorts of objections. For example, it's a
> > > mistake to try putting device-specific information
On Tue, 7 Jun 2005, Greg KH wrote:
> On Tue, Jun 07, 2005 at 11:44:48AM -0400, Alan Stern wrote:
> > There are other, more general sorts of objections. For example, it's a
> > mistake to try putting device-specific information in a module parameter
> > (which, by its very nature, should apply t
On Tue, Jun 07, 2005 at 11:44:48AM -0400, Alan Stern wrote:
> There are other, more general sorts of objections. For example, it's a
> mistake to try putting device-specific information in a module parameter
> (which, by its very nature, should apply to all devices managed by that
> driver).
T
On Tue, 7 Jun 2005, Alex Butcher wrote:
> How about a module parameter for usb-storage?
>
> ignorequirks=<0|1>
> 0=use unusual_devs.h (default)
> 1=ignore unusual_devs.h
>
> or possibly, more flexibly:
> ignorequirks=,,<0|1>
This wouldn't solve the proble
On Tue, 7 Jun 2005, Alan Stern wrote:
On Mon, 6 Jun 2005, Phil Dibowitz wrote:
Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
design geniuses at Prolific we're caught in a "damned if you do, damned if
you don't" situation.
What about a sysfs option or sysctl?
I'm n
On Mon, 6 Jun 2005, Phil Dibowitz wrote:
> > Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
> > design geniuses at Prolific we're caught in a "damned if you do, damned if
> > you don't" situation.
>
> What about a sysfs option or sysctl?
> I'm not wrapping my mind aroun
Alan Stern wrote:
> On Mon, 6 Jun 2005, Alex Butcher wrote:
>
>
>>>Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
>>>design geniuses at Prolific we're caught in a "damned if you do, damned if
>>>you don't" situation.
>>
>>Is it possible to do something in user space, based
Alan Stern wrote:
> On Sun, 5 Jun 2005, Phil Dibowitz wrote:
>
>
>>>What does bother me is preventing people from using the last sector of a
>>>disk when they already have valid data stored there. Assuming the updated
>>>PL-3507 chips don't get used in a context where the last disk sector coul
On Mon, 6 Jun 2005, Alex Butcher wrote:
> > Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
> > design geniuses at Prolific we're caught in a "damned if you do, damned if
> > you don't" situation.
>
> Is it possible to do something in user space, based on a unique device
>
On Mon, 6 Jun 2005, Alan Stern wrote:
On Sun, 5 Jun 2005, Phil Dibowitz wrote:
What does bother me is preventing people from using the last sector of a
disk when they already have valid data stored there. Assuming the updated
PL-3507 chips don't get used in a context where the last disk secto
On Sun, 5 Jun 2005, Phil Dibowitz wrote:
> > What does bother me is preventing people from using the last sector of a
> > disk when they already have valid data stored there. Assuming the updated
> > PL-3507 chips don't get used in a context where the last disk sector could
> > be written (for
Alan Stern wrote:
> On Tue, 31 May 2005, Phil Dibowitz wrote:
>
>
>>Oh, I CC'd the list but didn't include all the previous emails. The
>>summary (though it can probably be pieced together from the above, I
>>figure I should state it) is that the latest version of the firmware for
>>the PL-3507 f
On Tue, 31 May 2005, Phil Dibowitz wrote:
> Oh, I CC'd the list but didn't include all the previous emails. The
> summary (though it can probably be pieced together from the above, I
> figure I should state it) is that the latest version of the firmware for
> the PL-3507 fixes the CAPACITY bug and
Phil Dibowitz wrote:
> Alex Butcher wrote:
>
>>Unfortunately, some of us can't upgrade to newer firmware since our caddies
>>have been manufactured with flash memory that can only be reprogrammed
>>out-of-circuit. Oh, and I can't use the Firewire port either, since the
>>firmware in my caddies is
Alex Butcher wrote:
>
> Unfortunately, some of us can't upgrade to newer firmware since our caddies
> have been manufactured with flash memory that can only be reprogrammed
> out-of-circuit. Oh, and I can't use the Firewire port either, since the
> firmware in my caddies is utterly broken w.r.t. t
15 matches
Mail list logo
