On Fri, Mar 4, 2011 at 10:48 AM, Devon H. O'Dell <devon.od...@gmail.com> wrote: > I initially said that there's no way that I can do admin / mentor stuff, but: > > 2011/3/4 John Floren <j...@jfloren.net>: >> On Mar 4, 6:03 am, Jacob Todd <jaketodd...@gmail.com> wrote: >>> I hope so. There are some ideas listed on my site[1]. >>> >>> [1]http://bender.eugenics-research.org/doc/plan_9/GSoC/ >> >> I really like these ideas from your site: >> * Wifi drivers. I think WPA/WPA2 is the most important part; setting >> it up in Linux is a pain in the ass, we need a nice way to list >> networks, choose one, set a key, connect, etc. I think a wififs could >> handle this... cat /n/wifi/scan, echo 'key' > /n/wifi/key, etc. I >> think this one will be tough but not impossible > > This would make P9 a lot more useful for modern laptops, but I think > we tend to shy away from driver development for some reason. There are > good reasons that come up every year that I can't recall off the top > of my head. Similarly, it'd be nice to see some additional work with > ACPI (wasn't nemo working on that some?) > [remainder of message snipped] (forgot to actually send this to the list)
I think driver development gets avoided because it's harder. When you're developing a userspace app, if it crashes you just change the code and try again. If you're working on the kernel, you need a dedicated test machine that can netboot your experimental kernels. And then, when the kernel crashes, you have a hard time getting the debug info off. I can see how it would be easy to get discouraged doing a driver; this one would need somebody with previous kernel experience imo, be it Linux or Plan 9. John -- You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code" group. To post to this group, send email to plan9-gsoc@googlegroups.com. To unsubscribe from this group, send email to plan9-gsoc+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/plan9-gsoc?hl=en.
