From: Jakob Viketoft <jakob.viketoft@bitsim.se>
To: Linux PPC Embedded list <linuxppc-embedded@ozlabs.org>
Subject: Adding machine types to the kernel tree...
Date: Thu, 03 Mar 2005 12:46:12 +0100 [thread overview]
Message-ID: <4226F904.5010104@bitsim.se> (raw)
Hi!
Are there any certain policys or religious issues about adding machine
types to the (ppc40x) kernel tree, and who's responsible for kicking
stuff like this up the main tree?
Specifically, I would like to replace the PowerPC405 support for the
Xilinx ML 300 (development board) with generic Xilinx Virtex-II Pro and
Virtex4 support (FPGAs). In my opinion, the end target isn't the
development boards, but the custom configuration it all will run on in
the end, and so things would benefit from a more general support. Do
anyone have any insightful views/opinions on this or comments of any kind?
Clearly, there seem to be some demand for this lately according to
traffic on the list...
Cheers!
/Jakob
next reply other threads:[~2005-03-03 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 11:46 Jakob Viketoft [this message]
2005-03-03 18:50 ` Adding machine types to the kernel tree Andrew May
2005-03-07 10:07 ` Jakob Viketoft
2005-03-07 12:27 ` Matt Porter
2005-03-08 18:01 ` Debian User
2005-03-14 9:43 ` Jakob Viketoft
2005-03-07 17:38 ` Kumar Gala
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=4226F904.5010104@bitsim.se \
--to=jakob.viketoft@bitsim.se \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).