On 08/04/2014 06:24 AM, Hans de Goede wrote:
Hi,
On 08/04/2014 12:13 PM, Robert Moskowitz wrote:
On 08/04/2014 04:10 AM, Hans de Goede wrote:
Hi,
On 08/04/2014 02:44 AM, Robert Moskowitz wrote:
YES! I have a working ethernet:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 02:c4:03:82:c1:53 brd ff:ff:ff:ff:ff:ff
inet 208.83.67.183/28 brd 208.83.67.191 scope global dynamic eth0
valid_lft 259182sec preferred_lft 259182sec
inet6 2607:f4b8:3:3:c4:3ff:fe82:c153/64 scope global noprefixroute dynamic
valid_lft 33sec preferred_lft 23sec
inet6 fe80::c4:3ff:fe82:c153/64 scope link
valid_lft forever preferred_lft forever
Good, I'm happy to hear that everything now works.
So the next question is how do I track updates to the uboot and which step in your build cookbook do I start with. I suspect it is the git checkout. Do I just run that each time I pull down a new F21 build candidate?
Yes until a .bin file for the cubieboard2 shows up which it should eventually.
# git checkout -B next origin/next
Branch next set up to track remote branch next from origin.
Reset branch 'next'
Your branch is up-to-date with 'origin/next'.
So looks like I am good for a bit.
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
