RE: ioctl function not completing and hypervisor output

Hi, Sounds like a good idea, firstly Valentine has a good point I also think there is something wrong with the I/O port access (if not then something else in the I/O) so I changed debug_console.phys_start points from 0x3f8 to 0x3e8 in my configs/myboard.c and then make again to obtain a new

Re: ioctl function not completing and hypervisor output

On 14.07.2016 14:16, Dube, Swaraj wrote: Hi, I just got to know that the board I am using uses MMIO, I will have to confirm the base addresses in config/myboard.c with the team in that case however should that be a problem? IIRC debug port setting has no effect on MMIO. But I vaguely recall

RE: ioctl function not completing and hypervisor output

I totally agree with you here, just give me some time to gather relevant information about my target. Regards, Swaraj Dube. -Original Message- From: Jan Kiszka [mailto:jan.kis...@siemens.com] Sent: Friday, July 15, 2016 1:39 PM To: Dube, Swaraj ; Valentine

RE: ioctl function not completing and hypervisor output

I used the command : "dmesg | grep ttyS2" as that is the serial port on my board, it shows the MMIO address at 0x9222e000 however when I add that to debug_console.phys_start(originally 0x3f8) in my configs/myboard.c (attached) , I still get the same error(cpu stalls and no hypervisor output :(

Re: ioctl function not completing and hypervisor output

On 2016-07-15 13:32, Dube, Swaraj wrote: > I used the command : "dmesg | grep ttyS2" as that is the serial port on my > board, it shows the MMIO address at 0x9222e000 however when I add that to > debug_console.phys_start(originally 0x3f8) in my configs/myboard.c (attached) > , I still get the