[Arm-netbook] ICS build? Kernel 3.x ?

Tue Apr 10 08:05:41 BST 2012

Yep i figured it was for GB.

I'm guessing you are waiting for a stable kernel to come out and then
update your post.

Nevertheless, for someone like me, who is noob, i did not even know that it
was more like the standard build until you just mentioned.

My main aim is to just replace the system.img that i've built from the aosp
code.

Btw, can you tell me if this
post<http://forum.xda-developers.com/showthread.php?t=1490886&page=9#edit24523131>
will
actually work?

On Tue, Apr 10, 2012 at 12:20 PM, Sztupák Sz. Zsolt <mail at sztupy.hu> wrote:

> Hi!
>
> The tutorial you see is for Gingerbread builds as they are quite
> proprietary. I haven't updated them yet for ICS, mainly because an ICS
> build is more like the standard on these devices (kernel+initramfs in one
> file + system.img is a sparse ext4 in a separate one).
>
>  SztupY
>
> Akash <akash87 at gmail.com> a következőt írta:
>
> >On Tue, Apr 10, 2012 at 10:27 AM, Tom Cubie <mr.hipboi at gmail.com> wrote:
> >
> >>
> >>
> >> On Tue, Apr 10, 2012 at 11:56 AM, Akash <akash87 at gmail.com> wrote:
> >>
> >>>
> >>> On Apr 10, 2012 6:29 AM, "Tom Cubie" <mr.hipboi at gmail.com> wrote:
> >>> >
> >>> >
> >>> >
> >>> > On Mon, Apr 9, 2012 at 10:58 PM, Akash <akash87 at gmail.com> wrote:
> >>> >>
> >>> >> Hi,I downloaded allwinner-linux 3.0 branch from amery in github. i
> >>> changed the cross compile path to the appropriate location in
> >>> sun4i_crane.sh file. Running
> >>> >>
> >>> >> buil.sh -p sun4i_crane gives me an error in the build_standby
> >>> function, saying there is no make target for 'all'
> >>> (lichee/arch/arm/mach-sun4i/pm/standby inside this folder)
> >>> >>
> >>> >> I tried "making" it manually and it still gave me an error, from the
> >>> root of the kernel.
> >>> >>
> >>> >> Jus wanted to find out, did anyone ever try compiling it? And if so,
> >>> did it compile successfully? With/without the shell script
> >>> >>
> >>> >> I'm stuck with a small problem and im wondering if anyone might be
> >>> able to solve it.
> >>> >>
> >>> >> I've built ics aosp source code with the allwinner device files and
> >>> system core provided by sztupy. I managed to build it successfully and
> now
> >>> i have the system.img and the other output files that usual building
> spits
> >>> out. But in order to make it successfully compatible with allwinner a10
> >>> board, they say i have to run mkfs.sh script, but this REQUIRES a
> >>> kernel/compiled kernel files as you might know.
> >>> >> 1. Which of your kernels can i use to compile successfully? ( i
> would
> >>> be greatful if anyone can provide the bImage(compiled kernel) :) )
> >>> >
> >>> > You can use this kernel if you want to run android.
> >>> > https://github.com/allwinner/linux-2.6.36.git
> >>> Does ICS run on this kernel?
> >>
> >> ICS is not running on this kernel in products, but ICS can run on this
> >> kernel.
> >>
> >Thank you for this information, i will try it out and let you know!
> >
> >>
> >>> >>
> >>> >> 2. The tools provided by sztupy which will help disintegrate the
> >>> firmware image, Is it possible to use those files that have been
> extracted
> >>> back into the input for reconstructing it? If so how?
> >>> >
> >>> > Where is the tool?
> >>> The a10 kitchen tools...i can post the link if you want me to
> >>>
> >>> If you can get a kernel from an android ics image, you can use it in
> your
> >>> ics build. In ics, the
> >>> > nandb is the boot.img partition, which contains kernel and rootfs.
> >>> ooh thanks, and how do i get the recovery.img and root.img?
> >>
> >> recovey.img is not important, but you can get root.img from boot.img,
> it's
> >> an android
> >> defined image, you can see the header here:
> >>
> >>
> https://github.com/sztupy/allwinner_android_system_core/blob/android-2.3.7_r1/mkbootimg/bootimg.h
> >> You can check this page for more info:
> >>
> >>
> http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
> >>
> >You see i was going along this tutorial
> >http://forum.xda-developers.com/showthread.php?t=1490886
> >It was over there that i found the a10 flash kitchen tool, which says
> >according to
> >
> http://forum.xda-developers.com/showthread.php?t=1490886#post_message_22397975
> > that
> >
> >*B: Create image*
> >
> >If you have initialized the kitchen, you have to copy the four files from
> >linux (system.img, root.img, recovery.img and bImage) inside the _input
> >directory. You will also need to rename the .img files to .fex (so they
> >should be system.fex, root.fex, recovery.fex).
> >
> >If you are done with this, then run create_image.bat. It will create an
> >output.img file, that can be flashed to the device using LiveSuite.
> >
> >Naturally, from this i was thinking that those 4 files would be needed to
> >be able to create the final image.
> >
> >>
> >>> >>
> >>> >> 3. Ultimately i want to replace only the system.img in the final
> >>> image, is there a straight forward way to do that?
> >>> >
> >>> > Try fastboot.
> >>> Fastboot does not even recognize the damn device :p
> >>
> >> Fastboot needs u-boot running fastboot command and in fastboot state.
> >>
> >(Ok, i think i've to elaborate in this case, i'm using ubuntu 10.04 as per
> >the recommended build environment. Plugging in my device and taking it
> into
> >the fastboot state is when "fastboot devices" should list down the device.
> >But it is not doing so. I'm guessing i'm going to have to try it in
> windows
> >now)
> >Directly related to this, i was wondering, again because of looking at the
> >tutorial, it says i'm supposed to run the images through the shell script
> >mkfs.sh, which will give out system.img. Am i supposed to flash the img
> >given out by the shell script or am i supposed to flash the img that has
> >been derived from compiling the aosp code?
> >
> >>
> >>> >>
> >>> >> Thanks In advance!
> >>> >>
> >>> >> --
> >>> >>
> >>> >> Adrenaline Junkie
> >>> >>
> >>> >> _______________________________________________
> >>> >> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> >>> >> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> >>> >> Send large attachments to arm-netbook at files.phcomp.co.uk
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Keep simple, stay foolish.
> >>> >
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> >>> > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> >>> > Send large attachments to arm-netbook at files.phcomp.co.uk
> >>>
> >>>
> >>> _______________________________________________
> >>> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> >>> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> >>> Send large attachments to arm-netbook at files.phcomp.co.uk
> >>>
> >>
> >>
> >>
> >> --
> >> Keep simple, stay foolish.
> >>
> >>
> >>
> >> _______________________________________________
> >> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> >> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> >> Send large attachments to arm-netbook at files.phcomp.co.uk
> >>
> >
> >
> >
> >--
> >Adrenaline Junkie
> >
> >_______________________________________________
> >arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> >http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> >Send large attachments to arm-netbook at files.phcomp.co.uk
> _______________________________________________
> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> Send large attachments to arm-netbook at files.phcomp.co.uk
>

-- 
Adrenaline Junkie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.phcomp.co.uk/pipermail/arm-netbook/attachments/20120410/b457106f/attachment-0001.html 