On Friday, July 20, 2012 5:39:04 PM UTC+3, Jean-Baptiste Queru wrote:
> We're currently stuck on the code review of a platform change to > disable VSync on hardware that doesn't support it. Until that change > gets approved by the maintainer of that code, we can't move forward.
> JBQ
> On Fri, Jul 20, 2012 at 5:55 AM, Martin Heller <heller.m...@gmail.com> > wrote: > > Hello,
> > do you have an idea when AOSP builds for PandaBoard will be fixed? > > And will the master branch (i.e. 4.1) be fixed or a working tagged > > release of 4.0 will be made?
> > Thanks
> > Martin
> > On 07/13/2012 04:56 PM, Jean-Baptiste Queru wrote: > >> We have changes in process that are expected to fix things. If those > >> don't work, we'll find a way to go back to the last-known-good state.
> >> JBQ
> > -- > > You received this message because you are subscribed to the "Android > Building" mailing list. > > To post to this group, send email to android-building@googlegroups.com > > To unsubscribe from this group, send email to > > android-building+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-building?hl=en
> -- > Jean-Baptiste M. "JBQ" Queru > Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
On Monday, July 30, 2012 7:20:37 AM UTC-5, Ferruh Yiğit wrote:
> Hi,
> Is there any update on issue? Any possible date for fix?
> Or is there any alternative way to make pandaboard work with graphics > using AOSP?
> Thanks and Regards,
> ferruh
> On Friday, July 20, 2012 5:39:04 PM UTC+3, Jean-Baptiste Queru wrote:
>> We're currently stuck on the code review of a platform change to >> disable VSync on hardware that doesn't support it. Until that change >> gets approved by the maintainer of that code, we can't move forward.
>> JBQ
>> On Fri, Jul 20, 2012 at 5:55 AM, Martin Heller <heller.m...@gmail.com> >> wrote: >> > Hello,
>> > do you have an idea when AOSP builds for PandaBoard will be fixed? >> > And will the master branch (i.e. 4.1) be fixed or a working tagged >> > release of 4.0 will be made?
>> > Thanks
>> > Martin
>> > On 07/13/2012 04:56 PM, Jean-Baptiste Queru wrote: >> >> We have changes in process that are expected to fix things. If those >> >> don't work, we'll find a way to go back to the last-known-good state.
>> >> JBQ
>> > -- >> > You received this message because you are subscribed to the "Android >> Building" mailing list. >> > To post to this group, send email to android-building@googlegroups.com >> > To unsubscribe from this group, send email to >> > android-building+unsubscribe@googlegroups.com >> > For more options, visit this group at >> > http://groups.google.com/group/android-building?hl=en
>> -- >> Jean-Baptiste M. "JBQ" Queru >> Technical Lead, Android Open Source Project, Google.
>> Questions sent directly to me that have no reason for being private >> will likely get ignored or forwarded to a public forum with no further >> warning.
On Monday, 30 July 2012 14:20:37 UTC+2, Ferruh Yiğit wrote:
> Is there any update on issue? Any possible date for fix?
From what I've learned over the last few weeks, "experimental support for PandaBoard" usually means "it won't work": there is no AOSP branch or tag where PandaBoard not only builds but also works as a platform. If you are lucky, you can get a fully working PandaBoard build from "master".
If you spot one of these rare beasties, *please* do a repo manifest snapshot and provide that manifest for download.
NB: Google are not paid for PandaBoard support, so it is amazing that *
building* works as reliably as it does.
As far as I understand, another part of the problem is that the PandaBoard at its core has an OMAP4430, and the graphics library is not open-source. Luckily for us all Imagine Technologies provides precompiled shared objects, but these also need to be in sync with the open-source interface part used by the applications. Not easy!
> Or is there any alternative way to make pandaboard work with graphics > using AOSP?
If you have the knowledge, incentive, and time to actually debug the issues yourself, fix the issues, then submit the patches back to AOSP and (hopefully quickly) get some people to review and _tag_ them on the AOSP repo.
In short, "get involved and help". :-)
For my purposes, I was lucky and found another post with a download link for a PandaBoard manifest that at least allowed me to run several Dalvik VMs and get a shell, and this was all I needed (at the time).
NB: The Google folks are doing some amazing work with AOSP, and without their openness we would have much less than we do - a thoroughly reliable build, continuous improvement, and a chance of getting a working platform.
With the complexity of embedded development you can't expect them to really care for a platform that is not in the focus of their own core interests. The workload is already too high, so if you want something, you have to help.
On Tuesday, July 31, 2012 9:37:07 AM UTC+2, hagenp wrote:
> On Monday, 30 July 2012 14:20:37 UTC+2, Ferruh Yiğit wrote:
>> Is there any update on issue? Any possible date for fix?
> From what I've learned over the last few weeks, "experimental support for > PandaBoard" usually means "it won't work": there is no AOSP branch or tag > where PandaBoard not only builds but also works as a platform. If you are > lucky, you can get a fully working PandaBoard build from "master".
> If you spot one of these rare beasties, *please* do a repo manifest > snapshot and provide that manifest for download.
> NB: Google are not paid for PandaBoard support, so it is amazing that *
> building* works as reliably as it does.
> As far as I understand, another part of the problem is that the PandaBoard > at its core has an OMAP4430, and the graphics library is not open-source. > Luckily for us all Imagine Technologies provides precompiled shared > objects, but these also need to be in sync with the open-source interface > part used by the applications. Not easy!
>> Or is there any alternative way to make pandaboard work with graphics >> using AOSP?
> If you have the knowledge, incentive, and time to actually debug the > issues yourself, fix the issues, then submit the patches back to AOSP and > (hopefully quickly) get some people to review and _tag_ them on the AOSP > repo.
> In short, "get involved and help". :-)
> For my purposes, I was lucky and found another post with a download link > for a PandaBoard manifest that at least allowed me to run several Dalvik > VMs and get a shell, and this was all I needed (at the time).
> NB: The Google folks are doing some amazing work with AOSP, and without > their openness we would have much less than we do - a thoroughly reliable > build, continuous improvement, and a chance of getting a working platform.
> With the complexity of embedded development you can't expect them to > really care for a platform that is not in the focus of their own core > interests. The workload is already too high, so if you want something, you > have to help.
On Tuesday, July 31, 2012 2:37:07 AM UTC-5, hagenp wrote:
> On Monday, 30 July 2012 14:20:37 UTC+2, Ferruh Yiğit wrote:
>> Is there any update on issue? Any possible date for fix?
> From what I've learned over the last few weeks, "experimental support for > PandaBoard" usually means "it won't work": there is no AOSP branch or tag > where PandaBoard not only builds but also works as a platform. If you are > lucky, you can get a fully working PandaBoard build from "master".
> Agreed. > If you spot one of these rare beasties, *please* do a repo manifest > snapshot and provide that manifest for download.
> NB: Google are not paid for PandaBoard support, so it is amazing that *
> building* works as reliably as it does.
> Of course .. no complaints there. > As far as I understand, another part of the problem is that the PandaBoard > at its core has an OMAP4430, and the graphics library is not open-source. > Luckily for us all Imagine Technologies provides precompiled shared > objects, but these also need to be in sync with the open-source interface > part used by the applications. Not easy!
> This I was not aware! Thanks for the info. i will ask around more to find
out if there is a easy way to fix this.
>> Or is there any alternative way to make pandaboard work with graphics >> using AOSP?
> If you have the knowledge, incentive, and time to actually debug the > issues yourself, fix the issues, then submit the patches back to AOSP and > (hopefully quickly) get some people to review and _tag_ them on the AOSP > repo.
> In short, "get involved and help". :-)
> Sure! I hope to get the Linaro one built soon. Once I have that I will try
> For my purposes, I was lucky and found another post with a download link > for a PandaBoard manifest that at least allowed me to run several Dalvik > VMs and get a shell, and this was all I needed (at the time).
> NB: The Google folks are doing some amazing work with AOSP, and without > their openness we would have much less than we do - a thoroughly reliable > build, continuous improvement, and a chance of getting a working platform.
> With the complexity of embedded development you can't expect them to > really care for a platform that is not in the focus of their own core > interests. The workload is already too high, so if you want something, you > have to help.
I've just added a branch ics-plus-aosp that matches the state of the
AOSP master before the Jelly Bean release. In quick testing, it seems
to work on PandaBoard.
On Wed, Aug 1, 2012 at 11:29 AM, Magnus Bäck <ba...@google.com> wrote:
> On Wednesday, August 01, 2012 at 10:03 EDT,
> sebbi <sebi.stic...@googlemail.com> wrote:
>> I have a good checkout of the AOSP master before they merged it with JB.
>> What do I have to provide to help others? Really like that copy, runs
>> almost perfect on my Pandaboard ES with Wifi+BT running pretty good.
> You can capture the state of your repository and produce a manifest file
> with SHA-1s that others can sync against:
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
-- Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
On Wednesday, August 1, 2012 4:36:47 PM UTC-5, Jean-Baptiste Queru wrote:
> I've just added a branch ics-plus-aosp that matches the state of the > AOSP master before the Jelly Bean release. In quick testing, it seems > to work on PandaBoard.
> JBQ
> On Wed, Aug 1, 2012 at 11:29 AM, Magnus Bäck <ba...@google.com> wrote: > > On Wednesday, August 01, 2012 at 10:03 EDT, > > sebbi <sebi.stic...@googlemail.com> wrote:
> >> I have a good checkout of the AOSP master before they merged it with > JB.
> >> What do I have to provide to help others? Really like that copy, runs > >> almost perfect on my Pandaboard ES with Wifi+BT running pretty good.
> > You can capture the state of your repository and produce a manifest file > > with SHA-1s that others can sync against:
> > -- > > You received this message because you are subscribed to the "Android > Building" mailing list. > > To post to this group, send email to android-building@googlegroups.com > > To unsubscribe from this group, send email to > > android-building+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-building?hl=en
> -- > Jean-Baptiste M. "JBQ" Queru > Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
On Wednesday, August 1, 2012 4:03:19 PM UTC+2, sebbi wrote:
> I have a good checkout of the AOSP master before they merged it with JB.
> What do I have to provide to help others? Really like that copy, runs > almost perfect on my Pandaboard ES with Wifi+BT running pretty good.
> On Tuesday, July 31, 2012 9:37:07 AM UTC+2, hagenp wrote:
>> On Monday, 30 July 2012 14:20:37 UTC+2, Ferruh Yiğit wrote:
>>> Is there any update on issue? Any possible date for fix?
>> From what I've learned over the last few weeks, "experimental support for >> PandaBoard" usually means "it won't work": there is no AOSP branch or tag >> where PandaBoard not only builds but also works as a platform. If you are >> lucky, you can get a fully working PandaBoard build from "master".
>> If you spot one of these rare beasties, *please* do a repo manifest >> snapshot and provide that manifest for download.
>> NB: Google are not paid for PandaBoard support, so it is amazing that *
>> building* works as reliably as it does.
>> As far as I understand, another part of the problem is that the >> PandaBoard at its core has an OMAP4430, and the graphics library is not >> open-source. Luckily for us all Imagine Technologies provides precompiled >> shared objects, but these also need to be in sync with the open-source >> interface part used by the applications. Not easy!
>>> Or is there any alternative way to make pandaboard work with graphics >>> using AOSP?
>> If you have the knowledge, incentive, and time to actually debug the >> issues yourself, fix the issues, then submit the patches back to AOSP and >> (hopefully quickly) get some people to review and _tag_ them on the AOSP >> repo.
>> In short, "get involved and help". :-)
>> For my purposes, I was lucky and found another post with a download link >> for a PandaBoard manifest that at least allowed me to run several Dalvik >> VMs and get a shell, and this was all I needed (at the time).
>> NB: The Google folks are doing some amazing work with AOSP, and without >> their openness we would have much less than we do - a thoroughly reliable >> build, continuous improvement, and a chance of getting a working platform.
>> With the complexity of embedded development you can't expect them to >> really care for a platform that is not in the focus of their own core >> interests. The workload is already too high, so if you want something, you >> have to help.
On Thursday, August 2, 2012 12:36:47 AM UTC+3, Jean-Baptiste Queru wrote:
> I've just added a branch ics-plus-aosp that matches the state of the > AOSP master before the Jelly Bean release. In quick testing, it seems > to work on PandaBoard.
> JBQ
> On Wed, Aug 1, 2012 at 11:29 AM, Magnus Bäck <ba...@google.com> wrote: > > On Wednesday, August 01, 2012 at 10:03 EDT, > > sebbi <sebi.stic...@googlemail.com> wrote:
> >> I have a good checkout of the AOSP master before they merged it with > JB.
> >> What do I have to provide to help others? Really like that copy, runs > >> almost perfect on my Pandaboard ES with Wifi+BT running pretty good.
> > You can capture the state of your repository and produce a manifest file > > with SHA-1s that others can sync against:
> > -- > > You received this message because you are subscribed to the "Android > Building" mailing list. > > To post to this group, send email to android-building@googlegroups.com > > To unsubscribe from this group, send email to > > android-building+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-building?hl=en
> -- > Jean-Baptiste M. "JBQ" Queru > Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
On Wednesday, August 1, 2012 11:36:47 PM UTC+2, Jean-Baptiste Queru wrote:
> I've just added a branch ics-plus-aosp that matches the state of the > AOSP master before the Jelly Bean release. In quick testing, it seems > to work on PandaBoard.
Yay - first time I got video from an ICS build on PandaBoard! Many thanks!!!
- - -
[Bonus advice for others trying to get PandaBoard/ICS up and running with the ics-plus-aosp branch.]
For PandaBoard, device/ti/panda/README is relevant, but there are a few stumbling blocks to avoid:
1. When you download the "proprietary binaries", use "PandaBoard binaries for Android 4.0.4 (IMM76I to IMM76L)" 2. In device/ti/panda/README, sections "Initial setup, part 1" and "Build and flash, part 1": use "lunch full_panda-userdebug" or "lunch full_panda-eng" (not two underscores) 3. Post-boot setup: "adb shell date $(date +%s)" will set the date on PandaBoard in UTC. "adb shell date -s $(date +%Y%m%d.%H%M%S)" will set it to your local timezone. If you want to do the "date -s YYYYMMSS.hhmmss" manually (or with a terminal script) on a PandaBoard console terminal, don't forget to first obtain root rights with "su" - by default the console user is restricted. 4. For me, after making an SD card with fastboot, ICS on PandaBoard reported EXT4-FS (mmcblk0p6): VFS: Can't find ext4 filesystem and later stops with an SysRq : Emergency Remount R/O This is an indication that "fastboot erase cache" did not create a valid ext4 file system. You can easily fix this by manually formatting the SD card 'cache' partition as ext4. On my Ubuntu 10.04LTS development box, an external SDHC reader works well together with the "Disk Utility" (palimpsest) from the "System" > "Administration" menu. This also displays the efi partition labels, which is handy to make sure you really ext4-format the correct partition. 5. Enjoy! :-)
<eric.pfaffhau...@gmail.com> wrote:
> Branch ics-plus-aosp works great. Thanks JBQ!
> But: where can I find the sources/repos/configs you've used to create
> bootloader.bin and x-loader.bin?
> eRiC
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
-- Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
On Tuesday, August 7, 2012 11:24:14 AM UTC-5, Jean-Baptiste Queru wrote:
> I believe that they're on git.omapzoom.org, but I'm not sure. I got > those binaries directly from TI.
> JBQ
> On Tue, Aug 7, 2012 at 9:22 AM, Eric Pfaffhauser > <eric.pfaffhau...@gmail.com> wrote: > > Branch ics-plus-aosp works great. Thanks JBQ!
> > But: where can I find the sources/repos/configs you've used to create > > bootloader.bin and x-loader.bin?
> > eRiC
> > -- > > You received this message because you are subscribed to the "Android > > Building" mailing list. > > To post to this group, send email to android-building@googlegroups.com > > To unsubscribe from this group, send email to > > android-building+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-building?hl=en
> -- > Jean-Baptiste M. "JBQ" Queru > Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
bootloader.bin identifies itself as 'U-Boot 1.1.4-gedeced79 (Feb 6 2012 - 09:27:11)'. Any pointer where to find this exact git revision (gedeced79)? Thanks! -Hagen
> bootloader.bin identifies itself as 'U-Boot 1.1.4-gedeced79 (Feb 6 2012 -
> 09:27:11)'.
> Any pointer where to find this exact git revision (gedeced79)? Thanks!
> -Hagen
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
-- Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
On Wed, Aug 8, 2012 at 5:30 PM, Jean-Baptiste Queru (JBQ) wrote: > If this is similar to the kernel markers, gedeced79 means "Git commit > edeced79", so you need to look for revision edeced79
Many thanks for pointing out the 'g' is not part of the revision! ('g' is not even a hex digit... i did not spot the clue... argh!)
Hmm... still no luck. "git show edeced79' returned with an error message (ambiguous or not found). Is there a special search incantation, or is this likely a "private commit"? [Or is it still in review? ;-)]
"u-boot commit edeced79 seen anywhere, dead or alive? Please report!" :-)
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
It's seems that the Pandaboard does not boot with the new kernel (commit 985648b1897e56fd62ba24e1e94c9fe0ef3d0bad in device/ti/panda) and updated graphics drivers (20120807).
The problem is that the kernel does not start :
See the boot trace of my pandaboard :
Texas Instruments X-Loader 1.41 (Oct 21 2011 - 09:28:33)
OMAP4460: 1.2 GHz capable SOM
Starting OS Bootloader from MMC/SD1 ...
> There's a known issue with graphics on PandaBoard, where the display > is entirely black.
> I suspect that's related to the changes that were done in Jelly Bean > around triple buffering.
> My understanding is that someone is already working on updating the > graphics libraries. In the meantime, PandaBoards won't display much > :-(
> JBQ
> -- > Jean-Baptiste M. "JBQ" Queru > Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private > will likely get ignored or forwarded to a public forum with no further > warning.
For me (ES EB3), the kernel boots, but the graphics system fails to
initialize, in a way that looks like an incompatibility between
userland and the kernel.
I'm pretty sure that it was working when I prepared those files, but
that was weeks ago.
Do things still working when going back to the previous kernel and
graphics libraries?
On Fri, Sep 28, 2012 at 7:24 AM, hagenp <hagen.pat...@gmail.com> wrote:
> On Friday, 28 September 2012 08:20:38 UTC+2, Adrien Grassein wrote:
>> Someone else have the same problem?
> Yes. I just checked, and with a current "master" build for full_panda-eng
> the kernel hangs (ES2.1).
> ("repo manifest -r " also throws errors, so I can't even upload a snapshot
> manifest. Tsk.)
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
-- Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
On Fri, Sep 28, 2012 at 8:36 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> For me (ES EB3), the kernel boots, but the graphics system fails to
> initialize, in a way that looks like an incompatibility between
> userland and the kernel.
> I'm pretty sure that it was working when I prepared those files, but
> that was weeks ago.
> Do things still working when going back to the previous kernel and
> graphics libraries?
> JBQ
> On Fri, Sep 28, 2012 at 7:24 AM, hagenp <hagen.pat...@gmail.com> wrote:
>> On Friday, 28 September 2012 08:20:38 UTC+2, Adrien Grassein wrote:
>>> Someone else have the same problem?
>> Yes. I just checked, and with a current "master" build for full_panda-eng
>> the kernel hangs (ES2.1).
>> ("repo manifest -r " also throws errors, so I can't even upload a snapshot
>> manifest. Tsk.)
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-building@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-building+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
> --
> Jean-Baptiste M. "JBQ" Queru
> Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
-- Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
> For me (ES EB3), the kernel boots, but the graphics system fails to
> initialize, in a way that looks like an incompatibility between
> userland and the kernel.
> I'm pretty sure that it was working when I prepared those files, but
> that was weeks ago.
> Do things still working when going back to the previous kernel and
> graphics libraries?
> JBQ
> On Fri, Sep 28, 2012 at 7:24 AM, hagenp <hagen.pat...@gmail.com> wrote:
> > On Friday, 28 September 2012 08:20:38 UTC+2, Adrien Grassein wrote:
> >> Someone else have the same problem?
> > Yes. I just checked, and with a current "master" build for full_panda-eng
> > the kernel hangs (ES2.1).
> > ("repo manifest -r " also throws errors, so I can't even upload a
> snapshot
> > manifest. Tsk.)
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/android-building?hl=en
> --
> Jean-Baptiste M. "JBQ" Queru
> Technical Lead, Android Open Source Project, Google.
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
Which previous kernel are you using? We have built Android with prebuilt kernel, works fine, but now we use the kernel from the kernel build page and it doesn't work. A linaro 2.6.35 will allow me to build but gets hung up after booting kernel. So does a 3.4. Please help. We would like to build android with kernel source rather than prebuilt and get it running on pandaboard, so that we can include custom hardware/firmware files but we've had no luck finding a kernel compatible with android. We are willing to revert to previous android build if necessary. Thanks, BT
