Steve Spano wrote:
Hello Folks,
We have a patchset that will be released shortly against the MontaVista
kernel from the DVEVM and the git U-BOOT.
The patchset will add support for the FLE FALCON, which is our
SingleBoard DSP System based on the DM6446 and Xilinx Spartan3E FPGAs.
The FALCON is heavily based on the DVEVM architecture; so you can take
an app developed on the DVEVM and run it with minor changes on the
FALCON.
I can send more details if someone is interested in specifics on the
FALCON.
Is there a process here for releasing patchsets for inclusion?
* Regarding U-Boot:
U-Boot patches have to go to U-Boot development list:
[EMAIL PROTECTED]
http://www.denx.de/wiki/UBoot/Patches
On U-Boot list they are more strict regarding patches than we are here
at DaVinci list, so you should follow some rules:
- Make sure your coding style is okay:
http://www.denx.de/wiki/UBoot/CodingStyle
- U-Boot list has a limitation of 40kByte per Mail, so you have to
split your patch to reasonable parts. You can take Sergeys inital
DaVinci patch as an example:
http://sourceforge.net/search/?words=DaVinci&sort=posted_date&sortdir=desc&offset=70&group_id=65938&type_of_search=mlists&pmode=0
As subject I propose e.g.:
[PATCH 0/x] ARM: DaVinci: Support for FLE FALCON
[PATCH 1/x] ARM: ...
Normally, patch 0/x contains a description what the following patches
are about, without any patch in it. The real patches are in mails 1/x,
2/x etc. Don't forget your Signed-off-by:
- You need to use a mail tool to send the patches which can inline
patches (no attachment!) but doesn't wrap the lines. I was told that
git-send-mail does it the best way, but never tried myself. Maybe you
want to send the patches first to yourself and check the format before
sending them to the list.
* Regarding kernel:
I can't talk about MV kernel. From my point of view, this is quite
outdated (2.6.10?) and it would be a pain to port things to recent
kernel. So IMHO doing patches against this isn't a good idea.
If you like to support open source community and release patches
against recent open source git kernel:
Yes, we are really interested in patches! Unfortunately Kevin, who
maintains the git kernel, currently has only really limited time to do
so. But basically we are really interested in patches.
Regarding the patches themself, most of the rules applying for U-Boot
will work here as well. However, we are not so strict, as patch
frequency is lower here.
- Codingstyle: ./scripts/checkpatch.pl of Linux kernel shouldn't have
any complains any more
- Subject style should be
[PATCH 0/x] ARM: DaVinci: Support for FLE FALCON
[PATCH 1/x] ARM: ...
as well.
- We have no 40k limit here and attachments should at least be okay.
But split your patches in reasonable, easy to review parts. And if you
select attachments, send them so that mail tools will understand them
as text and not binary.
Regarding kernel and U-Boot all patches have to apply to recent code
without recjects, but this should be clear ;)
Be prepared that most probably you have to go through several
review-cyles and iterations before everybody is happy and patches are
considered for inclusion. Can be time consuming... ;)
Best regards
Dirk
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
