9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jim mckie jmk@plan9.bell-labs.com
Subject: [9fans] Re: etherelnk3.c
Date: Tue, 23 Dec 1997 23:30:28 -0500	[thread overview]
Message-ID: <19971224043028.waLK208fOxj7VfkxcSXj59X5HH4LEccRWLus8OhmpdU@z> (raw)

actually, it's easier. you can turn a Block-based driver into
a filesystem driver with a handful of #defines, two trivial functions
and a couple of #ifdefs (i know, we don't actually approve of that).
#ifdefs are only necessary because Blocks use read and write pointers
and Msgbufs use a base and count.

--jim

------ forwarded message follows ------

>From cse.psu.edu!owner-9fans Mon Dec 15 13:30:30 EST 1997
Received: from cse.psu.edu ([130.203.3.50]) by plan9; Mon Dec 15 13:30:30 EST 1997
Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.7/8.7.3) with SMTP id NAA22716; Mon, 15 Dec 1997 13:29:56 -0500 (EST)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Mon, 15 Dec 1997 13:29:24 -0500
Received: (from majordom@localhost) by cse.psu.edu (8.8.7/8.7.3) id NAA22677 for 9fans-outgoing; Mon, 15 Dec 1997 13:29:19 -0500 (EST)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from ns.dbSystems.com (root@ns.dbsystems.com [204.178.76.1]) by cse.psu.edu (8.8.7/8.7.3) with SMTP id NAA22673 for <9fans@cse.psu.edu>; Mon, 15 Dec 1997 13:29:13 -0500 (EST)
Received: (from gdb@localhost) by ns.dbSystems.com (8.6.11/8.6.9) id MAA16085 for 9fans@cse.psu.edu; Mon, 15 Dec 1997 12:14:33 -0600
Date: Mon, 15 Dec 1997 12:14:33 -0600
From: "G. David Butler" <dbSystems.com!gdb>
Message-Id: <199712151814.MAA16085@ns.dbSystems.com>
To: cse.psu.edu!9fans
Subject: Re: [9fans] Re: etherelnk3.c
Sender: cse.psu.edu!owner-9fans
Reply-To: cse.psu.edu!9fans
Precedence: bulk

>From: eld@jewel.ucsd.edu (Eric Dorman)
>> From: "G. David Butler" <gdb@dbSystems.com>
>> To: 9fans@cse.psu.edu
>> Subject: [9fans] Re: etherelnk3.c
>> 
>  Another thing to consider is how these changes would affect
>the integration of ether drivers between the fs and terminal code.
>Integrating these two trees first allieviates a whole mess of 
>existing problems and ensures that this type of effort won't 
>have to be done again (perhaps differently, even) for fs.

In fact the problem becomes worse since Blocks don't exist
in the fs.  There we would have to use Msgbufs.




             reply	other threads:[~1997-12-24  4:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-24  4:30 jim [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-01-02 21:54 jim
1997-12-31 17:14 Eric
1997-12-31 15:10 jim
1997-12-31  8:54 Nigel
1997-12-31  6:49 G.David
1997-12-31  5:16 jim
1997-12-31  3:51 G.David
1997-12-31  2:41 jim
1997-12-30 19:05 Eric
1997-12-30  1:20 G.David
1997-12-29 20:25 Eric
1997-12-15 18:14 G.David
1997-12-15 17:43 Eric
1997-12-14 16:37 G.David
1997-12-13 18:04 G.David

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=19971224043028.waLK208fOxj7VfkxcSXj59X5HH4LEccRWLus8OhmpdU@z \
    --to=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).