All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Raphael Assenat <raph@8d.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Criteria for merging new board support files
Date: Thu, 12 Jul 2012 23:51:04 -0700	[thread overview]
Message-ID: <20120713065102.GJ1122@atomide.com> (raw)
In-Reply-To: <20120712204710.GA3850@renkinjitsu.usine.8d.com>

Hi,

* Raphael Assenat <raph@8d.com> [120712 14:28]:
> Hello,
> 
> We have designed a board based on the AM3505 to use in one of our products,
> an unattended payment terminal. I am wondering if it would be meaningful 
> to clean up and submit our patches to add support for our board in the 
> mainline.
> 
> As this board is neither a development/evm platform nor a mass produced 
> consumer product, not many users, if ever, will want to customize
> their kernel. Therefore I am not sure what the advantages for the 
> community at large would be... Besides our code serving as yet another 
> board file example.
> 
> What is the current maintainer position regarding new board support files? 
> Were submissions from people in the same situation ever merged? Do you think
> it worth the effort to clean up and submit our board support files?

We're moving towards device tree based booting and the board-*.c files
will be going away except for board-generic.c. No new board-*.c files
will be merged.

I've been carrying some board-*.c files in the testing-board branch,
but we're now at a point where the devicetree based booting should work
for simple cases. Some parts are of course still missing.

So I suggest you just provide a new .dts file for your board. Might be
worth posting the board-*.c file anyways so people can use that if
they want to.

Regards,

Tony

      reply	other threads:[~2012-07-13  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 20:47 Criteria for merging new board support files Raphael Assenat
2012-07-13  6:51 ` Tony Lindgren [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=20120713065102.GJ1122@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=raph@8d.com \
    /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.