boot_param on boot_usb is not 'top priority', but would definitely be very useful.
Eg. currently the ezx-bp code does not call poweroff on BPWDI2 pin low situation. This pin is used on poweron, when it is low it means that the battery is discharged or that the phone was powered on by a battery insert event, in both cases the correct behaviour is immediate poweroff. On a780 everything works fine, but E680 when booted via boot_usb with stock blob always come with wdi2 low. When flashed, or booted with blob2 it has the exact same behaviour as a780. We could have a kernel argument for this issue, and the same binary kernel will be bootable by boot_usb or flashed and still behave correctly on both cases. Not to mention all the other hardcoded parameters, i cant use 192.168.1.x on usblan without messing with my lan. I like rootfs on mmcblk0p2, others may not., etc... Anyway, as i said its not 'top prio', but it is on my always growing OpenEZX TODO list ;) On 8/25/07, Alex Zhang <[EMAIL PROTECTED]> wrote: > hi Daniel, > > Alex, can this be the cause of the mount failures you got on the SD/TF > support? > > > I don't think it's relative with SD/TF, because SD driver seems time-out > after CMD2. I think we don't power on the card correctly. > > A better quick fix would be patching boot_usb to write zeros to > > boot_param before executing the kernel, or, if you have spare time, > > add boot parameters support to boot_usb. ;) > > > Oh, do you think add boot parameters support to boot_usb is important? > But boot parameters work well we add it to .config. > > Alex Zhang > -- EOF Daniel Ribeiro
