[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some questions about libports and notification of ports

From: Thomas Bushnell BSG
Subject: Re: Some questions about libports and notification of ports
Date: Tue, 26 Aug 2008 19:01:35 -0700

On Wed, 2008-08-27 at 03:38 +0200, Da Zheng wrote:
> Thomas Bushnell BSG wrote:
> > On Wed, 2008-08-27 at 01:56 +0200, Da Zheng wrote:
> >   
> >>> Yes, but the point here is that *you* are opening that file and
> >>> expecting something to happen.  I thought you were writing the program
> >>> which would *serve* that file.
> >>>   
> >>>       
> >> I know it's a bit confusing. Then what should I do?
> >>     
> >
> > If you want to serve that file, you'll be writing a trivfs translator
> > for it. 
> >   
> I'm sorry, I don't understand you.
> The translator associated to the device file is actually written with 
> libtrivfs.

Good grief, I can't keep track of what you are talking about.

I'm just about to give up, but I'm going to try.  You omit a lot of
information.  I'm going to ask you to stop doing that.  If you want
communication to succeed, you MUST try and give all the information, and
not just guess that I can guess what's in your head.  I can't.

Ok, so I saw code that opened these /dev/eth0 nodes.  I saw no code that
implements them.  I said, "hey, what implements them?" and you said,
"well, this is what they will do."  Ok, I'll try again.  What implements
these /dev/eth0 nodes?  Is that something you've written?  Something
that already exists? 

> Do you mean I should implement the IO operation? so other programs can 
> read and write the device file to communicate with the kernel device?
> but what we want is a translator that helps other programs get the port 
> to the device. That's it.

Um, that is *obviously* not what you are wanting.  (And please, don't
say "what we want"; just say "what I'm trying to implement".  I can
hardly keep track of what you are working on because it seems to change
from message to message.)

If you only wanted "the port to the device", it would be a simple
translator that held the device master port and handed out the Mach
device port.

Obviously you do NOT want simply to "help other programs get the port to
the device."  Please help me understand.  What *exactly* is your


reply via email to

[Prev in Thread] Current Thread [Next in Thread]