Date: Sun, 1 Apr 2012 20:19:26 +0200 From: Aleksander Dutkowski <adutkowski@gmail.com> To: freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org Subject: [GSoC] [ARM] arm cleanup - my own proposal Message-ID: <CABkKHSZwco6kB8os7JZXaWk1=z99934hdwapOrrhhtT4X07-sg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
hello! after few weeks searching for interesting idea for me, I've decided to propose my own one. It is already mentioned on IdeasPage: - ARM cleanup Why I have chosen this one? I am very interested in embedded world. Now I am working on porting FBSD to at91sam9g45 - I will be much more motivated working on arm fbsd project than any other. Why should you let me do that project? While working on freebsd/arm I've noticed places that could be optimized, or separated, i.e. at91_samsize() should be declared for each board separately - now, this function has if-else and checks, which board is he running on. I would like to identify and fix that bugs, so the code will be more efficient and clear. Moreover, I think there should be a tutorial/framework for adding new boards or SoCs, so I will be simplier. I am currently reading the code in sys/arm/at91 and searching for improvements but I will be very pleased, if you send me your insights. The first question is - should I cleanup only at91 branch or more? I am quite familiar with at91 right now. The second - how to test the code? Some of boards could be tested in qemu, I could buy board with at91rm9200 for example, if I'm in. But maybe I will find here people with their own boards, they could help me testing? I havs sbc6045 board with at91sam9g45 SoC but it hasn't fbsd support yet (I'm working on it now :) ) I also thought about reducing kernel size for embedded, if arm cleanup won't fit. -- regards Aleksander Dutkowski http://ping.kti.gda.pl/~aleek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABkKHSZwco6kB8os7JZXaWk1=z99934hdwapOrrhhtT4X07-sg>