From: Tony Lindgren <tony@atomide.com>
To: "Dejan Gačnik" <dejan.gacnik@gmail.com>
Cc: yegor_sub1@visionsystems.de,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Yegor Yefremov <yegorslists@googlemail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX
Date: Mon, 8 Oct 2012 13:55:52 -0700 [thread overview]
Message-ID: <20121008205552.GC13011@atomide.com> (raw)
In-Reply-To: <CAFoWwXv2GjWt2+sCYqM+vbtJ5xJBJAJMSuZhjKLKtURQ0eziVw@mail.gmail.com>
* Dejan Gačnik <dejan.gacnik@gmail.com> [120927 07:13]:
>
> I and my colleagues have developed a brand new very enhanced board having
> AM35xx CPU, 512MB DDR2, DVI, true dual Ethernet support (not using PRUSS),
> CAN, SPI, I2C, 7 USBs, etc…Board is already materialized and operational.
>
>
> According to our board we have create new machine type in the kernel
> (version: linux-3.2-psp04.06.00.07.sdk) and all other required stuff to
> support our board, modify some things, like adding support for dual eth,
> etc. Our goal is to provide this new board to the market (let say with
> large quantity) and therefore I am wondering how to start or if it is even
> possible to transfer our kernel change the main stream of this distro?
> During this kernel modification process we have been looking to not
> changing anything in kernel, what could affect other machine types.
For the mainline kernel, you should go with device tree based booting
to start with, we are no longer adding new board-*.c files. For older
distro kernels you need to maintain a separate board-*.c file until
we have moved everything to use device tree and distros are using
that kernel.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-10-08 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 14:20 [PATCH] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX yegorslists
2012-09-24 17:18 ` Tony Lindgren
2012-09-24 19:05 ` Yegor Yefremov
2012-09-24 23:16 ` Russell King - ARM Linux
2012-09-25 0:37 ` Tony Lindgren
2012-09-25 8:05 ` Yegor Yefremov
2012-09-25 8:14 ` Russell King - ARM Linux
2012-09-25 8:28 ` Yegor Yefremov
2012-09-27 14:12 ` Dejan Gačnik
2012-10-08 20:55 ` 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=20121008205552.GC13011@atomide.com \
--to=tony@atomide.com \
--cc=dejan.gacnik@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=yegor_sub1@visionsystems.de \
--cc=yegorslists@googlemail.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 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).