yocto@lists.yoctoproject.org

[PATCH 2/2] meta-cedartrail: Update PVR graphics driver to version 1.0.2

From: Rahul Saxena <rahul.saxena@...> This update of the driver enables support for B3 stepping of Cedarview processor and also support for DP/eDP ports. Signed-off-by: Rahul Saxena

By rahul.saxena@... · #8953 ·

[PATCH 1/2] meta-cedartrail: Update SRCREV for the linux-yocto kernel pvr branch

From: Rahul Saxena <rahul.saxena@...> Update SRCREV to point to yocto/pvr kernel branch with v1.0.2 pvr driver support. Signed-off-by: Rahul Saxena <rahul.saxena@...> ---

By rahul.saxena@... · #8952 ·

[PATCH 0/2][meta-intel] Cover letter to update pvr driver to v1.0.2 in meta-cedartral, denzil branch

From: Rahul Saxena <rahul.saxena@...> Cover letter to update pvr driver to v1.0.2 in meta-cedartrail. This update of the driver supports B3 stepping of the Cedarview processor and also

By rahul.saxena@... · #8951 ·

Re: New task progress interface with Yocto 1.3 ?

Yes, it's definitely an improvement! Elvis

By Elvis Dowson · #8950 ·

Re: New task progress interface with Yocto 1.3 ?

Yes isn't it cool

By Khem Raj · #8949 ·

New task progress interface with Yocto 1.3 ?

Hi, I'm building against the latest yocto master branch, and noticed that the task progress now summarizes the total number of active theads: NOTE: Resolving any missing task queue

By Elvis Dowson · #8948 ·

Re: [PATCH 3/3] Enable bash-ptest

Thanks for proposing and getting the initial implementation started, this has been something we have been thinking about for a while, great to have the things like this become reality! When

By Saul Wold <sgw@...> · #8947 ·

configuring WiFi in Yocto

When I configured WiFi with Yocto on a n450 based netbook, all I had to do was get the right drivers for the hardware included in the Yocto 3.2 kernel, then I could use the GUI Connection Manager to

By Jim Abernathy · #8946 ·

Re: TARGET_FPU not getting populated for powerpc 405/440 fpu-hard targets

fpu-hard is the classic PowerPC FPU unit. If that is what these ip blocks implement then there is nothing further required. If the unit does NOT include a classic PowerPC FPU, then you should not be

By Mark Hatle <mark.hatle@...> · #8945 ·

Re: TARGET_FPU not getting populated for powerpc 405/440 fpu-hard targets

yes. However if there are some special ABI extentions becasue of FP that gcc should configure itself with then that should be specified in TARGET_FPU. I havent looked into gcc code to check if it

By Khem Raj · #8944 ·

Re: TARGET_FPU not getting populated for powerpc 405/440 fpu-hard targets

Hi Khem, The FPU unit is an IP core, that is attached to a generic PowerPC405 or PowerPC440 embedded processor core on the FPGA, which by default doesn't contain an FPU unit. In the Xilinx FPGA

By Elvis Dowson · #8943 ·

Re: TARGET_FPU not getting populated for powerpc 405/440 fpu-hard targets

that means default is hard for this architecture. This option is essentially used to configure gcc unless your fpu is special like fsl one's you are good here.

By Khem Raj · #8942 ·

Re: dev manual section on "customizing images" needs serious adjustment

That is quite a different thing: core-image-minimal is a recipe to build an image with defined contents, in contrast core-image is a class, and the whole point of classes is that recipes can inherit

By Tomas Frydrych <tf+lists.yocto@...> · #8941 ·

Re: Errors while creating a new PowerPC 405e tune file

gcc only knows 405fp so thats what you use here

By Khem Raj · #8940 ·

TARGET_FPU not getting populated for powerpc 405/440 fpu-hard targets

Hi, I just observed that TARGET_FPU is not getting populated, when you do a build for fpu-hard targets. For fpu-soft targets, it displays TARGET_FPU = "soft", but for fpu-hard targets, it

By Elvis Dowson · #8939 ·

Re: dev manual section on "customizing images" needs serious adjustment

sure. but if you similarly explicitly set IMAGE_INSTALL before inheriting core-image, you're not really "inheriting" core-image either. :-) rday --

By Robert P. J. Day · #8938 ·

Re: Errors while creating a new PowerPC 405e tune file

Hi, My bad, it was a typo, I should have been written as follows: TUNE_PKGARCH_tune-ppc405e = "ppc405e" The only question I have now is, should I be defining TARGET_CPU as 405fp or 405e

By Elvis Dowson · #8937 ·

Re: dev manual section on "customizing images" needs serious adjustment

+1. If you add additional packages to core-image-minimal in your local.conf, you're no longer really building core-image-minimal. Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel

By Scott Garman <scott.a.garman@...> · #8936 ·

Re: [PATCH 3/3] Enable bash-ptest

As it stands, I can bet on upstream saying "no" to this for good reason. A better concept might be to introduce $(CC_FOR_TEST) which could default to CC_FOR_BUILD. This would let us do what you're

By Richard Purdie · #8935 ·

Errors while creating a new PowerPC 405e tune file

Hi, I have defined a tune-ppc405e.inc ( suffixed with an 'e' to signify that it has a hardware floating point unit attached), as follows: DEFAULTTUNE ?= "ppc405e" require

By Elvis Dowson · #8934 ·

Messages