9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sergey Reva <rs_rlab@mail.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] usb or lp
Date: Mon, 29 Nov 2004 15:21:50 +0200	[thread overview]
Message-ID: <583088821.20041129152150@mail.ru> (raw)
In-Reply-To: <ff23873c2ad14df9c79064796311854c@granite.cias.osakafu-u.ac.jp>

Hello 9fans,

Monday, November 29, 2004, 4:29:26 AM, Kenji wrote:
KO> I don't know what type of printer of Canon S200, however,
KO> do you have correct entry in /sys/lib/lp/devices and neccessary 
KO> initializer for that printer?
Here is my /sys/lib/lp/device, it's equal to my old (working) installation:

canon - - /dev/usb0/1/ep1data - gs!bjc600+nohead generic nospool - - - -

KO> 1) search the /dev/usb tree, and find the strings of '0x020107',
KO> which is the usb printer.   And then, 
KO> echo 'ep 3 bulk w 64 32' > /dev/usb3/$i/ctl
KO> where ep '3" is the endpoint number of USB printer's data endpoint,
KO> and $i stands for the usb device number found.
KO> Then, bind /dev/usb3/$i/ep3data /n/lp, and then print the data
KO> to /n/lp.
Yes, usbprint do the same but this don't work in all version of Plan 9 which I have.
In my case writing endpoint is 1, I see it when run usb/usbd -v -d.
I have only 2 endpoints. When I try bind (in old or new) I get this:

term% bind /dev/usb0/1/ep1data /n/lp
bind ep1data /n/lp: inconsistent mount

Binding ep2data take same result.

Any ideas.

Sergey


P.S.
Yes I know, my English is terrible, try understand me :)
-- 
http://rs-rlab.narod.ru                            mailto:rs_rlab@mail.ru



  parent reply	other threads:[~2004-11-29 13:21 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
2004-11-29 13:21   ` Sergey Reva [this message]
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=583088821.20041129152150@mail.ru \
    --to=rs_rlab@mail.ru \
    --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).