First module draft

[Claudio]

Hello Todor and Michal!

Todor already knows about the status of the chieroth.c. However, I
thought it would be nice to tell a bit about what I developed to day,
so that Michal is also informed.

This afternoon I wrote the whole (almost complete) skeleton of the
driver. This includes all the signal handlers and wrapper functions
for switching modes, initializing the driver, cleaning up, creating
the /proc information, deleting the /proc information, and much more.

Right now, the driver is full of functions and comments everywhere.
However, if you notice, the functions are mostly empty. We basically
have to field these functions in the chieroth.c with the missing
functionality. Plesae find enclosed a list, which I think it tells
what do we need to code still:

1) register the IRQ handlers (in the function register_interrupts())
2) unregister the IRQ handlers (in the function unregister_interrupts
())
3) modify proc_read(), so that it actually gives the information
about the freq. meter and so on
4) modify create_proc() and change the size of the proc file,
according to the amount of information we need there
5) implement the binary clock time formatting (for writing into the
LEDs) and writing to the LEDs
6) implement the functionality for update_freq_meter(), which will
basically update the /proc entry

For now, that's all that comes to my mind. If you check it carefully,
it is not much work, probably about 30 or 40 lines of code. Further,
the key points to be considered here are:

a) how to register the IRQs and to which counter
b) how to create the API for writing to the LEDs (e.g. binary clock
will use it)
c) how to create the information about the freq. meter and put it in
a nice way in the /proc entry

I hope this information is a little bit useful and that we can move
forward by Saturday. Actually, if we manage to properly connect the
IRQs, I think the job will be done.

Have a good evening :)


Claudio M. Camacho

[mpa...@gmail.com]

Hi Claudio,

We've just finished with Todor to write the frequency measurement part
of the project.
You can test it by displaying the proc entry.
What is most important for you is that the frequency of updating has
been increased to 2 Hz (it's already working). We decided that it's
more convenient and fluent.
I also made some mess as I started to write the LEDs display for
frequency measurement. I hope you don't mind some weird-looking global
variables...
See you soon!

Michal and Todor (or just me, because Todor is going to write another
message anyway)

[Todor Vlaev]

Hello guys,

We are approaching the 1000 lines ;) One of the minimum required
features (frequency measurement in /proc) is implemented.

I would just like to align the priorities, considering the latest improvements:
1. Binary Clock functionality: Claudio
1. Gadget board: Todor and Michal
2. Frequency LED indication: Michal
2. Mode switching and On/Off: to be decided (default: Todor)
3. Error handling: to be decided

So there is Green light for each of the tasks, except Frequency LED
indication, until a unified function for controlling the LEDs is
available. I suggest that we ignore the Mode switching and On/Off for
a while before the Binary Clock is ready as well.

Me and Michal will be designing the board during the weekend. I know
that due to exams the actual driver development will resume again on
Wednesday, so the plan is to have the hardware ready by then - no
rush.

Thank you for your hard work! Let's keep the momentum and target at
our respective tasks.

Have a nice evening!

Kind regards,
Todor

2009/5/22 <mpa...@gmail.com>:

--
Helsinki Metropolia University of Applied Sciences
Information Technology Programme

Todor Vlaev
Mobile: +358 50 935 0230

[Claudio]

Excellent Todor and Michal!

I will visit EVTEK tomorrow to work on the bits for the binary clock. Although the LEDs are not there, I will map the pins and create the functions to write decimal integers as bits, so I'll try to finish those functions for tomorrow.

For testing, I will also try to add binary clock information to the /proc (then it can be removed, after we have the board).

If you are going to visit EVTEK tomorrow, then see you tomorrow. Otherwise, have a nice weekend!

Best regards,

--
Claudio M. Camacho
http://www.claudiocamacho.org

[Todor Vlaev]

Hi,

That's perfect!

I think we're going to be there around 10-11. See y'all in the morning.

Kind regards,
Todor

2009/5/22 Claudio <claud...@gmail.com>: