From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ivan Kuten Date: Sun, 07 Oct 2007 20:45:48 +0300 Subject: [Buildroot] Adding Cirrus EP93XX ARM to buildroot In-Reply-To: <20071006201536.GH20951@aon.at> References: <20071003204012.GE20951@aon.at> <47041DC1.8020301@promwad.com> <003c01c8063e$26e48a70$b07ee255@atmel.com> <20071006201536.GH20951@aon.at> Message-ID: <47091B4C.8090205@promwad.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>> >>> And submitting patches to mainstream takes long time. And we want Cirrus support now. > > Supporting some old version of packages with supplemental patches is > fine and one thing. Refusing even try to get your additions merged is > not a proper thing to do IMO. > > It is extremely burdensome and impractical to have to patch every single > "new" upstream release (let alone time-consuming and thus probably > expensive if somebody pays the time you're spending on doing it). > Bernhard, I only wanted to notice that having Cirrus support in buildroot can be -before- then some of Cirrus patches go in mainline kernel. I'm aware about Cirrus patches to 2.6.20.4 and 2.6.17.14, and some of our customers still use 2.6.17.14 kernel version. BR, Ivan -------------------------------- Embedded Linux engineer, Promwad Company: http://www.promwad.com/ Homepage : http://www.ivankuten.com/ --------------------------------