From: Mike Frysinger <vapier@gentoo.org>
To: Ronny Kramer <ronny.kramer@s2010.tu-chemnitz.de>,
gentoo-embedded@lists.gentoo.org
Cc: solar@gentoo.org
Subject: [gentoo-embedded] Re: Howto add support for Microblaze Architecture
Date: Thu, 20 Mar 2014 20:35:30 -0400 [thread overview]
Message-ID: <6771047.7391CWc7Nz@vapier> (raw)
In-Reply-To: <53270CD8.3060708@s2010.tu-chemnitz.de>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On Mon 17 Mar 2014 15:55:20 Ronny Kramer wrote:
> currently I am about to write my bachelor's thesis about how to setup an
> Microblaze Architecture with Linux support to ease lectures in low level
> coding. I've built an ready to use Linux from Scratch root filesystem
> but i want to use Gentoo as my Base to ease the package compilation.
>
> Is there an Documentation available, how to correctly add an new
> architecture?
hmm, i've had this guide (and helper scripts) for many years:
http://dev.gentoo.org/~vapier/PORTING-HOWTO
but it could do with a bit of a refresh. i guess would also be good to move
it to the wiki for better visibility.
> To get crossdev (specially linux-headers) working I've added an new
> architecture in "profiles/arch" and added the name in
> "profiles/arch.list". This did not help to prevent emerge from
> complaining about "Package unsupported for unknown".
make sure your profiles/arch/microblaze/make.defaults has:
ARCH=microblaze
and that your profiles/default/linux/microblaze/parent file loads that
directory. if you want an example, look at how arm64 is doing things as that
is the newest Gentoo port currently.
i'd be happy to merge microblaze into the main tree if you send patches :).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
parent reply other threads:[~2014-03-21 0:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53270CD8.3060708@s2010.tu-chemnitz.de>]
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=6771047.7391CWc7Nz@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=ronny.kramer@s2010.tu-chemnitz.de \
--cc=solar@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox