From: Pantelis Antoniou <panto@intracom.gr>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: How to submit support for a new board
Date: Mon, 07 Oct 2002 13:11:18 +0300 [thread overview]
Message-ID: <3DA15DC6.9000808@intracom.gr> (raw)
Hello
We have a board based on a MPC850SR that I want to submit
for inclusion to the main tree.
Currently we work on the stable 2.4.19 branch.
The thing is that this board in kind of peculiar.
For example there's a driver for the multichannel controller
so that means that no serial port is available after booting.
That required to include the netconsole patch by Ingo
and make it work without being a module.
Given into account the scarcity of the dual port RAM under
such conditions I've added support for a malloc like
interface for DPRAM use, after taking into account
the uCode patches and any holes left over by the
enabled peripherals.
As you can see there is no chance in hell of getting
these included as they are.
How should I go about this given the feature freeze
for 2.6; but the 2.6 tree is too unstable for us.
Any suggestions?
Regards
Pantelis Antoniou
Intracom S.A. Greece
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-10-07 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DA15DC6.9000808@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@lists.linuxppc.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.