From: "Quiliro Ordóñez" <quiliro@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Fwd: [gNewSense-users] firmware development Fwd: convocatoria (pagada) a desarrollo
Date: Sun, 6 Sep 2009 11:00:24 -0500 [thread overview]
Message-ID: <606e87f00909060900n20469a68k4e2540b7d99334b4@mail.gmail.com> (raw)
In-Reply-To: <606e87f00909060835q51cb8b57h9544162ee1ade4ff@mail.gmail.com>
Dear folks.
I have like to have libre (free as in freedom) firmware for rt2561
wireless chipset. And forward this email for your consideration and
quote.
---------- Forwarded message ----------
From: Jason Self <jason.self@gmail.com>
Date: 2009/9/6
Subject: Re: [gNewSense-users] firmware development Fwd: convocatoria
(pagada) a desarrollo
To: gnewsense-users@nongnu.org
> Dear coleagues.
>
> As you might know, I use only libre software. If I would use semi-libre software I wouldn't have noticed the following. The wireless network card of most widespread use in Quito, Ecuador, South America is
>
> DLink DWL g 520 - RT61 Wireless LAN PCI Card
>
> It can be installed with kernel linux but its firmware is non-libre. I need that firmware to be developed as soon as possible and would like those whom feel capable of doing it (reverse engineering) post their quote for development. We consider paying different people (if that is possible) for different parts of the work.
>
> I would also ask to those whom would like to chip in for the payment of the development put some money in, express so and with how much money you would like to contribute for the payment of such development. If nobody destinates a budget, I will asume on my own the cost entirely but I asume that a small contribution starting from $1 will be possible for many people.
Have you contacted the folks at linuxwireless.org? Based on [1] it
appears that they would be willing to work with DLink (assuming that
DLink would be willing to work with them.) Even if not, perhaps you
might find an interested developer (or two or three) willing to take
it on?
[1] http://linuxwireless.org/en/vendors/DriverDevelopment
_______________________________________________
gNewSense-users mailing list
gNewSense-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/gnewsense-users
--
Saludos/Greetings
Quiliro Ordóñez
593(02)340 1517 / 593(09)821 8696
http://quiliro.wordpress.com
"Sólo cuando el último árbol esté muerto, el último río envenenado, y
el último pez atrapado, nos daremos cuenta que no se puede comer
dinero"
next parent reply other threads:[~2009-09-06 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <606e87f00812101427n351265a9u28dda004f7af37a4@mail.gmail.com>
[not found] ` <9de1a5ef0812131645l2cb021ebtf90fec38fea028ee@mail.gmail.com>
[not found] ` <20081214112923.2df83900@kgoetz.id.au>
[not found] ` <606e87f00909060614q545d758ch9f9d98bce7d276ad@mail.gmail.com>
[not found] ` <2EC2F428-19E1-4A4D-AF3A-C2F22BA3AFD7@gmail.com>
[not found] ` <606e87f00909060835q51cb8b57h9544162ee1ade4ff@mail.gmail.com>
2009-09-06 16:00 ` Quiliro Ordóñez [this message]
2009-09-08 16:06 ` [gNewSense-users] firmware development Fwd: convocatoria (pagada) a desarrollo Luis R. Rodriguez
2009-09-08 19:01 ` Gábor Stefanik
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=606e87f00909060900n20469a68k4e2540b7d99334b4@mail.gmail.com \
--to=quiliro@gmail.com \
--cc=linux-wireless@vger.kernel.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