From: Antti Palosaari <crope@iki.fi>
To: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Subject: GSoC: open firmware for ath9k_htc
Date: Wed, 04 Apr 2012 01:12:47 +0300 [thread overview]
Message-ID: <4F7B75DF.2040008@iki.fi> (raw)
Hello!
I am information engineering student of University of Oulu, Department
of Computer Science and Engineering, from Finland EU.
I have applied GSoC project called open firmware for ath9k_htc. It was
the really only somehow interesting topic as I would like to do
something Kernel related.
http://wireless.kernel.org/en/developers/GSoC/2012/ath9k_htc_open_firmware
I am active developer of the Linux-Media subsystem. My main
contributions are big amount of digital television chip and device
drivers. More about that can be found from my personal project page.
http://palosaari.fi/linux/
As I see that GSoC project needs some embedded skills and many are
surely interested to known if I have enough experience. Unfortunately I
don't have embedded experience as much as Kernel driver development
experience, but I think I still have rather good understanding which
should be enough for success project. Also I think it is worth to
mention I have rather much protocol reverse-engineering expertise,
especially USB and I2C, coming from the Linux DVB hacking.
Here is a list of embedded projects I quickly remember, not all, but
likely the biggest ones still.
Embedded thermometer. School project. Own made PCB, Philips 89C52 MCU
(Intel 8052 clone), two I2C controllable temperature sensors, two relays
and LCD display. Programming language C.
Learning remote controller. School project. Own made PCB, Atmel ATmega32
MCU, LCD display, JTAG, IR receiver, IR sender, few buttons. Programming
language C.
http://palosaari.fi/img_1305.jpg
SIP phone. School project. Hardware was Atmel ATmega128 MCU based board
called Ethernut2.1. Only some very limited SIP stack and ethernet
networking was implemented. RTP, meaning voice codecs, was not done.
Programming language C.
http://www.ethernut.de/en/hardware.html
"Egg-timer". School project. Atmel ATmega128 MCU based development board
called Olimex AVR-MT-128. LCD display, buzzer, relay, few buttons. I
coded running Pacman for the LCD screen top of all required
functionality :) Programming language C.
http://www.olimex.com/dev/avr-mt128.html
Test firmware for one Cypress EZ-USB FX2LP based DVB USB device. Cypress
FX2 is general and very common USB -interface chip. Firmware I did was
based of open Termini design. Due to that relative small amount changes
was needed.
http://www.cypress.com/?id=193
http://linuxtv.org/cgi-bin/viewvc.cgi/dvb-hw/dvbusb-fx2/
Electric meter. School project. FPGA. Hardware was Altera DE2
development board, featuring an Altera Cyclone II 2C35 FPGA. [6]
http://www.altera.com/education/univ/materials/boards/de2/unv-de2-board.html
After all I haven't got too many answers about that project. It sounds
like something overkill to make WLAN firmware from the scratch, but in
my understanding here is somehow working skeleton that can be use as a
example which reduces of course workload.
regards
Antti
--
http://palosaari.fi/
reply other threads:[~2012-04-03 22:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F7B75DF.2040008@iki.fi \
--to=crope@iki.fi \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.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;
as well as URLs for NNTP newsgroup(s).