From: Chris Ball <cjb@laptop.org>
To: Greg KH <greg@kroah.com>
Cc: tech-board-discuss@lists.linux-foundation.org
Subject: Re: [Tech-board-discuss] Obtaining hardware for writing Linux drivers?
Date: Fri, 04 Mar 2011 18:51:06 -0500 [thread overview]
Message-ID: <m3fwr2la1h.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <20110304233219.GB28060@kroah.com> (Greg KH's message of "Fri, 4 Mar 2011 15:32:19 -0800")
Hi Greg, thanks for the reply,
On Fri, Mar 04 2011, Greg KH wrote:
> On Fri, Mar 04, 2011 at 04:23:31PM -0500, Chris Ball wrote:
>> In the case of this particular device, I was pointed at Bdale Garbee by
>> people on IRC (but wouldn't have known to e-mail him myself) and will
>> see if I can get him to help. But, even assuming he can help me, that
>> still doesn't solve the problem in the general case. Any ideas?
>
> I'd be glad to step up and work on accomplishing this. But, supposing I
> am successful in getting these contacts and keeping them up to date, how
> would you recommend that we publicize this type of functionality that we
> could now provide?
A strawman proposal might look like:
* A mail to lkml announcing the program
* LWN article doing the same
* A mail to LF company members asking them to nominate a contact
person and encouraging them to take part, explaining how they'll
benefit from people who *already* want to write drivers for them
for free and just can't get the hardware they need to do so.
Once a decent mass of kernel hackers know about it, I'm sure it'll
spread by word of mouth to reach everyone else who needs to know;
I don't think there'll be a problem with disseminating the program
once the first batch of hackers knows about it.
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-03-04 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 21:23 [Tech-board-discuss] Obtaining hardware for writing Linux drivers? Chris Ball
2011-03-04 23:32 ` Greg KH
2011-03-04 23:51 ` Chris Ball [this message]
2011-03-05 0:23 ` Greg KH
2011-03-05 15:38 ` Jim Zemlin
2011-03-05 22:32 ` Greg KH
2011-03-05 22:59 ` Jim Zemlin
2011-03-05 23:29 ` Greg KH
2011-03-05 23:44 ` Greg KH
2011-03-05 23:49 ` Jim Zemlin
2011-03-06 0:40 ` Greg KH
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=m3fwr2la1h.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=greg@kroah.com \
--cc=tech-board-discuss@lists.linux-foundation.org \
/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