Google Summer of Code 2012 - Application for the Linux Foundation submitted
Hi,
I have submitted the application for the Linux Foundation as mentoring organization in the GSoC 2012 to Google.
To get the best chances to get accepted again, the Google people need to see many project ideas. Please enter as soon as possible your project ideas on the appropriate sub pages on
https://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer-code-2012
or link to the project ideas on your web site ASAP. The application period ends tomorrow 23:00 UTC and from then on Google people will evaluate the applications. So please post your ideas as soon as possible!
If you have problems mail me with your project idea and your Linux Foundation user name. Note that you beed to be member of the "GSOC" group on the Linux Foundation. Please request appropriate membership and I will approve it.
Till
Quoted 11 lines · Till Kamppeter
Hi,
I have submitted the application for the Linux Foundation as mentoring organization in the GSoC 2012 to Google.
To get the best chances to get accepted again, the Google people need to see many project ideas. Please enter as soon as possible your project ideas on the appropriate sub pages on
https://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer-code-2012
Quoted 8 lines
or link to the project ideas on your web site ASAP. The application period ends tomorrow 23:00 UTC and from then on Google people will evaluate the applications. So please post your ideas as soon as possible!
If you have problems mail me with your project idea and your Linux Foundation user name. Note that you beed to be member of the "GSOC" group on the Linux Foundation. Please request appropriate membership and I will approve it.
So one idea I had was working on open firmware for ath9k_htc. We don't have the resources to open that up but can likely provide under NDA source code to let it get cleaned up for public release. If this is reasonable I'll throw it on.
Luis
Quoted 6 lines · Luis R. Rodriguez
So one idea I had was working on open firmware for
ath9k_htc. We don't have the resources to open that up but can likely provide under NDA source code to let it get cleaned up for public release. If this is reasonable I'll throw it on.
OK, please do it.
Till
Quoted 10 lines · Till Kamppeter
Quoted 7 lines · Luis R. Rodriguez
So one idea I had was working on open firmware for
ath9k_htc. We don't have the resources to open that up but can likely provide under NDA source code to let it get cleaned up for public release. If this is reasonable I'll throw it on.OK, please do it.
OK I'll add some other thing for backports. I'll try to see if some is up for backporting a video driver and integrating it with compat.
Luis
Quoted 9 lines · Till Kamppeter
Quoted 6 lines · Luis R. Rodriguez
So one idea I had was working on open firmware for
ath9k_htc. We don't have the resources to open that up but can likely provide under NDA source code to let it get cleaned up for public release. If this is reasonable I'll throw it on.
Quoted 3 lines
OK, please do it.
Till
Wait wait wait... qualcomm/Atheros does not have the resources, so how on earth should a student (or students) actually do that?
Given the TODO over at
<http://wireless.kernel.org/en/users/Drivers/ath9k_htc#TODO> [Scroll down till you get "fixed in the firmware. ]. This would be at least one years of full-time work for a small team of trained code-monkey and therefore this "project" is highly unrealistic.
Maybe we should stick to something less complicated.
Like extending PID to use MCS rates, or implementing a TPC control algorithm [this is stuff, every drivers could use].
Quoted 15 lines · Martin Schleier
Quoted 9 lines · Till Kamppeter
Quoted 6 lines · Luis R. Rodriguez
So one idea I had was working on open firmware for
ath9k_htc. We don't have the resources to open that up but can likely provide under NDA source code to let it get cleaned up for public release. If this is reasonable I'll throw it on.Quoted 3 lines
OK, please do it.
Till
Quoted 8 lines
Wait wait wait... qualcomm/Atheros does not have the resources, so how on earth should a student (or students) actually do that?
Given the TODO over at
<http://wireless.kernel.org/en/users/Drivers/ath9k_htc#TODO> [Scroll down till you get "fixed in the firmware. ]. This would be at least one years of full-time work for a small team of trained code-monkey and therefore this "project" is highly unrealistic.
It didn't take one year to open up the ar9170.fw [0] which lead to carl9170.fw [1] and we even had two drivers from this work. I think you underestimate our potential ;)
[0] http://wireless.kernel.org/en/users/Drivers/ar9170.fw
[1] http://wireless.kernel.org/en/users/Drivers/carl9170.fw
Quoted 1 line
Maybe we should stick to something less complicated.
Lets not undermine potential.
Quoted 2 lines
Like extending PID to use MCS rates, or implementing a TPC control algorithm [this is stuff, every drivers could use].
PID? Hah, PID is dead. And TPC -- well... that requires a long answer. Just finding documentation on TPC and what vendors do for TPC is as much hard work as writing open firmware. But hey, its a wiki, feel free to add what you think might be good, you can, and please be verbose ;)
http://wireless.kernel.org/en/developers/GSoC/2012
Luis