From: Grant Likely <grant.likely@secretlab.ca>
To: "David H. Lynch Jr." <dhlii@comcast.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Howto submit drivers/patches ?
Date: Fri, 30 Dec 2005 21:02:03 -0700 [thread overview]
Message-ID: <43B602BB.7030906@secretlab.ca> (raw)
In-Reply-To: <43A64446.8080109@comcast.net>
David H. Lynch Jr. wrote:
> 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.
Do you want to send me your patches for the UartLite (and cc the list)?
I'd be happy to take a look. What other things did you change?
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
prev parent reply other threads:[~2005-12-31 4:09 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 ` Howto submit drivers/patches ? David H. Lynch Jr.
2005-12-19 10:09 ` Vitaly Bordug
2005-12-19 13:10 ` John Carlson
2005-12-31 4:02 ` Grant Likely [this message]
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=43B602BB.7030906@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=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).