public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Schaefer <frank.schafer@setuza.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: Serial port- Linux kernel
Date: 03 May 2002 08:58:56 +0200	[thread overview]
Message-ID: <1020409136.272.0.camel@ADMIN> (raw)
In-Reply-To: <GVHNWI$3922BF840A57031E8DFA5B1C29C46DC1@inwind.it>

On Thu, 2002-05-02 at 16:50, antonelloderosa@inwind.it wrote:
> I must control the serial port at kernel level, because I have to make several measurements of one-way delay between a source and a destination host, so while I set the DTR on the source host when I send the UDP packet, the destination host must be able to set by itself the RTS when it receives the packet.
> 
> I'm quite a beginner in Linux-kernel, so may you help me more?
> 
> Thanks again
> 
> Antonello 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
Hi Antonello,

if you're new to the kernel ( like me :o), you could take Rubini &
Corbets ``Linux Device Drivers'' book, and write a special driver for
your problem. That could be a nice task for learning the kernel.
I did something similar, programming a little parport-LED-lightshow.
Your real and my artificial problem enlightenes one in driver, module,
kernel and user-space / kernel-space relations, and is ( thus ) a fine
task to start with.

Regards
Frank

PS: Many thanks to Alessandro and Jonathan for this fine collection of
paper.




      reply	other threads:[~2002-05-03  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 14:50 Serial port- Linux kernel antonelloderosa
2002-05-03  6:58 ` Frank Schaefer [this message]

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=1020409136.272.0.camel@ADMIN \
    --to=frank.schafer@setuza.cz \
    --cc=linux-kernel@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