On Wed, Oct 11, 2000 at 12:15:08AM +0200, Matthias Andree wrote:
> On Tue, 10 Oct 2000, Kurt Garloff wrote:
>
> > Actually, 2.0e3 did include one rather important fix which solved the
>
> Uh. Fix? This sounds like working around very broken devices to me, or
> are devices allowed to wreak havoc
On Wed, Oct 11, 2000 at 12:15:08AM +0200, Matthias Andree wrote:
On Tue, 10 Oct 2000, Kurt Garloff wrote:
Actually, 2.0e3 did include one rather important fix which solved the
Uh. Fix? This sounds like working around very broken devices to me, or
are devices allowed to wreak havoc if
On Tue, 10 Oct 2000, Kurt Garloff wrote:
> Actually, 2.0e3 did include one rather important fix which solved the
Uh. Fix? This sounds like working around very broken devices to me, or
are devices allowed to wreak havoc if sync negotiation is tried in spite
of not being advertised in inquiry
Kurt Garloff wrote:
> Actually, 2.0e3 did include one rather important fix which solved the
> trouble: Some devices get upset, when the driver tries to negotiate sync
> (or wide) connections, but the device actually does not support it.
> So, the driver now waits for the first INQUIRY result and
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote:
> On Mon, 02 Oct 2000, Alan Cox announced:
> > 2.2.18pre15
>
> I'd like to know if there are any issues with the current dc390-2.0e or
> 2.0e3 drivers that prevent its inclusion/that prevent Kurt from
> submitting it for inclusion.
On Mon, 02 Oct 2000, Alan Cox announced:
> 2.2.18pre15
I'd like to know if there are any issues with the current dc390-2.0e or
2.0e3 drivers that prevent its inclusion/that prevent Kurt from
submitting it for inclusion. As per the web page, 2.0e was supposed to
be sent to Linux for 2.4, so it
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote:
On Mon, 02 Oct 2000, Alan Cox announced:
2.2.18pre15
I'd like to know if there are any issues with the current dc390-2.0e or
2.0e3 drivers that prevent its inclusion/that prevent Kurt from
submitting it for inclusion. As per
Kurt Garloff wrote:
Actually, 2.0e3 did include one rather important fix which solved the
trouble: Some devices get upset, when the driver tries to negotiate sync
(or wide) connections, but the device actually does not support it.
So, the driver now waits for the first INQUIRY result and
On Tue, 10 Oct 2000, Kurt Garloff wrote:
Actually, 2.0e3 did include one rather important fix which solved the
Uh. Fix? This sounds like working around very broken devices to me, or
are devices allowed to wreak havoc if sync negotiation is tried in spite
of not being advertised in inquiry
9 matches
Mail list logo
