Petter You are correct.I followed the same.But I doubt there will be some
MD5 *checksum *ssociated with it which I dont have any clue.
"same root structure like orig"..hmmm..i could try this as well.
plz if some one who has success in this , do report(in either SGT or SGS )
Rgds,
Saurabh
"..pain
I am trying to port gingerbread kernel to zoom3 board.
The kernel was download from omapzoom git server.
Kernel(top of the tree):
# git clone git://git.omapzoom.org/kernel/omap.git android-2.6.35
# cd android-2.6.35
# git checkout -b p-android-omap-2.6.35 --track origin/p-android-omap-2.6.35
def
I think that your problem is, that samsung uses initramfs in kernel
image, so theirs modules(and other files) are packed in zImage, so if
are some of these modules(files) not open, you must extract them from
orig. kernel, put them into your kernel and pack your kernel with all
these modules(files).
I think use the fresh kernel suited for ZOOM3.
Try to give the proper details about the issue.
Regards,
Jagan.
On Tue, Dec 13, 2011 at 8:03 PM, Ismail wrote:
> Amar Nath gmail.com> writes:
>
> >
> > Hi Sri,
> >
> > "Starting kernel..." is indeed the last message that u-boot prints
> > just bef
Amar Nath gmail.com> writes:
>
> Hi Sri,
>
> "Starting kernel..." is indeed the last message that u-boot prints
> just before jumping to
> the kernel entry point, so my understanding is that the your u-boot is
> working just fine.
>
> However, if your uImage is generated with a wrong entry poi
Hi
I download the source directory of android brunch 2.3.5 and compiled it to
receive the filesystem. I got an empty filesystem (~150KB) and added under
/lib/modules/ the new 7 modules from the kernel compilation.
The next step was to mkbootfs to recreate the new file system and then
mkbootimg fro
HI Kiran,
Do you have the set of instructions for the same.Plz send or direct us to
any such link.That will life saver for all of us.
Rgds,
Saurabh
"..pain is temporary.quitting lasts forever.."
On Tue, Dec 13, 2011 at 5:26 PM, Kiran Kumar Raparthy <
kumarsharma.andr...@gmail.com> wrote:
Hi Tal,
Usually your Bootloader will launch the kernel image in any kind of linux
systems.
So you have to create the kernel image to be compatible with
bootloader(Which adds the Header,size and CRC),so that when launching the
kernel, bootloader verifies the header,gets the kernel image based on the
Hi, we have the same problems here.
We successfully re-compile the Samsung Android kernel sources but we
get a zImage of just 3.1MB that doesn't boot the TAB.
It seems there's a lack of something (lack of informations too!)
compared to the official Samsung P1000 zImage (~7MB).
Someone could help
I downloaded
GT-P1000_OpenSource.zip frmo the open source
It has --> Android build.sh GT-P1000_Kernel.tar.bz2
GT-P1000_Platform.tar.bz2 kernel README.txt
I followed teh README
1. How to Build
- get Toolchain
From Code Sourcery site ( www.codesourcery.com )
Sounds like your def_config isn't correct.
On Tue, Dec 13, 2011 at 7:22 AM, s.rawat wrote:
> I too got the same problem ,
> I did it for samsung galaxy tab 7 inches, my kernel image is 3.5 mb where
> the actual is around 7 mb.When I flashed it using the heimdall or odin the
> tab remains atteh b
I too got the same problem ,
I did it for samsung galaxy tab 7 inches, my kernel image is 3.5 mb where
the actual is around 7 mb.When I flashed it using the heimdall or odin the
tab remains atteh bootscreen and didnt go any further.I got frustrated at
one time and unplugged the cable and it resulte
12 matches
Mail list logo
