Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] beagleboneblack: add board
Date: Fri, 27 Sep 2013 15:21:09 +0300	[thread overview]
Message-ID: <1380284469.22318.31.camel@viko> (raw)
In-Reply-To: <1380220826-17732-1-git-send-email-jkridner@beagleboard.org>

On Thu, 2013-09-26 at 18:40 +0000, Jason Kridner wrote:
> From: Jason Kridner <jdk@ti.com>
> 
> Signed-off-by: Jason Kridner <jdk@ti.com>
> ---
>  board/beagleboneblack/linux-3.8.config | 4305 ++++++++++++++++++++++++++++++++
>  configs/beagleboneblack_defconfig      |   38 +
>  2 files changed, 4343 insertions(+)
>  create mode 100644 board/beagleboneblack/linux-3.8.config
>  create mode 100644 configs/beagleboneblack_defconfig
> 

Tested this with Beaglebone Black. u-boot loads kernel image
from /boot/uImage by default (see include/configs/am335x_evm.h) so that
BR2_LINUX_KERNEL_INSTALL_TARGET is needed to be able to boot.

I see these errors at startup:

/etc/init.d/S93-am335x-pm-firmware-load: line 4: can't
create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory
/etc/init.d/S93-am335x-pm-firmware-load: line 5: can't
create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/data: nonexistent directory
/etc/init.d/S93-am335x-pm-firmware-load: line 6: can't
create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory


I have also tried my chance to boot "am335x evm starter kit" by adding
am335x-evmsk to the dts list; but it didn't boot :/

Thanks,
Fatih

  parent reply	other threads:[~2013-09-27 12:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 18:40 [Buildroot] [PATCH] beagleboneblack: add board Jason Kridner
2013-09-26 19:42 ` Peter Korsgaard
2013-09-26 20:09   ` Ryan Barnett
2013-09-26 20:53     ` Jason Kridner
2013-09-27  5:42       ` Fatih Aşıcı
2013-09-27  6:12       ` Fatih Aşıcı
2013-09-27 14:19         ` Jason Kridner
2013-10-03 20:32           ` Peter Korsgaard
2013-10-03 23:19             ` Jason Kridner
2013-09-27 13:07       ` Ryan Barnett
2013-09-27 12:21 ` Fatih Aşıcı [this message]
2013-09-27 14:24   ` Jason Kridner
2013-09-28  3:08 ` [Buildroot] [PATCHv2] beaglebone: add BeagleBone Black support Jason Kridner
2013-09-30  6:23   ` Fatih Aşıcı
2013-10-04 15:31     ` Peter Korsgaard
     [not found]       ` <A20C6CC8-715F-45C3-BB9F-5085269FFD13@ti.com>
2013-10-04 15:40         ` Peter Korsgaard
2013-10-05  7:53           ` Fatih Aşıcı
2013-10-05  9:12             ` Peter Korsgaard
2013-10-05 10:21               ` Fatih Aşıcı
2013-10-05 18:13                 ` Peter Korsgaard
2013-10-04 15:41       ` Jason Kridner

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=1380284469.22318.31.camel@viko \
    --to=fatih.asici@gmail.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox