From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa BUILDROOT support
Date: Tue, 3 Mar 2009 09:34:20 +0100 [thread overview]
Message-ID: <20090303093420.77f7c3dd@surf> (raw)
In-Reply-To: <49ACD317.6060205@hq.tensilica.com>
Le Mon, 02 Mar 2009 22:49:59 -0800,
Maxim Grigoriev <maxim@tensilica.com> a ?crit :
> Xtensa BUILDROOT uses a concept of source overlays,
> which are necessary because Xtensa processors are
> configurable and extensible. Xtensa tools, e.g.
> gcc, gdb, and binutils, use source overlays, which
> can not be substituted by the current BUILDROOT
> patching mechanism. This update makes patch-kernel.sh
> script capable of handling these overlays.
Can you detail how this concept of source overlays work, technically ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-03-03 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 6:49 [Buildroot] Xtensa BUILDROOT support Maxim Grigoriev
2009-03-03 8:34 ` Thomas Petazzoni [this message]
2009-03-03 22:09 ` Maxim Grigoriev
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=20090303093420.77f7c3dd@surf \
--to=thomas.petazzoni@free-electrons.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