From: Forest Bond <forest@alittletooquiet.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Dan Williams <dcbw@redhat.com>,
Greg KH <greg@kroah.com>
Subject: Re: VT6656 driver source now GPL
Date: Mon, 13 Apr 2009 20:55:23 -0400 [thread overview]
Message-ID: <20090414005523.GC31504@storm.local.network> (raw)
In-Reply-To: <49E3D7AA.1050207@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
Hi,
[Re-added Cc's, hope you hadn't dropped them on purpose. Sorry for spamming if
they were trimmed deliberately.]
On Mon, Apr 13, 2009 at 07:24:10PM -0500, Larry Finger wrote:
> Forest Bond wrote:
>
> > 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.
>
> You might be able to get it added to the drivers/staging directory - that is
> where the c r a p drivers that have no chance of making it to mainline are put.
>
> To see what is wrong with that driver, compare its coding style to that of any
> driver in the drivers/net/wireless directory tree.
>
> A second problem is that no new drivers that implement a software-based MAC
> layer are likely to be accepted - this driver would have to be modified to use
> mac80211.
Great, this is enough to get started, at least. I assume that the quality bar
is low for code in drivers/staging. Low quality work is a trademark of mine, so
I should be able to tackle this. ;)
Is there any reason I ought to think that it would be easier to get this
accepted in linux-staging than drivers/staging? I'll admit that I feel better
about the layout of drivers/staging than I do about the quilt stuff in
linux-staging.
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:55 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
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 [this message]
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=20090414005523.GC31504@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--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).