OK, so Which bsd and which driver?

[Camilo Alejandro Arboleda]

If you think it is easier to port linux driver, you can try what we did 
when we needed a driver for M-Systems DiskOnChip hardware: Ask the 
author for permision to redistribute it with the exception.

Most people don't care about the exact license terms if you act in an 
ethical way and keep the software free (open source).

Camilo Alejandro Arboleda.

gregory.menke at gsfc.nasa.gov wrote:

>Alright, now that I've thrown away all code from the Linux 3com
>driver, which of the 5 million bsd variations supports modern 3com
>hardware?  And, is it possible to know which of the incoherent driver
>names they seem to use does the 3com support?
>
>Some Freebsd's apparently scatter support for various 3com cards
>across various drivers- very nice.  Netbsd asserts that it supports
>3com hardware too- but won't tell you the actual files that implement
>it.  Heaven only knows what OpenBSD does.
>
>Joking aside, Joel, please don't take this the wrong way- but this
>kind of thing is EXTREMELY frustrating.  I really wish these licensing
>issues were made more plain.  A recursive grep for GPL in the rtems
>source tree didn't turn up any general warnings about inclusion of GPL
>code in RTEMS- only a couple ancient boilerplate references here and
>there.  Instead of wasting 2 days, I could have easily wasted a couple
>weeks getting the Linux 3com driver ported, working and efficient- and
>then have to throw it out due to the AFAICT essentially undocumented
>no-GPL requirement.  Sure, I could use it in-house, which I probably
>would, but thats not helping the RTEMS community any.
>
>So, I'm grumpy today, but I'll get over it.
>
>Gregm
>
>  
>

-- 
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop at Netscape! 
http://shopnow.netscape.com/