9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb/print problem since last update
Date: Tue, 13 Oct 2009 19:34:30 +0200	[thread overview]
Message-ID: <8ccc8ba40910131034q18c7990dn38b2dbff5704526c@mail.gmail.com> (raw)
In-Reply-To: <fe41879c0910131031l614ebdddw9734721f7fe58848@mail.gmail.com>

Have you updated your kernel?

We increased the size of the max ctl request in both the usb
library and also in usb[ueo]hci.c

You seem to have a new library but an old kernel. The library
is asking for more max size than the kernel can afford now.

I'm sorry, I should have teached the kernel how to cope with
old sizes. In the mean time, it's easier if you recompile your kernel.



On Tue, Oct 13, 2009 at 7:31 PM, Akshat Kumar
<akumar@mail.nanosouffle.net> wrote:
> Last time I played with printing, was quite a while
> before the last update to usb/print (apparently Sep.
> 25). And stuff worked back then.
>
> Here's the output now:
>
> cpu% usb/print
> usb/print: startdevs: opening #0 /dev/usb/ep7.0
> usb/print: /dev/usb/ep7.0: config: d2h data too large to fit in uhci
> usb/print: no device found
>
> and what does the ctl see?
>
> cpu% cat /dev/usb/ep7.0/ctl
> enabled control rw speed full maxpkt 8 pollival 0 samplesz 0 hz 0 hub
> 4 port 1 idle
> 255 csp 0x00ccff csp 0x020107 csp 0x00d4ff vid 0x03f0 did 0x4f11 HP
> 'Officejet 5600 series'
>
> Using the backup, usb/_print from July 28, stuff still
> works (there's a usable /dev/lp^$n device for printing
> and no error).
>
>
> Best,
> ak
>
>



  reply	other threads:[~2009-10-13 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 17:31 Akshat Kumar
2009-10-13 17:34 ` Francisco J Ballesteros [this message]
2009-10-13 17:51   ` Akshat Kumar
2009-10-13 19:05     ` Francisco J Ballesteros
2009-10-15  8:15       ` Akshat Kumar
2009-10-15  8:34         ` Francisco J Ballesteros
2009-10-17  3:31           ` Akshat Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ccc8ba40910131034q18c7990dn38b2dbff5704526c@mail.gmail.com \
    --to=nemo@lsub.org \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).