-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 20 May 2001, David Brownell wrote:
> > > How about the "printer-0519.patch" ... did that resolve, by itself,
> > > the problems in the printer driver? Specifically: the looping you
> > > observed with the previous printer patch, caused by th
> > How about the "printer-0519.patch" ... did that resolve, by itself,
> > the problems in the printer driver? Specifically: the looping you
> > observed with the previous printer patch, caused by the fact that
> > usblp_write didn't drop the semaphore so usblp_disconnect could
> > never do its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 20 May 2001, David Brownell wrote:
> > > Bogus kernel config, those drivers didn't get rebuilt -- sorry. This
> > > one should be OK ("dev" --> "usb_dev").
> >
> > Hi Dave,
> >
> > Thanks for the update! Now things compile, but the oopses c
> > Bogus kernel config, those drivers didn't get rebuilt -- sorry. This
> > one should be OK ("dev" --> "usb_dev").
>
> Hi Dave,
>
> Thanks for the update! Now things compile, but the oopses come back
> to back :-(.
OK, so that "usbcore-0519.patch" won't behave. There are even more
nonsen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 19 May 2001, David Brownell wrote:
> > > Can you try the attached "usbcore-0519.patch" ...
> >
> > I couldn't compile with your usbcore patch.
>
> Bogus kernel config, those drivers didn't get rebuilt -- sorry. This
> one should be OK ("dev"
> > Can you try the attached "usbcore-0519.patch" ...
>
> I couldn't compile with your usbcore patch.
Bogus kernel config, those drivers didn't get rebuilt -- sorry. This
one should be OK ("dev" --> "usb_dev").
- Dave
usbcore-0519.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 19 May 2001, David Brownell wrote:
> Can you try the attached "usbcore-0519.patch" (with the previous
> printer patch, not printer-0519) to see if that makes that oops go away?
Hi Dave,
I couldn't compile with your usbcore patch. Did you f
Hi Anders,
> I tried to follow your instructions...
Wasn't quite what I had in mind, but gave me what has to be the
answers anyway. One printer bug, one more usbcore-ish (looks
to be pretty long-standing, too).
> Then I did my usual "cat /boot/bzImage > /dev/usb/lp0" after turning
> the print
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dave,
I tried to follow your instructions. I modified usblp_check_status()
as follows (after applying your patch printer-0518.patch):
static int usblp_check_status(struct usblp *usblp, int err)
{
unsigned char status, newerr = 0;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I forgot to attach David's patch; here it is.
Anders
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.5 (SunOS)
Comment: For info see http://www.gnupg.org
iD8DBQE7BLZMWyfD6jrb5n4RAln4AKCV0uocmfser9vsWlE8NpdhmObr5wCg2fk9
67RPClSJWEJquk5NG012rjg=
=7i
her gremlins
at play here.
- Dave
- Original Message -
From: "Thomas Dodd" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 7:03 AM
Subject: Re: [linux-usb-devel] Re: Bug report (2.4.1)
> Miles Lane wrote:
> >
> > David Brownell
Miles Lane wrote:
>
> David Brownell wrote:
>
> > If this is the same erratum I remember from before,
> > it shouldn't show up in recent hardware. Only chips
> > made before last May or so, not more recent ones;
> > recent Socket-A systems tend to have Via (or ALi,
> > DDR now available :-) chi
David Brownell wrote:
> If this is the same erratum I remember from before,
> it shouldn't show up in recent hardware. Only chips
> made before last May or so, not more recent ones;
> recent Socket-A systems tend to have Via (or ALi,
> DDR now available :-) chipsets, especially for the
> southga
13 matches
Mail list logo
