From: Forest Bond <forest@alittletooquiet.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Dan Williams <dcbw@redhat.com>
Subject: Re: VT6656 driver source now GPL
Date: Mon, 13 Apr 2009 20:08:35 -0400 [thread overview]
Message-ID: <20090414000835.GA31504@storm.local.network> (raw)
In-Reply-To: <20090320131014.GG25237@storm.local.network>
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
Hi,
On Fri, Mar 20, 2009 at 09:10:15AM -0400, Forest Bond wrote:
> On Thu, Mar 19, 2009 at 09:45:19AM -0700, Luis R. Rodriguez wrote:
> > On Thu, Mar 19, 2009 at 9:42 AM, Forest Bond <forest@alittletooquiet.net> wrote:
> > > Hi,
> > >
> > > VIA has released a new version of the VT6656 driver source, and it now has a
> > > proper license!
> > >
> > > http://www.viaarena.com/Driver/VT6656_Linux_src_v1.19_12_x86.zip
> > >
> > > As you may recall, the previous version lacked a license altogether, making it
> > > unfit for distribution.
> > >
> > > I'd really like to see this driver integrated into the kernel. Does anyone care
> > > to comment regarding feasibility?
> >
> > Indeed good news, what is the latest kernel it compiles for? If it
> > compiles on Linus' tree it can be stashed into staging while it gets
> > properly ported.
>
> Just so I know who to pester*, will you be driving this? Do you have interest
> in also pulling in the VT6655 driver?
>
> * I won't pester that much. ;)
I'm getting the sense that there is not a lot of developer interest in these
drivers. Is there anything I can do to aid in getting these drivers into the
kernel?
I would be willing to send patches, however, my experience with kernel hacking
is limited and I don't have a lot of time available to contribute. With a
little direction, though, I might be able to get somewhere.
Any input would be appreciated.
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-04-14 0:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 16:42 VT6656 driver source now GPL Forest Bond
2009-03-19 16:45 ` Luis R. Rodriguez
2009-03-19 16:48 ` Forest Bond
2009-03-20 13:10 ` Forest Bond
2009-04-14 0:08 ` Forest Bond [this message]
2009-04-14 0:12 ` Luis R. Rodriguez
2009-04-14 0:22 ` Forest Bond
2009-04-14 0:40 ` Greg KH
[not found] ` <49E3D7AA.1050207@lwfinger.net>
2009-04-14 0:55 ` Forest Bond
2009-04-14 1:04 ` Larry Finger
2009-04-14 2:11 ` Greg KH
2009-04-14 2:20 ` Forest Bond
2009-04-14 2:33 ` Greg KH
2009-04-14 2:46 ` Forest Bond
2009-04-14 2:10 ` Greg KH
2009-06-11 13:29 ` Harald Welte
2009-06-11 13:50 ` Forest Bond
2009-06-11 16:30 ` Harald Welte
2009-03-19 16:46 ` Forest Bond
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=20090414000835.GA31504@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).