Re: [yocto] raspberrypi3-64 target not booting

2017-08-26 Thread Bill Jenkins

> On Aug 26, 2017, at 12:36 AM, Herve Jourdain  wrote:
> 
> Hi,
> 
> Are you using vc4 as graphics, or are you using the default userland?
> If you want graphics with 64 bits, you need to use vc4.
> 

The raspberrypi3-64.conf file has the line:

MACHINE_FEATURES_append = " vc4graphics"

I assume this means it is using vc4? There is no use of "userland" in my 
build/conf
directory. I am fairly new to Yocto, so I am wondering if there is a definitive 
way to 
tell whether the vc4 graphics were used to build the image.

>> Any ideas on how to get the HDMI port to function the same way as it 
>> does for the 32-bit case?
>> 
> 
> Readding the mailing list.
> 
> what you have is exactly what I had when I submitted the port to
> meta-raspberrypi. Haven;t had a chance to revisit it. but this could
> be related to device tree files we are using here. I have had reports
> from other devs of having been able to boot into graphics using older
> kernels but I never got
> that far myself.
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Problems running image in qemu (x86)

2017-08-26 Thread Alex J Lennon
Hi,

I'm bringing the Mono build up to date in the meta-mono layer and ran
into a problem with my testing.

I generally target QEMU, e.g. qemux86, build a core-image-sato based
Mono test image and run up with 'runqemu qemux86'

It's a remote build system so I am SSH'd in with VNC port forwarding and
I view the QEMU box running with a TightVNC client.

This has worked well for a long time, and still works fine with the
current krogoth branch.

I have just built against master though and am seeing screen corruption.

e.g. https://postimg.org/image/xjcdybdul

Can anybody tell me what's changed?

Thanks,

Alex

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] raspberrypi3-64 target not booting

2017-08-26 Thread Herve Jourdain
Hi,

Are you using vc4 as graphics, or are you using the default userland?
If you want graphics with 64 bits, you need to use vc4.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Khem Raj
Sent: vendredi 25 août 2017 19:28
To: Bill Jenkins ; yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] raspberrypi3-64 target not booting

On Fri, Aug 25, 2017 at 10:14 AM, Bill Jenkins  wrote:
>
> On Aug 25, 2017, at 9:42 AM, Khem Raj  wrote:
>
>
> On Fri, Aug 25, 2017 at 9:39 AM Bill Jenkins  wrote:
>>
>> I am trying to just get the simple 64-bit rpi-basic-image to work, 
>> but the Raspberry Pi 3 seems to hang with the rainbow screen at startup.
>
>
> Can you plugin a serial cable and see if that worked or try to add ssh 
> daemon on target and try to ssh into pi
>>
>>
>
> That was a good call. I can login with the ssh daemon, so it does 
> successfully boot. I just cannot access it from the HDMI port. (I do 
> not have the hardware for a serial connection at the moment)
>
> Any ideas on how to get the HDMI port to function the same way as it 
> does for the 32-bit case?
>

Readding the mailing list.

what you have is exactly what I had when I submitted the port to
meta-raspberrypi. Haven;t had a chance to revisit it. but this could
be related to device tree files we are using here. I have had reports
from other devs of having been able to boot into graphics using older
kernels but I never got
that far myself.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto