Hi, Martin. I no longer have any "ownership" of usblp.c or the
hpoj.sourceforge.net project (HP management decisions beyond my control).
Good catch. Along the same lines, libusb/usb[dev]fs (at least in 2.4)
has a similar problem when trying to do device ID requests that way
rather than through u
Hi, Henning. I recently discovered that the Linux kernel USB scanner
driver (in 2.4.22 and 2.6.0-test at least) binds to a few HP multi-function
peripherals:
{ USB_DEVICE(0x03f0, 0x1411) }, /* PSC 750 */
{ USB_DEVICE(0x03f0, 0x2f11) }, /* PSC 1210 */
This serves no useful purpose
Johannes Erdfelt wrote:
> On Tue, May 07, 2002, Peter Denison <[EMAIL PROTECTED]> wrote:
> > Turning my HP PSC750 printer/scanner off and on again during a session,
> > results in the following trace - pay particular attention to the 5th line.
> > This is true for at least 2.5.14 and 2.5.11, and
Oliver Neukum wrote:
> you fail to free minors if something goes wrong in probe.
...
> usblp->minor++;
> if (usblp->minor >= USBLP_MINORS) {
> err("no more free usblp devices");
> - goto abort;
>
David Brownell wrote in response to Allen Barnett:
> > I was able to scan in SMP mode with kernel 2.5.10, if that's helpful
> > (printer.c version 0.8 (2.4.18) vs. version 0.12 (2.5.10)).
>
> Highly suggestive, if you ask me ... :)
>
> I notice that 2.4.19-pre7 claims to be version 0.11, you mi
Vojtech Pavlik wrote:
> On Thu, May 02, 2002 at 01:08:47AM +0200, Oliver Neukum wrote:
>
> > Hi,
> >
> > looking through printer.c in preparation for shifting devfs
> > support to usbcore I noticed that printer advertises a device
> > through devfs before it can be opened.
> > As devfs, or more
Hi,
Since this question has come up a lot recently, I thought I should explain
exactly what's going on and how to fix it in the short and long terms.
Till, I apologize for not addressing this better until now, which is
probably too late to do anything for Mandrake 8.2.
The problem: if you connec
Greg KH wrote:
> > [EMAIL PROTECTED], 2002-03-17 10:48:38-08:00, [EMAIL PROTECTED]
> > USB printer patch
> >
> > added NEC printer to quirks list
> >
> > drivers/usb/printer.c |1 +
> > 1 files changed, 1 insertion(+)
...
> + { 0x0409, 0xefbe, USBLP_QUIRK_BIDIR }, /* NEC Picty900
Oliver Neukum wrote (in response to me):
>
> > I've seen similar issues firsthand on an SMP box. I think the reported EIP
> > address tends to lie in non-USB parts of the kernel, such as various
> > network drivers, but I don't know if that's always the case. I just know
>
> Are they repeatabl
Hi. There seem to be kernel-panic issues in the USB subsystem when running
in SMP mode, specifically with printer-class devices, although I don't know
if printer.c is what's at fault. I'm forwarding the message from the
person who reported this to me; please reply-to-all with any information.
S
Oliver Neukum wrote:
> > > You are right. Unfortunately they _have_ accepted it.
> > > Can we now be confident that no other printers will implement it
> > > and put a workaround into printer.c ?
> >
> > While I can't comment on non-HP printers or future HP products, I can say
> > that it's not sa
Lars Doelle wrote:
> Hmm, i have another suggestion:
>
> I had a look at the descriptors, and found three interfaces, but each in a
> different alternate setting and same endpoints. This is really a hack. HP
> should have provided two interfaces with a printer and a scanner class with
> differ
e accepting these
> > protocols, as it would never work in the moment.
>
> David Paschal swears that it would break some other hardware,
> check this thread:
> http://marc.theaimsgroup.com/?t=9966299144&r=1&w=2
> Also this:
> https://bugzilla.redhat.com/bugzilla/sh
AIL PROTECTED]>
* Copyright (c) 1999 Pavel Machek <[EMAIL PROTECTED]>
* Copyright (c) 2000 Randy Dunlap <[EMAIL PROTECTED]>
* Copyright (c) 2000 Vojtech Pavlik <[EMAIL PROTECTED]>
+ # Copyright (c) 2001 Pete Zaitcev <[EMAIL PROTECTED]>
+ # Copyright (c)
c) 2000 Vojtech Pavlik <[EMAIL PROTECTED]>
+ # Copyright (c) 2001 Pete Zaitcev <[EMAIL PROTECTED]>
+ # Copyright (c) 2001 David Paschal<[EMAIL PROTECTED]>
*
* USB Printer Device Class driver for USB printers and printer cables
*
@@ -17,9 +19,11 @@
* v0.4 -
printer.c.diff -- a diff between printer-2.4.13.c and printer.c
- printer.c.udiff -- a unified diff between printer-2.4.13.c and printer.c
-- David Paschal ([EMAIL PROTECTED], [EMAIL PROTECTED])
And here's the patch in &q
François Patte wrote:
> I have just read the thread about this printer, is the change of code in
> printer.c is now available? I have to install linux on a station with
> this printer.
Hi, François. I have a hacked version that has this change in it.
See "http://hpoj.sourceforge.net/download/ex
file
- printer.c -- the hacked version of printer.c
- Makefile -- the makefile I use so I don't have to rebuild the whole kernel
- printer-2.4.12.c -- for comparison, the printer.c from kernel 2.4.12
- printer.c.diff -- a diff between printer-2.
Joel Becker wrote:
> Pete Zaitcev poked me with your URL because I have played with
> the USB device ID issues in the past
...
> I ran into this problem for a simple printing frontend for the New
> Internet Computer. My solution was an ioctl like LPIOC_GET_BUS_ADDRESS,
> but only for the de
Hi, I'm back. Sorry about taking so long to reply, due to several weeks
of vacation, LinuxWorld, and catching up with things. :-)
I finally got around to fleshing out my "ioctl wishlist" for printer.c.
It's posted at "http://hpoj.sourceforge.net/doc/ioctl_requests.html";.
Comments are welcome,
Carlos Puchol wrote:
> hi, i am trying to debug the situation of an hp officejet g55
> connected to one of the onboard usb ports in my spakin' new
> asus a7v133. the printer is recognized but there is no way
> to print or scan from it
...
> so, maybe the problem is in the kernel. i am running a fr
David Brownell wrote:
> I'd expect them to be connected to nothing at all ...
So in other words you're saying that a program executed from a hotplug script
receives no open file descriptors (i.e. for stdin/stdout/stderr) the way it
would if it were executed from a normal shell prompt or startup sc
ck of standard input.
Thanks,
David Paschal
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
David M. Curry wrote:
> Does anybody have any information regarding the LaserJet 1200? the usblp
> (printer module) sees it and sets up /dev/usb/lp0, but writes to it
> dissapear into the bit-bucket. After playing a while, I'm pretty sure that
> the data is being sent to the printer. Does this
Adam J. Richter wrote:
> Finally, on a note that actually has something to do with USB,
> I just want to make clear that you can currently read the IEEE-1284
> parallel port device ID information with a stock 2.4.3 kernel, under
> any of the following scenarios, which cover just about everyt
25 matches
Mail list logo