From: Forest Bond <forest@alittletooquiet.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: VT6656 driver source available from VIA
Date: Mon, 7 Jan 2008 13:49:49 -0500 [thread overview]
Message-ID: <20080107184949.GI18550@storm.local.network> (raw)
In-Reply-To: <20071114170634.GC6226@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Hi,
On Wed, Nov 14, 2007 at 12:06:34PM -0500, John W. Linville wrote:
> On Wed, Nov 14, 2007 at 12:00:51PM -0500, Forest Bond wrote:
>> On Sun, Nov 04, 2007 at 09:07:31PM -0500, Forest Bond wrote:
>>> The post is here:
>>>
>>> http://forums.viaarena.com/messageview.aspx?catid=28&threadid=78745
>>>
>>> Any noise that can be contributed is welcome and appreciated. You'll need
>>> to create an account to post, though.
>
>> I also added these. Perhaps having plenty of content/links regarding this
>> issue will help to increase visibility:
>>
>> http://www.alittletooquiet.net/text/a-license-for-the-via-vt6656-linux-driver/
>> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/162671
>
> Excellent...I appreciate your efforts as an agitator! :-)
At this point I am not anticipating positive results WRT this endeavor, and am
unable to pursue further assistance from VIA. Further, I've seen that the
driver in question likely exhibits some interesting quirks that makes it
difficult to use. It is also bit-rotting out of relevance.
Can the driver be used as a reference for a fresh implementation? I've not
written a driver before, but would be open to the possibility.
What are the legal ramifications of a driver author having access to
proprietary source code?
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-07 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 19:37 VT6656 driver source available from VIA Forest Bond
2007-09-19 20:52 ` Forest Bond
2007-09-20 14:04 ` Johannes Berg
2007-09-20 14:10 ` Forest Bond
2007-09-20 14:15 ` Luis R. Rodriguez
2007-11-01 18:59 ` John W. Linville
2007-11-01 19:07 ` Forest Bond
2007-11-01 19:12 ` John W. Linville
2007-11-01 20:21 ` Forest Bond
2007-11-05 2:07 ` Forest Bond
2007-11-14 17:00 ` Forest Bond
2007-11-14 17:06 ` John W. Linville
2008-01-07 18:49 ` Forest Bond [this message]
2008-01-07 20:20 ` Luis R. Rodriguez
2008-01-07 20:31 ` Forest Bond
2008-01-07 20:47 ` Luis R. Rodriguez
2008-01-07 20:54 ` Luis R. Rodriguez
2008-01-07 21:06 ` Forest Bond
2008-01-07 21:38 ` Luis R. Rodriguez
2008-01-07 20:54 ` Dan Williams
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=20080107184949.GI18550@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).