On Tue, Jun 16, 2009 at 5:27 PM, hu zhangli <huzhan...@gmail.com> wrote:
> 1. to daniel , pls update newest zImage and related CONFIG. > > i remember i only use boot-usb to download the android 2.6.25, i dont use > gen-blob. why? > when the battery is quickly insert, at this time the system log will be > still in the ram. > so use boot_usb to dump the kernel message, but as you say , the boot_usb , > gen-blob may flush part mem , right??? > On the Wiki: There is a bug in the mainline pxa-udc's driver (not used in OpenEZX's 2.6.25 or older kernels that used a different pxa-udc driver (the one in svn server)and don't necessitate the 'boot_usb gen-blob 0' command) that cause a "kernel panic", so the only way to use usb without any changes on this driver is to boot using a second stage bootloader, gen-blob, that "prepare" the phone in a way the driver can work with it, and not cause a panic. Also, the .25 version of android's patches published on motorolafans was only valid for a1200 afaik, and may not run on other phones with a machid, so the machid have to be reimplemented... anther quesiton , i see there is no much USB UDC code to support usbnet > communcation, whether openezx git mainline dont support usbnet > so i couldnt use NFS to mount ROOFS. i could only use SD card??????? > > could you guide me the detail how to port related BSP, steps. for example > sdram , fb init, ram console init, bp init, emu etc. > > 2. > whether related dev node will be created dynamicly , such as logger, > binder, ashem, fb , these device nodes should be created by hand?? > > > > > > > > 2009/6/16 Daniel Ribeiro <drw...@gmail.com> > > Em Ter, 2009-06-16 às 11:35 +0800, hu zhangli escreveu: >> > after i download zImage to A1200 , the lcd panel is confused and >> > no kernel message print. could you recommend one way to dump out the >> > startup message? >> >> You can use boot_usb/gen-blob to read the phone RAM after the crash. You >> will probably(*) see the kernel messages in there. >> >> Follow these steps: >> Cause the "white screen" crash. >> Remove the battery and reinsert it as fast as possible. >> Enter gen-blob USB mode. >> run boot_usb read 0xa0000000 31457280 memdump >> strings memdump | less >> >> (*) Probably, because the original bootloader and gen-blob will >> overwrite some parts of the memory, so, you need some "luck" here. ;) >> >> -- >> Daniel Ribeiro >> > >
