Is there a way to save the log somewhere (like /cache or /data), so I
could check what did not work and get a start somewhere.
> there is a debug procedure called, RAM_CONSOLE, find it on google[enough
info]

Regards,
Jagan.

On Tue, Jan 24, 2012 at 9:29 PM, Rudolf Tammekivi <[email protected]>wrote:

> It's MSM7x30, and when I am browsing through the manufacturer's code,
> I see they have taken the msm7x30 board and simply modified for their
> needs. So I am currently trying to do the same.
> What do you mean by "procedural way"? I did an early build, after the
> boot logo, it simply turned off/screen turned off, USB did not work. I
> did try this on the recovery, because that should not need all things
> Android needs, right?
>
> Is there a way to save the log somewhere (like /cache or /data), so I
> could check what did not work and get a start somewhere.
>
> On Jan 24, 8:41 am, jagan <[email protected]> wrote:
> > What is your device QC Chipset?
> > -If you your phone chipset supports the downloaded msm kernel, try to
> > download msm-2.6.35[chipset supportable].
> > do the diff b/w   msm-2.6.35 to your device kernel, identify the device
> > spec changes & apply them on msm-3.0.
> >
> > Be-careful you need to do it in a procedural way.
> >
> > Regards,
> > Jagan.
> >
> > On Sat, Jan 21, 2012 at 11:46 PM, Rudolf Tammekivi <[email protected]
> >wrote:
> >
> >
> >
> >
> >
> >
> >
> > > My device has 2.6.35.7 source code provided, but I want to upgrade it
> to
> > > 3.0. Most of the 2.6.35.7 sources are from CodeAurora, which are
> modifed by
> > > manufacturer, and I have already downloaded the 3.0 base for msm. What
> are
> > > the mandatory things I need to modify in order to make it boot? Like
> CPU,
> > > display, memory.
> >
> > > --
> > > unsubscribe: [email protected]
> > > website:http://groups.google.com/group/android-kernel
>
> --
> unsubscribe: [email protected]
> website: http://groups.google.com/group/android-kernel
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel

Reply via email to