From: Chris Ball <cjb@laptop.org>
To: tech-board-discuss@lists.linux-foundation.org
Subject: [Tech-board-discuss] Obtaining hardware for writing Linux drivers?
Date: Fri, 04 Mar 2011 16:23:31 -0500 [thread overview]
Message-ID: <m3zkpalgvg.fsf@pullcord.laptop.org> (raw)
Hi TAB folks,
This is a little bit of a long story. I'm the upstream MMC maintainer,
and have started seeing bug reports for a new Realtek card reader that's
not yet supported in mainline. Here are some of the bugs:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658351 # Dell M301Z
https://bugs.meego.com/show_bug.cgi?id=2390 # HP Mini Note
I'd like to fix this by adding mainline support for the device, but it's
hard to do so without hardware. I'm sure there's *someone* in the
kernel community who knows people at Realtek or Dell or HP, one of whom
could get me access to hardware, but I don't know who that person is.
I'm thinking that it would be pretty helpful if (a) there was a person
who actively cultivated vendor contacts for this purpose, and (b) if the
kernel maintainers all knew who that person was, and that it's okay to
mail them if you're the maintainer of a driver and need to get hardware
to test/fix it on.
Does that make sense? Could LF be the right group to organize having
such a person exist?
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?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next reply other threads:[~2011-03-04 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 21:23 Chris Ball [this message]
2011-03-04 23:32 ` [Tech-board-discuss] Obtaining hardware for writing Linux drivers? Greg KH
2011-03-04 23:51 ` Chris Ball
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=m3zkpalgvg.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--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