From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Booting BeagleBoard
Date: Sat, 12 Feb 2011 20:21:40 -0500 [thread overview]
Message-ID: <4D573224.8020705@windriver.com> (raw)
In-Reply-To: <4D569EC5.6040609@mlbassoc.com>
On 11-02-12 9:52 AM, Gary Thomas wrote:
> I have a BeagleBoard C3 (not the new xM). Trying to run the
> latest Poky ran into some problems:
>
> * The boot commands in README.hardware are no longer accurate
> for the 2.6.37 (linux-yocto) kernel. At least you need to
> use ttyO2 for the serial console.
This one is known, we are balancing the fact that the
beagle board exists in multiple kernel versions and
2.6.37 is a transition point for the serial .. so the
docs haven't been update with that change yet.
> * There is no video? /dev/fb0 is not being created.
>
> I know that the previous (Angstrom based) 2.6.32 kernel had
> lots of additions which support video (DSS subsystem) and
> also camera (ISP). Has this support been ported forward
> into the Yocto kernel?
>
> Perhaps I missed some setting?
Not missing anything. We are moving onto some other
beagleboard variants, so left the forward port of the
beagleboard at mainline status (which is enough to meet
the existing demo requirements). So whatever has made it
to the mainline 2.6.37 kernel works, which is largely
what you are seeing.
What we are building up for the supported boards is a
common set of features (tracing, boot media, filesystems,
configuration, etc) that are uniform across architectures
and boards. That in turn extends our ability to build,
validate and maintain many more boards that would otherwise
be possible.
On top of the common feature set, comes the board specific
functionality. That functionality is selected / ported from
the best sources (and is hopefully something on its
way to mainline). That porting effort typically comes
after we have the base solidified and a board is of suitable
interest to have this deeper support (or if patches are
contributed).
Anyway, that doesn't answer your question, but explains
what/why things may appear to be in an early phase of
support.
Cheers,
Bruce
>
> Thanks
>
next prev parent reply other threads:[~2011-02-13 1:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:52 Booting BeagleBoard Gary Thomas
2011-02-12 14:55 ` Gary Thomas
2011-02-14 16:34 ` Darren Hart
2011-02-12 15:01 ` Koen Kooi
2011-02-13 14:57 ` Gary Thomas
2011-02-13 15:00 ` Koen Kooi
2011-02-13 15:06 ` Gary Thomas
2011-02-13 15:21 ` Koen Kooi
2011-02-13 15:32 ` Gary Thomas
2011-02-13 18:14 ` Frans Meulenbroeks
2011-02-14 12:35 ` Richard Purdie
2011-02-14 13:23 ` Frans Meulenbroeks
2011-02-13 1:21 ` Bruce Ashfield [this message]
2011-02-14 16:32 ` 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=4D573224.8020705@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=gary@mlbassoc.com \
--cc=poky@lists.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.