Oliver Rauch wrote:
> I suggest to keep it as USB function. Other bus systems may need
> different timeout values so it is better to use different functions for
> different connection types.
Right. Additionally, it might be reasonable to use different timeout
values for different USB devices, li
Hi,
Henning Meier-Geinitz wrote:
> On Wed, Dec 01, 2004 at 02:54:59PM +0100, René Rebe wrote:
>
>>the default timeout passed to libusb of 30 seconds is quite a bit long.
>>So recovering from errors is already quite annoying for some use cases.
>>Now I have a situation where I expect an error t
Am Mit, 2004-12-01 um 20.39 schrieb m. allan noah:
> On Wed, 1 Dec 2004, Henning Meier-Geinitz wrote:
>=20
> > Hi,
> >
> > On Wed, Dec 01, 2004 at 02:54:59PM +0100, Ren=C3=A9 Rebe wrote:
> >> the default timeout passed to libusb of 30 seconds is quite a bit lo=
ng.
> >> So recovering from errors is
Hi,
On Wed, Dec 01, 2004 at 02:39:54PM -0500, m. allan noah wrote:
> is there any value to makeing this function call have a more generic name,
> like sanei_set_timeout() which could perhaps be a noop in the scsi case
> for now? is variable timeout ever going to apply to scsi?
It could be of so
Hi,
On Wed, Dec 01, 2004 at 02:54:59PM +0100, René Rebe wrote:
> the default timeout passed to libusb of 30 seconds is quite a bit long.
> So recovering from errors is already quite annoying for some use cases.
> Now I have a situation where I expect an error to happen for some models
> and adj
Hi all,
the default timeout passed to libusb of 30 seconds is quite a bit long.
So recovering from errors is already quite annoying for some use cases.
Now I have a situation where I expect an error to happen for some models
and adjust the code-path of future commands due to this. An initial
t
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--1386613362-1831700870-1101929994=:25855
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
On Wed, 1 De
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--1386613362-797012048-1101914199=:25855
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
i am BIG in f
