Thanks for all the help. It turned out that using "fastboot boot
my_zImage" would boot the N1 just fine. So my problem is not in the
kernel but rather in the Android image. It should be a question for
another discussion board.
doug
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
w
I sent this to the list earlier, but didn't see it show up.
In case my mail server ate it, I'm sending it again.
Sorry if it's a dup.
On 07/29/2010 10:47 AM, Danke Xie wrote:
> This is quite amazing -- very few know this way of using the D+/D-
> pins for debugging. Does the ttyMSM0 device really
On 07/29/2010 01:53 AM, Sven Killig wrote:
>> -Original Message-
>> From: android-kernel@googlegroups.com [mailto:android-
>> ker...@googlegroups.com] On Behalf Of Tim Bird
>> Sent: Wednesday, July 28, 2010 10:53 PM
>> To: android-kernel@googlegroups.com
>&
m] On Behalf Of Tim Bird
> > Sent: Wednesday, July 28, 2010 10:53 PM
> > To: android-kernel@googlegroups.com
> > Subject: Re: [android-kernel] Re: Debugging boot problem
>
> > Does the N1 have an exposed serial port?
>
> It seems
> so:http://torvalds-family.blogspot.com/
> -Original Message-
> From: android-kernel@googlegroups.com [mailto:android-
> ker...@googlegroups.com] On Behalf Of Tim Bird
> Sent: Wednesday, July 28, 2010 10:53 PM
> To: android-kernel@googlegroups.com
> Subject: Re: [android-kernel] Re: Debugging boot problem
>
Hi, Danke
Thanks for reply.
I'm porting the kernel-msm-.32 on my Tattoo. It has msm7225 board with
QVGA screen, which is not supported by android. The board driver was
written by HTC for 2.6.29-msm kernel. It seems that to use 2.6.32
kernel on this device, I must port the board driver to kernel-m
Hi Jie,
There are indeed some kernel CONFIG options to enable console support
for a serial tty device. For example, there is one for the serial port
for sure. A serial device usually means it can be used as a tty
terminal, but to be used as a "console", there is additional work on
the driver. So y
Hi,
In my case, no way to run 'adb shell' because the kernel got stuck
before adbd started.
As for USB serial port method, I'm not sure whether some special
CONFIG for the kernel needed or not. What are the detailed steps?
On Jul 29, 9:35 am, andrew_esh wrote:
> Download the SDK Toolkit form
Download the SDK Toolkit form here:
http://developer.android.com/sdk/tools-notes.html
... and run ddms. Connect the phone via USB, and click on it when it
appears in the upper left corner. Watch the colored logcat messages
appear in the lower window pane. The messages may give you some
indication
How else can it be charged, or have photos unloaded?
On Jul 28, 8:09 pm, Abhinav wrote:
> Not sure... Does it have a USB port? if yes Might be worth giving a
> try to get usb -> serial converter.
>
> On Jul 28, 1:53 pm, Tim Bird wrote:
>
>
>
> > On 07/28/2010 12:38 AM, Abhinav wrote:
>
> > > Try
Not sure... Does it have a USB port? if yes Might be worth giving a
try to get usb -> serial converter.
On Jul 28, 1:53 pm, Tim Bird wrote:
> On 07/28/2010 12:38 AM, Abhinav wrote:
>
> > Try connecting a serial and getting the dmesg.. That may provide some
> > info about where it is stuck
>
> Doe
On 07/28/2010 12:38 AM, Abhinav wrote:
> Try connecting a serial and getting the dmesg.. That may provide some
> info about where it is stuck
Does the N1 have an exposed serial port?
-- Tim
=
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Son
Try connecting a serial and getting the dmesg.. That may provide some
info about where it is stuck
On Jul 27, 11:38 am, doug wrote:
> Hello,
>
> My N1 hung on the cross "X" screen after I flashed it with a new boot
> image. How do I debug this boot problem? Is there a way to read the
> boot seq
Hi, I'm also looking for the answer. :-)
On Jul 28, 2:38 am, doug wrote:
> Hello,
>
> My N1 hung on the cross "X" screen after I flashed it with a new boot
> image. How do I debug this boot problem? Is there a way to read the
> boot sequence off the device to see where it gets stuck?
>
> Thanks
14 matches
Mail list logo
