From: "David H. Lynch Jr." <dhlii@comcast.net>
To: linuxppc-embedded@ozlabs.org
Subject: Howto submit drivers/patches ?
Date: Mon, 19 Dec 2005 00:25:26 -0500 [thread overview]
Message-ID: <43A64446.8080109@comcast.net> (raw)
In-Reply-To: <OF22452781.22D7B3D3-ON652570D9.0019E468-652570D9.001A1298@tcs.com>
I am just polishing off bringup a Xilinx Virtex IV/ppc405 system with
minimal hardware under 2.6.14.4.
I have a collection of patches that I can submit for the specific,
board, for the Virtex IV, for board specific hardware, ...
Additionally I have 2 complete boot loader through full serial driver
implementations of a pseudo serial console driver for this board when it
is in a HOST development system - it is a compact flash card normally
plugged into a PC during development and using the PC as the console,
and a complete serial driver chain for the Xilinx UartLite as a console
when not in a Host, or as a general serial driver. The Xilinx Driver is
based heavily on other 2.6 driver/serial drivers and not the 2.4
implementation from Xilinx.
Is this list the right place to submit this ?
Is there a HOWTO addressing the rules/procedures to do so.
I have not looked at the kernel style guides, but the style of this
code is pretty much identical to other Kernel code. The UartLite driver
is virtually indistinguishable from other driver/serial drivers except
the few places where hardware differences require changes, and that
there is a full tree of end-end support similar to what exists for the
8250's.
David H. Lynch Jr.
DLA Systems
354 Rudy Dam Rd.
Lititz, PA 17543
717.627.3770
next prev parent reply other threads:[~2005-12-19 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 4:44 help reqd for mpc8260 linux prabha.j
2005-12-19 5:25 ` David H. Lynch Jr. [this message]
2005-12-19 10:09 ` Howto submit drivers/patches ? Vitaly Bordug
2005-12-19 13:10 ` John Carlson
2005-12-31 4:02 ` Grant Likely
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=43A64446.8080109@comcast.net \
--to=dhlii@comcast.net \
--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).