9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] usb or lp
Date: Sun, 28 Nov 2004 22:00:45 -0500	[thread overview]
Message-ID: <ee9e417a041128190056e13a4c@mail.gmail.com> (raw)
In-Reply-To: <ff23873c2ad14df9c79064796311854c@granite.cias.osakafu-u.ac.jp>

if the seq is causing problems that using for(c in /dev/usb?[0-9]*)
solves, then i would just use the good for loop instead and we 
can put it back.  or at least change it to 

for(c in /dev/usb^`{seq 0 16}) 

instead of

for(c in /dev/usb/^`{seq 16})

if not having usb0 is really the problem.  it's hard to tell
what you're saying the problem is.


On Mon, 29 Nov 2004 11:29:26 +0900, Kenji Okamoto
<okamoto@granite.cias.osakafu-u.ac.jp> wrote:
> I feel somthing is wrong in your usb printer setting...
> Yes, usb device driver was changed, however, for printers
> I think there is no difference.
> 
> I don't know what type of printer of Canon S200, however,
> do you have correct entry in /sys/lib/lp/devices and neccessary
> initializer for that printer?
> 
> >No when I try print something I get only this:
> >cat: write error copying /tmp/xyz: ken has left the building
> 
> I think this means you have not binded safely /n/lp to the correct
> usb printer device.
> 
> 1) search the /dev/usb tree, and find the strings of '0x020107',
> which is the usb printer.   And then,
> echo 'ep 3 bulk w 64 32' > /dev/usb3/$i/ctl
> where ep '3" is the endpoint number of USB printer's data endpoint,
> and $i stands for the usb device number found.
> Then, bind /dev/usb3/$i/ep3data /n/lp, and then print the data
> to /n/lp.
> 
> Kenji
> 
> 
> 
> ---------- Forwarded message ----------
> From: Sergey Reva <rs_rlab@mail.ru>
> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
> Date: Sun, 28 Nov 2004 10:54:45 +0200
> Subject: [9fans] usb or lp
> Hello 9fans,
> 
> With "latest sources" (about month ago) I can't print on my Canon S200 printer with USB
> interface. What happened? How fix this?
> 
> /sys/src/cmd/usb/misc/usbprint have error:
> 
> for (c in '{seq 16})
> where $c used in usb$c, it only generate number from 1 to 16, how about usb0?
> 
> In my old sources I have usbprint like this:
> for (c in /dev/usb?[0-9]*)
> But I don't used this and printer works well.
> 
> No when I try print something I get only this:
> cat: write error copying /tmp/xyz: ken has left the building
> 
> And finally in usbprint all version for printing used ep2data but in my
> case work only ep1data.
> 
> With best regards Sergey Reva
> --
> http://rs-rlab.narod.ru                          mailto:rs_rlab@mail.ru
> 
>


  reply	other threads:[~2004-11-29  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28  8:54 Sergey Reva
2004-11-29  2:29 ` Kenji Okamoto
2004-11-29  3:00   ` Russ Cox [this message]
2004-11-29 13:21   ` Sergey Reva
2004-11-30  0:56     ` Kenji Okamoto
2004-11-30 15:07       ` Sape Mullender
2004-11-30 16:28         ` Sape Mullender
2004-11-30 19:08           ` Sergey Reva
2004-11-30 20:21             ` Sape Mullender
2004-12-01 17:20             ` Sape Mullender

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=ee9e417a041128190056e13a4c@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).