From: Darren Hart <dvhart@linux.intel.com>
To: gmane@reliableembeddedsystems.com
Cc: poky@pokylinux.org
Subject: Re: beagle-xm more testing
Date: Mon, 16 May 2011 12:25:00 -0700 [thread overview]
Message-ID: <4DD17A0C.7030809@linux.intel.com> (raw)
In-Reply-To: <iqo4jm$4mj$1@dough.gmane.org>
On 05/15/2011 01:58 AM, Robert Berger wrote:
> Hi,
>
> with the remotes/origin/bernard-5.0.1 branch and this tweak:
>
> diff --git a/meta/recipes-bsp/uboot/u-boot_git.bb
> b/meta/recipes-bsp/uboot/u-boot_git.bb
> index 4686a58..23212aa 100644
> --- a/meta/recipes-bsp/uboot/u-boot_git.bb
> +++ b/meta/recipes-bsp/uboot/u-boot_git.bb
> @@ -2,7 +2,7 @@ require u-boot.inc
>
> LICENSE = "GPLv2+"
> LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb \
> -
> file://README;beginline=1;endline=22;md5=3a00ef51d3fc96e9d6c1bc4708ccd3b5"
> +
> file://README;beginline=1;endline=22;md5=5ba4218ac89af7846802d0348df3fb90"
This needs to be moved into one of the recipes which define the SRCREV,
otherwise the md5 may change from version to version. md5 and SRCREV
really don't belong in an .inc file.
Would you like to submit this a patch to be included?
>
> FILESDIR =
> "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/u-boot-git/${MACHINE}"
>
> You can get a working poky-sato-sdk well x-server fails, but you end up
> at some login prompt and have networking support.
>
> The poky-lsb-sdk also takes you to a login prompt, but without
> networking from dhcp.
>
> to enable networking from dhcp I did this, which i got from here:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit
> /?id=24b30e528554de78bb61022923e70dd6574e94ec
I agree that I like this approach better, but it won't make the point
release. Look for this one in 1.1.
>
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> auto lo
> iface lo inet loopback
>
> # Wireless interfaces
> iface wlan0 inet dhcp
> wireless_mode managed
> wireless_essid any
> wpa-driver wext
> wpa-conf /etc/wpa_supplicant.conf
>
> iface atml0 inet dhcp
>
> # Wired or wireless interfaces
> auto eth0
> iface eth0 inet dhcp
> iface eth1 inet dhcp
>
> # Ethernet/RNDIS gadget (g_ether) or LAN9514 on BeagleBoard xM
> auto usb0
> iface usb0 inet dhcp
>
> # Bluetooth networking
> iface bnep0 inet dhcp
>
> ... which gives me a usable lsb-sdk image for the beagle-xm ...
>
> The inclusion of those fixes in 5.0.1 would be great to get an "out of
> the box" experience, since the latest and greatest from git is not
> really working:
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1071
The u-boot issues concern me the most. Unfortunately the dev-cut for
5.0.1 is passed. We are looking for much improved bbxm support in 1.1.
Saul, is it too late for a fix like the above to the u-boot md5 to get
into the point release?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-16 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 8:58 beagle-xm more testing Robert Berger
2011-05-16 19:25 ` Darren Hart [this message]
2011-05-17 1:01 ` Robert Berger
2011-05-17 15:21 ` Darren Hart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD17A0C.7030809@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.