linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@terra.com.br>
To: gracecott@sancharnet.in
Cc: linux-c-programming@vger.kernel.org
Subject: Re: various doubts ......
Date: Mon, 9 Aug 2004 20:50:56 -0300	[thread overview]
Message-ID: <20040809205056.0ac6d2cb.lcapitulino@terra.com.br> (raw)
In-Reply-To: <4117B259.1090500@sancharnet.in>


 Hi Joy,

Em Mon, 09 Aug 2004 22:50:25 +0530
joy <gracecott@sancharnet.in> screveu:

| Hello,
| I  have a few , though unconnected doubts.
| 
| 1) can a named pipe be locked using normal lockf()  or do I have to 
| perform some voodoo?

 I think is possible, but take a look at fcntl(2).

| 2) I need to transfer data (protocol not an issue, just raw data) from a 
| usb peripheral(not HDD)
|     to the host comp. can I do this without writing a usb driver myself, 
| i.e , using some generic or user-space driver (like ppdev)
|     the peripheral is a texas instruments tusb246b hub.

 If I've understand what you mean: maybe. The question is: there is any driver
for that hub in the kernel ?

 As far as I read, in ppdev you do have two things. First, there is the
/dev/lp0, which is the _printer_ driver; second, there is the /dev/parport0,
the _parallel port_ driver.

 You can write a user-space driver for you printer, because the kernel
already give you a way (driver) to acesses the parallel port, through
/dev/parport0.

 There is this kind of thing for your USB device ?

 hope this helps,

PS: Don't know nothing about printers, so I may be wrong.

-- 
Luiz Fernando

  reply	other threads:[~2004-08-09 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 17:20 various doubts joy
2004-08-09 23:50 ` Luiz Fernando N. Capitulino [this message]
2004-08-11  2:51 ` joy

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=20040809205056.0ac6d2cb.lcapitulino@terra.com.br \
    --to=lcapitulino@terra.com.br \
    --cc=gracecott@sancharnet.in \
    --cc=linux-c-programming@vger.kernel.org \
    /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).