Err... a little correction - I mucked around with the N2 drivers a while
back, and I encountered this problem. SDL gives out the source to
cisco_linux (HDLC protocol), ppp_linux and raw_linux, but these only do
the protocol stuff. Each of them is linked with n2phys.elf and n2drv.elf,
which are object files containing have the routines that actually talk to
the card. They will not give the source to these - I tried last summer,
and this was when I worked for a large company that wasn't even a
competitor and ready to sign NDAs and stuff... (obviously,
reverse-assembling it wasn't something we could "officially" do ;)
If you have the manual that comes with the card, you don't even need
n2cfg.exe.
It's trivial to port their drivers to 2.1.x by the way - remove all
verify_area calls, change all memcpy_fromfs and memcpy_tofs to
copy_from_user and copy_to_user, and it should work...
-Vijay
On Tue, 3 Feb 1998, Gordon Chaffee wrote:
> Alan Cox writes:
> > Not so - they do exactly what the Ollicom guy is talking about but done
> > cleanly. There is no GPL code in their driver nor claim to be. Bits of
> > their driver are binary only so if it breaks or they get bored of supporting
> > it you lose. They do give you source to some bits however.
>
> I was wrong about the GPL--I had looked at the wrong file. Currently,
> the files cisco/cisco_linux.c, ppp/ppp_linux.c, and rawip/raw_linux.c
> are distributed under the GPL, but that is because of their origins.
> It looked like all the code was distributed, but I didn't realize the
> utility program n2xcfg was binary only. Everything else has source,
> but that really don't get around the problem.
>
> - - Gordon