See below ...
Regards,
Joe.
> -----Original Message-----
> From: Bernie [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, 25 August 2000 6:27
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: EPPPD 0.7 (rather urgent, so please read)
>
----- snip -----
> Now to get back to the RX trigger level that Joe asked about, this is from
> epppd (in n8250.h for those who have the source)
>
> #define FIFO_SIZE_1 0x00 /* RX fifo trigger levels */
> #define FIFO_SIZE_4 0x40
> #define FIFO_SIZE_8 0x80
> #define FIFO_SIZE_14 0xC0
>
> So this was easy (when I found it (perhaps I should have added "-i" to
> grep
> a little earlier now it took me 5-10 minutes to figure that out) to add
> support for in pppdrc.cfg but we still need a way to configure it in
> Arachne (and make Arachne write the information to pppdrc.cfg). Now the
> question is which values should be allowed (this should be checked in
> Arachne IMHO to not increase the size of epppd). Should they be 1, 4, 8
> and
> 14 or the hexadecimal numbers (and are others actually allowed? I now
> absolutely nothing about what the results may be of my changes in this
> area).
> In any event the information that pppdrc.cfg should contain is in decimal
> form (or actually the number would be even better but I doubt much is
> gained by that).
>
[da Silva, Joe]
The only FIFO trigger levels that exist are those given above. The
hex values shown above are ORed with $01 first, to produce $01,
$41, $81 or $C1 - assuming a FIFO exists and is to be enabled.
Of course, this ORing must already exist in the 'epppd' code, so
you shouldn't need further changes to do that ...
As for "we still need a way to configure it in Arachne ...", that's
the reason both files 'pppd.cfg' *and* 'pppdrc.cfg' should be
supported ... (IMHO).
> I'll see if I can put together a beta this weekend. Without the trigger
> choice of course and not with the best reduction I can make (for that I
> must know the exact order for how Arachne writes pppdrc.cfg - thereby
> making it work only with a specific version (1.70?)
>
[da Silva, Joe]
What do you mean, "without the trigger choice of course" ?! ;-)
I know you are trying to squeeze every last byte out of this
thing, but is it wise to make this so "rigid" that you even make
'pppdrc.cfg' order-specific ???
I mentioned before the possibility to support DPMS, thereby
making most of the packet driver live in XMS - would this be
a better approach than making 'epppd' too restrictive? To quote
from 'http://developer.novell.com/support/bullets/jun93.htm',
"Developers may distribute the server component royalty-free
with their DPMS client programs" - which seems to say that
the DPMS.EXE driver can be freely distributed (for those
that don't already have it) ...
> Michael perhaps we should take this either off this list now or onto the
> "Arachne Developer Network" - what do you say Glenn and Clarence,
> interested or not? Or should I just finish epppd 0.7 and send the changes
> required in Arachne to you?
>
> BTW: I actually noticed right now that I don't have the rights to make any
> changes to the code made by Toni Lopez and redistribute it. Ah heck, since
> he seems to have drop all interest in it (AFAIK) I guess he doesn't care
> if
> I change things...
>
[da Silva, Joe]
AFAIK, this stuff is "open source", so you should be able to make
changes, as long as you identify the changes and make the new
source readily available (?).
> BTW2: I also realized that I'll need to put some sort of documentation
> together :(
> I guess it will take a while before I'll release the stand-alone version
> then with complete docs...
