From: Dan Shearer <dan@shearer.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Changes to port_user
Date: Fri, 23 Jan 2004 02:13:02 +1030 [thread overview]
Message-ID: <20040122154302.GR4203@erizo.shearer.org> (raw)
In-Reply-To: <20040122144020.GQ4203@erizo.shearer.org>
On Fri, Jan 23, 2004 at 01:10:20AM +1030, Dan Shearer wrote:
> Now, I just want raw data to go from the kernel to the port and back
> again. So should I:
>
> a) just shortcircuit this by hooking the inbound and outbound
> descriptors up, or
I'm starting to get it, chan_kern is the place to start to understand
what happens when a read or write irq goes off. I don't think there is a
short-circuit mechanism for hooking up the internal fd for a tty
directly to an fd within a channel driver without breaking this design.
So what if I modified port_task_proc to copy the incoming data in the
appropriate direction? I'll give that a try next.
Jeff, please, what does "winch" stand for?
And also, if I submit some patches that just contain brief source
comments about how things work will you accept them? I notice you don't
use them much.
--
Dan Shearer
dan@shearer.org
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-01-22 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 14:40 [uml-devel] Changes to port_user Dan Shearer
2004-01-22 15:43 ` Dan Shearer [this message]
2004-01-22 18:13 ` Jeff Dike
2004-01-22 16:20 ` Jeff Dike
2004-02-15 15:24 ` roland
2004-02-15 16:20 ` Ulf Bartelt
2004-02-15 16:39 ` roland
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=20040122154302.GR4203@erizo.shearer.org \
--to=dan@shearer.org \
--cc=user-mode-linux-devel@lists.sourceforge.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