Recent content by CalcProgrammer1

I think there are two different issues here. In hardboot you have to reserve a "hardboot page". This is statically allocated by the kernel as part of the board file as your quoted code shows. The hardboot page doesn't actually store the kexec kernel image, but instead contains the address of...

Hardboot is ARM-specific. If you look at the patch it uses ARM assembly and hooks into SoC specific stuff.

1. The root= option will automatically mount that given device as the root partition (aka /). If you use root= you do not need an initramfs at all, because the kernel will mount the partition and run the /init script automatically. If you don't use a root= command or wish to run more complex...

You don't need them. My sloppy work is showing lol. I took most of that from another kexecboot from the HP TouchPad. Chances are your Tab3 doesn't use LVM, though the TouchPad did so that's where that came from. You can remove it. The tssrv binary is the userspace HP TouchPad touchscreen...

Step one is to get a kexec-capable kernel working. Kexecboot is just a frontend for kexec. There are two options - normal kexec and kexec-hardboot. I managed to make hardboot work with the Note 1 using some patches but haven't been successful with either on the Note 3. I don't know about...

I'm still here. I kinda gave up temporarily after running into too many roadblocks, then I bought a fancy RGB keyboard and lost track of the project. Then the holiday season took up the rest of my year. I want to get back into this, but I think I'm going to try and get Debian running natively...

Yeah, figured that out last night. I found a guide to recalibrate the sensor that worked perfectly. I tried cleaning the outside, but it didn't work and I don't feel like tearing the whole phone apart to clean it.

Awesome, recalibrated my sensor with the efs file and it worked perfectly. I never had an issue with the sensor until now (a month past one year of owning the phone, plus Knox is long tripped so warranty isn't happening). If it gets worse I'll take it apart and clean the sensor but for now the...

I'm having an issue where the proximity sensor only triggers on entering close proximity, not when leaving close proximity. This is noticeable when I get a call, hold the phone up to my ear and the screen turns off but take it away and the screen stays off. I can verify the issue reading the...

No, I just enabled the FIQ debugger in the .config (the code is already in the kernel) but it doesn't compile, FIQ_START is undefined. ryanbg said he was working on it so I am going to wait to see if he has already solved this as to not duplicate work. Have you looked into getting a serial...

hsbadr: Still interested for sure! I don't know what all good Hangouts will be unless we're all online at the same time though. ryanbg mentioned FIQ debugger in a PM he sent me so I'm going to investigate that route on the host kernel and try to get it working. Otherwise the memory tagging...

Trying to figure out /dev/mem <--> /dev/kmem mapping. It is getting to the code that turns on the MMU and after that the memory mapping should be changed, so to tag physical address 0x50000000 I need to know what the corresponding kmem virtual address is. From what I've found, at least in...

Sounds good, I'll take a look at those patches. My kexec-tools binary is the one Tasssadar has on his github for kexec-hardboot, but I guess now that I'm trying to use non-hardboot kexec I should use a different kexec-tools. Either way, I confirmed that execution is getting to the main kernel...

I just found the -C option for hexdump which corrects the endianness issue: [email protected]:/ # /data/local/viewmem 0x2700000 0x100 | hexdump -C...

Looking at this code: mov r8, r2 @ save atags pointer ldr r9, =0x50000000 str r0, [r9, #0] str r1, [r9, #4] str r2, [r9, #8] ldr r10, =0xFFFFFFFF str r10, [r9, #12] #ifndef __ARM_ARCH_2__ produces this output: / # hexdump test.bin 0000000 0000 0000 ffff ffff 1000 0000...