Hello,
My name is Andrei and I am a 1st year Master's student in Computer
Science.
My general interests are embedded systems, operating systems and
wireless sensor networks. I have experience with C, Linux kernel
development, general operating systems concepts, some electronics. I
also have limited ARMv7 assembly knowledge, but will learn if needed.
I have previously worked with the ATNGW100 (development kit based on
Atmel's AVR32), so i'm familiar with U-boot, automatic build systems
(buildroot in that case), cross-compiling, boot-up sequence and so on,
this would be my first time using the BeagleBoard.
I've looked at the project and 3 of them interest me. One is down as
it was deemed too hard for gsoc (minix3 port). What i would like to
know are details on the two other projects, what is expected as
deliverable and whether you think i am well suited for that project or
not (maybe list some other requirements).
1) U-boot improvements for BeagleBoard. I suppose the biggest
challenge in this project is getting the USB host to work. Ethernet
adapter was available on the Atmel board, so i'm guessing there's no
driver for beagleboard. Probably should start with that, or follow the
keyboard->display->mouse path. What do you think?
What would be the hardware required for this project? A JTAG
programmer? I understand there's another loader (xloader i think)
before u-boot, why is that needed and what will it take to make u-boot
directly bootable?
2) PM framework: I understand that this involves mimicking the runtime
pm framework from x86 on omap. Does it also involve working on some
existing drivers to make them use the new framework?
Thanks in advance,
Andrei Voinescu
Andrei Voinescu wrote:
1) U-boot improvements for BeagleBoard. I suppose the biggest
challenge in this project is getting the USB host to work. Ethernet
adapter was available on the Atmel board, so i'm guessing there's no
driver for beagleboard. Probably should start with that, or follow the
keyboard->display->mouse path. What do you think?
uboot with working EHCI host I have here in the office, so I don't
think that is too hard. Apparently there are EHCI patches for uboot
floating around, some "glue" needs to be added though.
What would be the hardware required for this project? A JTAG
programmer? I understand there's another loader (xloader i think)
before u-boot, why is that needed and what will it take to make u-boot
directly bootable?
no jtag was used here.
2) PM framework: I understand that this involves mimicking the runtime
pm framework from x86 on omap. Does it also involve working on some
existing drivers to make them use the new framework?
there is a linux PM framework already for the OMAP3, you might want to have a
look at that...
Hello,
My name is Andrei and I am a 1st year Master's student in Computer
Science.
My general interests are embedded systems, operating systems and
wireless sensor networks. I have experience with C, Linux kernel
development, general operating systems concepts, some electronics. I
also have limited ARMv7 assembly knowledge, but will learn if needed.
I have previously worked with the ATNGW100 (development kit based on
Atmel's AVR32), so i'm familiar with U-boot, automatic build systems
(buildroot in that case), cross-compiling, boot-up sequence and so on,
this would be my first time using the BeagleBoard.
[...]
2)PMframework: I understand that this involves mimicking the runtimepmframeworkfrom x86 on omap. Does it also involve working on some
existing drivers to make them use the newframework?
Hello, thanks for your interest in the PM framework. We could
definitely use some help here.
We have a good base of PM on OMAP but are now embarking on converting
it over to using the new runtime PM framework in mainline.
I have already done the runtime PM core for OMAP. What remains is
converting drivers over to using runtime PM instead of directly
managing their clocks. I have also done a couple of sample drivers
(UART and MMC) and some others are underway by some folks at TI, but
the bulk of the work is yet to be started.
Kevin