Obviously, there's a process challenge, between the obvious need to get things to work at all and the desire to submit patches back to the main Android tree and have them accepted. This is a situation where "build one to throw away" might have some merit.
This is a team effort. It'd be sad to end up in a situation where some effort gets duplicated. It'd be even worse to end up in a situation where some effort is missing and the end goal isn't reached. It'll be easier to get the relevant patches accepted if they're small, if they have change descriptions that are actually descriptive, if some of the design decisions were discussed ahead of time, and if the overall task of getting patches submitted and accepted could be tracked in an android-related bug tracker. I've filed http://code.google.com/p/android/issues/detail?id=1449 for that purpose, we can spin off separate issues in the future. The roadmap at http://source.android.com/roadmap contains two relevant items: -the IMF/IME work that is currently scheduled for release during next quarter is likely to resolve many of the issues around a softkeyboard, and so much work has been put into it already that it wouldn't make sense to try to second-guess it before the code is available. Note that the IMF/IME work doesn't remove the requirement for "hardware" buttons for call/home/menu/back/end, so those will still need to be custom-emulated on the FreeRunner (and other devices with a similar form factor). -the open-source tree is currently scheduled to be udpated with an up-to-date version of the source code during this quarter. Because there's been quite some work done that hasn't been open-sourced yet and will be part of the update, making significant changes in the existing open-source tree is likely to cause future integration headaches, and it'd be better to try to limit ourselves to smaller changes until the "big" upgrade, to make the future merge easier. Looking forward to approving OpenMoko-related changes, JBQ On Thu, Dec 4, 2008 at 6:22 AM, Christopher Friedt <[EMAIL PROTECTED]> wrote: > > Hi Sean, > > On Tue, Nov 25, 2008 at 10:01 PM, Sean McNeil <[EMAIL PROTECTED]> wrote: >> Third, work that I have done needs cleanup to get past Googles >> high-grade review process. I have other things to do, so I honestly have >> no idea when I'll get around to that. > > I was one of the earlier guys to hack android onto the freerunner > myself, along with Ben, Brian, etc, and I checked out your patches. > > We were essentially working on the same thing, but I think you were > striving more to make it 'Just Work (TM)', while I was striving more > for completeness. What I mean is, that I was working on wrapping most > of the v5T instructions in either macros or subroutines so that the > v5T code could be made almost transparently portable to the v4T code, > while you bypassed most of the work that wasn't necessary at the time. > I think that's what the code reviewers did not like. > > If you would like some organized help to clean up your code, then just > point me in the right place and I'll get started. I've already written > up most of what's on the wiki page > (http://wiki.openmoko.org/wiki/Android), and have translated several > opcodes as well ( pld, clz, blx(2), ldrd/strd(all addressing modes) ). > I was calling the porting effort ANDROIDv4T. > > I took a break from Android for a while because a) I had some pressing > things at work, b) my master's thesis needed some more love, and c) my > baby boy got caught a flu, then my wife caught a flu, then I caught a > flu, etc. > > There are still some major limitations to the FreeRunner hardware, > unfortunately. Namely, there is no DSP and video / graphics support > will suffer until the Glamo is opened up a bit more. I can't see video > happening on Android / FreeRunner until then, and even at that point, > if Android isn't patched to make special use of the Glamo hardware, it > will still not work. > > Anyway, I did download your image - good work ;-) I haven't been able > to make calls yet though (or more importantly send SMS). Hopefully the > Android folks will soon finish the specs for a proper on-screen > keyboard (written for Dalvik??). > > Cheers, > > Chris > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-porting" group. To post to this group, send email to android-porting@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-porting?hl=en -~----------~----~----~----~------~----~------~--~---
