On 12/06/14 13:38, meino.cramer@gmx.de wrote:

Hi,

recently I bought a great little Linux board: Arietta G25
(http://www.acmesystems.it/arietta)

Since I like Gentoo I installed it instead of the provided Debian
system.  The system I used to compile the kernel is -- of course -- a
Gentoo -- Linux PC.

Fantastic effort there Meino!

Ok, so looking here:

http://www.gentoo.org/proj/en/base/embedded/

I cannot determine who is the one to contact to
get this offering of current information, correctly
formatted to be included in the "boards" section
of the gentoo embedded handbook?

Next point, Meino has offered up a great bit of information
that surely does not belong in the Gentoo embedded handbook,
but is a great resource to encourage others how to go about
hacking away at a gentoo embedded project. So I think the
original email can be listed somewhere for others newer to
embedded gentoo hacking, as an example. Where would this
be placed? Linked to the handbook as "references" or "notes" or "appendix 1"  or such?


Also, if there is a format we want folks to follow should the
gentoo embedded project page have a suggested format to follow?

Many of those listing in the board section merely contain:

1. Board specifications
2. /proc/cpuinfo

Maybe the full possible format (optional for the contributor)
could have these additional categories:

make.conf

bootstrap/init details

installed packages

cross compiling details

Native compiling details

Special code/hacks included
(such as netconsole.c)

Libraries
ulibC, musl, bionic, glibc

languages

Added hardware, such as a relay board to
power up and down other electronics as an example.

So, being a long time reader of gentoo embedded, I understand that
most folks in the gentoo-embedded-project space, are busy and have
a very deep and strong background in embedded linux. I also understand
that they do not need a robustly maintained gentoo-embedded-handbook. But, if we are to encourage others to learn and develop into strong
gentoo-embedded hackers, then we should provide a pathway for their
needs. Expanding the scope of the gentoo-embedded-manual or creating
an ancillary document, with many more simplified steps, would be
an excellent first step to revitalizing gentoo-embedded, imho.

Personally, I'd like to see what the 64Bit arm devs have in mind for
the Gentoo embedded handbook, or as a minimized full (stage?) offering?
I've just been waiting for 64Bit arm boards to come down a bit in
price; ymmv.

I will defer to the leadership decision of the gentoo-embedded-project
team.

sincerely,
James Horton