Re: [yocto] UEFI support for Crown Bay

2012-09-23 Thread Sean Liming 
 -Original Message-
 From: Tom Zanussi [mailto:tom.zanu...@intel.com]
 Sent: Saturday, September 22, 2012 9:40 PM
 To: Sean Liming
 Cc: yocto@yoctoproject.org
 Subject: Re: [yocto] UEFI support for Crown Bay
 
 On Fri, 2012-09-21 at 23:11 -0700, Sean Liming wrote:
 
 
  Yocto=1.2
 
  BSB = Crown Bay (Intel Atom Processor E660 with Intel Platform
  Controller Hub EG20T Development Kit)
 
  Target System= Inforce Computing, Inc. - SYS9400 Reference Platform -
  VGA output only.
 
  UEFI only no BIOS
 
  Base Image: core-image-minimal
 
  Hob used to build the image
 
 
 
 
 
 
 
  The target platform only has UEFI and doesn’t have traditional BIOS. I
  am able to re-configure the UEFI firmware using the BLDK application
  if needed. The Crown Bay BSP doesn’t include an efi loader
  (bootia32.efi) like Cedar Trail BSP in the live image (hddimg). If I
  add the EFI boot files from Cedar Trail live image, the USB flash disk
  presents the menu for boot or install. Upon selecting boot, I can see
  output on the serial console, but it eventually stops no output on the
  VGA monitor. I have attached the output from the serial port.
 
 
 
  1. Is UEFI supported with Crown Bay BSP? Is there a flag that needs to
  be set like EFI = “1”?
 
 
 Hi,
 
 The Crown Bay BSP doesn't yet have EFI support - I added it earlier this year
 but had some problems getting it to work.  I just now updated it and tried
 again but though I see the grub menu, selecting 'boot' also gets me a blank
 screen, and I don't even get serial output.
 
 If you want to try it out for yourself and see if you get better results, 
 here's
 the branch (the top 6 commits add efi support and some related cleanup):
 
 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-
 contrib/log/?h=tzanussi/crownbay-efi-v2
 
 The current BSP can be found in the meta-intel repo in the meta-crownbay
 directory (the README has some build instructions):
 
 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/
 
 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-crownbay
 
 
 Since you're using the Inforce Sys9400, though, I'm thinking that it might
 make more sense to use the meta-sys940x BSP:
 
 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-sys940x
 
 I see it already has efi support and so I think that's already been tested and
 probably works (cc'ing Darren, the author of the sys940x and EFI expert who
 actually added the EFI support recipes, etc).
 
 As for EMGD and X, the current BSPs should all be good to go - there was
 some unrelated problems with X in the core which has been fixed, and at
 least as far as the crownbay goes, I know it works as I tested it just
 yesterday...
 
 Hope that helps,
 
 Tom
 
 
Tom,

Thank you. I will get started trying them out.


Regards,

Sean Liming
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176




 
 
  There seems to be discussions about this back in 2011:
 
  https://lists.yoctoproject.org/pipermail/yocto/2011-November/005806.ht
  ml
 
  http://lists.linuxtogo.org/pipermail/openembedded-core/2011-
 November/0
  12972.html
 
 
 
  2. Is it possible to setup serial console for Crown Bay? I tried the
  following flags from the n450 information:
 
 
 
  SYSLINUX_OPTS_atom-pc = serial 0 115200
 
  SERIAL_CONSOLE_atom-pc = 115200 ttyS0
 
  APPEND_atom-pc = console=ttyS0,115200 console=tty0
 
 
 
  3. There was some discussion about EMGD and X Windows issues and a
  possible fix. Where can I download the latest BSP to try out?
 
 
 
 
 
  Regards,
 
 
 
  Sean Liming
 
  Annabooks
 
  Tel: 714-970-7523 / Cell: 858-774-3176
 
 
 
 
  ___
  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] what are libraries required to use SDL

2012-09-23 Thread Tarek El-Sherbiny 
Hi,

I'm porting a program which uses SDL to openembedded Yocto-project. I have
included libsdl to my image but SDL is failling to initialize
SDL_Init(SDL_INIT_VIDEO) gives:
 No available video device

What are the packages that I need to install to get SDL video device?

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

Re: [yocto] what are libraries required to use SDL

2012-09-23 Thread Chris Tapp 
On 23 Sep 2012, at 20:07, Tarek El-Sherbiny wrote:

 Hi,
 
 I'm porting a program which uses SDL to openembedded Yocto-project. I have 
 included libsdl to my image but SDL is failling to initialize 
 SDL_Init(SDL_INIT_VIDEO) gives:
  No available video device
 
 What are the packages that I need to install to get SDL video device?

What graphics do you have available? I've got it working ok using DirectFB and 
X11 should be ok as well.

Chris Tapp

opensou...@keylevel.com
www.keylevel.com



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

Re: [yocto] beagleboard uEnv.txt file

2012-09-23 Thread Sean Liming 
Ed,

 

I was able to build and successfully boot core-image-sato image on the
BeagleBoard Rev C4. There is no mouse or arrow keys to move things around
the screen, but I do get the GUI.

 

I am using Yocto 1.2.

 

Regards,

 

Sean Liming

Annabooks

Tel: 714-970-7523 / Cell: 858-774-3176

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Sean Liming
Sent: Saturday, September 22, 2012 8:15 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] beagleboard uEnv.txt file

 

On 09/22/2012 07:08 AM, Edward Vidal wrote:

Hello All,
Does anyone have a working uEnv.txt file for the core-image-sato for the
beagleoard?
Any help will be appreciated thanks in advance.






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

Attached is one that worked for core-image-minimal.

Here are the contents:

bootfile=uImage
address_uimage=0x8030

console=ttyO2,115200n8

mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
optargs=console=tty0

mmc_load_uimage=fatload mmc 0:1 ${address_uimage} ${bootfile}

mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot}
rootfstype=${mmcrootfstype}

loaduimage=run mmc_load_uimage; echo Booting from mmc ...; run mmcargs;
bootm ${address_uimage}





-- 
Regards,
 
Sean D. Liming
 
Annabooks
Cell: 858-774-3176
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto