some questions about kernel src

some questions about kernel src

[ayaka]

Hello everyone I am porting debian armhf to my mobile htc shooteru(evo 3d gsm). But I met some problem with htc kernel source, so I want to try Mr.David's src. I have clone it, but I don't know which branch shall I check out. The problem of htc kernel src is once you set config_vt=y, kernel will load the initramfs in the boot partition of emmc. I have made a image whose kernel don't support initramfs with a fake empty initramfs and noinitrd in kernel parameters. I wish the Mr.David's src won't have this problem.

another question is whether I can ask question about lk_bootloader here. I cannot compile it.

Thank you.
-- 
ayaka

Re: some questions about kernel src

[Denis 'GNUtoo' Carikli]

On Sunday, May 20, 2012 01:33:30 PM ayaka wrote:
> Hello everyone I am porting debian armhf to my mobile htc shooteru(evo 3d
> gsm). But I met some problem with htc kernel source, so I want to try
> Mr.David's src. I have clone it, but I don't know which branch shall I
> check out. The problem of htc kernel src is once you set config_vt=y,
> kernel will load the initramfs in the boot partition of emmc. I have made a
> image whose kernel don't support initramfs with a fake empty initramfs and
> noinitrd in kernel parameters. I wish the Mr.David's src won't have this
> problem.
I think his trees are wor for integration in linux-next.

While the code is way cleaner and won't have the problem you described it will 
have other issues such as:
* No support for shooteru board(you will have to add it yoursel by adding a 
board file or a device tree file, I don't know the current status of device tree 
for msm).
That may require to get or build a serial cable specially for for your phone.
*incomplete drivers support: not all drivers you want/need for your phone are 
in mainline or in linux/next, however there are some(I didn't look at it 
extensively, so I can't tell how much, sorry) support for msm8x60.

Basically if you go the mainline road expect to have to do some work for 
integrating the lacking drivers(that comes from your shooteru kernel) and for 
adding a board file/device tree file for shooteru.
But that will get you a cleaner kernel for your device, and kernel experience 
too. so it might be worth it.

Denis.

Re: some questions about kernel src

[David Brown]

On Sun, May 20, 2012 at 01:33:30PM +0800, ayaka wrote:

> Hello everyone I am porting debian armhf to my mobile htc
> shooteru(evo 3d gsm). But I met some problem with htc kernel source,
> so I want to try Mr.David's src. I have clone it, but I don't know
> which branch shall I check out. The problem of htc kernel src is
> once you set config_vt=y, kernel will load the initramfs in the boot
> partition of emmc. I have made a image whose kernel don't support
> initramfs with a fake empty initramfs and noinitrd in kernel
> parameters. I wish the Mr.David's src won't have this problem.

Which Mr David are you referring to?  The kernel/msm.git kernel tree
on codeaurora.org's current active branch is msm-3.0

> another question is whether I can ask question about lk_bootloader
> here. I cannot compile it.

I'm not sure if anyone reads it who would know, but I don't think
there is anywhere else to ask.  How are you trying to build it?  I've
been able to build it, but not tried running.

David

> Thank you.
> -- 
> ayaka
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

Re: some questions about kernel src

[Shantanu Gupta]

I'm able to compile and run lk on 8x50 target, but had to fixup the
cryptography which is not really needed and not sure if it is even
supported on your board, apart from that you'll need to gather a lot
more info about your board like nand partition map etc.. required for
you to read the kernel from nand and place it in memory and maybe more
if you want fastboot to work (oem commands will not be available in
lk), iirc, if you want to load lk instead of linux kernel from
manufacturer's bootloader, you will have to preserve r0~r3 and the
tagged list, you can read the partition map for applications from
there (modem partitions are not passed to linux). It would be better
if you could use a tinboot (or arch/arm/boot/compressed/head.S) like
wrapper if necessary, but since your board's bootloader supports
booting linux, why do you need to build lk ?

>> another question is whether I can ask question about lk_bootloader
>> here. I cannot compile it.